#4355669 - 05/06/17 07:33 AM
Re: Windows 10 creators update
[Re: dutch]
|
Joined: Sep 2007
Posts: 1,910
dutch
Member
|
Member
Joined: Sep 2007
Posts: 1,910
EURO-zone
|
|
|
|
#4357520 - 05/15/17 07:50 PM
Re: Windows 10 creators update
[Re: dutch]
|
Joined: Sep 2007
Posts: 1,910
dutch
Member
|
Member
Joined: Sep 2007
Posts: 1,910
EURO-zone
|
It will become worser for us as Woff'ers running this GM on a single core game: game mode tested Intresting is that, while other sites only test for FPS, this site also included the CPU load.
Last edited by dutch; 05/15/17 08:07 PM.
|
|
|
#4357564 - 05/16/17 01:26 AM
Re: Windows 10 creators update
[Re: dutch]
|
Joined: Mar 2006
Posts: 2,454
MajorMagee
Member
|
Member
Joined: Mar 2006
Posts: 2,454
Dayton, OH
|
I don't know about WIn 10 Game Mode, but I do know that between Process Lasso Pro, and AnKor's 2017 shader updates, I'm able to run on three out of my four cores now. So much for it being limited to a "single core game".
Service To The Line, On The Line, On Time
US Army Ordnance Corps.
|
|
|
#4357625 - 05/16/17 11:42 AM
Re: Windows 10 creators update
[Re: dutch]
|
Joined: Mar 2006
Posts: 2,454
MajorMagee
Member
|
Member
Joined: Mar 2006
Posts: 2,454
Dayton, OH
|
I've been using the pay once for all time version for many years now. It became a requirement when a computer change moved me from an Intel 2 Core CPU to an AMD 4 Core CPU. The program would start, but as you started to fly in game it would lock up because of core thread conflicts. Using Process Lasso was the only way to reliable block at lest two of the cores from being used so CFS3/OFF would work. It also brought the ability to run in Process Lasso's game mode where the simulation runs with elevated priority over background processes (including TrackIR, and EVGA Precision that are restricted to their own Core).
It was only late last year with AnKor's revised code that he addressed some of the CPU utilization issues, and I started actively testing the performance again. It was during the 2017 changes that I discovered that I could get the game to run on three cores at the same time successfully now (1-3, but not 0). I've rebalanced my level of detail and GPU settings so the three cores run heavily loaded, but not quite maxed out to prevent them falling behind the display rate to prevent micro-stutter because of waiting for the CPU to finish a frame. I also moved to a 3440x1440 G Sync monitor about a year ago to let me go above 60 fps without tearing, and I can get a smooth 70-90 FPS out of my 3.8 GHz processor unless I'm low over an airfield where it drops to 45-60.
The practical effect is that the initial stuttering from loading new objects still exists (I don't have an SSD or a particularly fast buss on the Mother Board), but after that it's typically gone.
Service To The Line, On The Line, On Time
US Army Ordnance Corps.
|
|
|
#4357742 - 05/16/17 10:39 PM
Re: Windows 10 creators update
[Re: dutch]
|
Joined: Mar 2006
Posts: 2,454
MajorMagee
Member
|
Member
Joined: Mar 2006
Posts: 2,454
Dayton, OH
|
Until this year, if I tried to set affinities to use more than 2 cores it would lock up.
I just did some testing and found that the load was spread evenly some of the time, and was biased primarily onto one core at other times. This applied to both WOFF and CFS3. At one point in the testing I thought it had to do with being in the cockpit view or not, but even that tendency wasn't always the case, as I found the reverse to be true at lest once.
Service To The Line, On The Line, On Time
US Army Ordnance Corps.
|
|
|
|
|