It's painful, but maybe a reinstall is the next thing to try. I haven't flown enough to know yet if I have the issue or not, but I am having Dev mode issues (and no I cannot turn it off, because then I wouldn't be able to, well... you know "dev")...

 

 

13 minutes ago, Will Fly For Cheese said:

Caught it in the act earlier.

Bimbling about in the skies over Surrey earlier at 60 FPS or so when it tanked down to 15-20 FPS. Opened Task Manager and saw the GPU was on the floor and the CPU was at 94%.

Where I've drawn the red line on the left is where the frames suddenly recovered back to 60 FPS and you can see at a glance how the GPU has recovered and the load has come off the CPU.

 

 

 

Nice catch. Very interesting that CPU drops and GPU increases when the issue is recovered. 

CPU is usage usually goes up when there's complex scenery to render, like in urban areas. But this thing is happening everywhere, in rural areas, urban areas, in mountain ranges and in flat areas. There's something weird introduced with the latest update. This needs a hotfix.

Just now, Republic3D said:

Nice catch. Very interesting that CPU drops and GPU increases when the issue is recovered. 

CPU is usage usually goes up when there's complex scenery to render, like in urban areas. But this thing is happening everywhere, in rural areas, urban areas, in mountain ranges and in flat areas. There's something weird introduced with the latest update. This needs a hotfix.

Yah, that's interesting, some code they added in last update could have performance issue with CPU. Could also be they changed the streaming algorithm to be more real-time, can you turn off Bing and see if it still happens?
 

3 minutes ago, Alpine Scenery said:

Yah, that's interesting, some code they added in last update could have performance issue with CPU. Could also be they changed the streaming algorithm to be more real-time, can you turn off Bing and see if it still happens?
 

For me, my gpu will go down to about 40% usage and then it goes back up

Just now, devgrp said:

For me, my gpu will go down to about 40% usage and then it goes back up

Maybe the driver. I think I'll roll back and see...

4 minutes ago, Republic3D said:

Nice catch. Very interesting that CPU drops and GPU increases when the issue is recovered. 
 

The CPU and GPU recover to the normal states of % utilisation. The GPU should always be running at greater utilisation than the CPU. It just demonstrated that the sim has recovered it's frames by correctly utilising the appropriate amounts of power from each of the processors.

During the tanking - yep, GPU seems to go in to some sort of fit and fall to the floor and the CPU looks like its taking the load at near 100%. That's bad news for temps and my old 4790K - that's been trying to retire for a couple of years now.

8 minutes ago, jarmstro said:

Maybe the driver. I think I'll roll back and see...

Don't bother - I've tried 3 different nVidia Drivers today and they all manifest the same circumstance with only the odd 2-4 FPS difference starting with rolling back from the latest to the famous one; 457.30 then the current one then one from a month ago. Same result each time. From that testing I deduce (my dear Dr Watson) it's not a Driver issue.

Edited March 11, 20215 yr by Will Fly For Cheese

I dont know why everyone is looking to tinker with their systems looking for a "fix" when the fix needs to come from the developers. If your systems were running fine before World Update 3 and post World update 3 you now have utilization issues then what makes people believe that changing drivers and tinkering with stuff is going to fix it ?

I understand the frustration and desperation but really. The solution needs to come from Asobo.

Just make sure you all send in your zendesk reports to show that this isn't some rando run of the mill pebcak error and they cant brush it under the rug. Like they tried to do yesterday with that farce of a twitch update.

Edited March 11, 20215 yr by Maxis

10 minutes ago, Maxis said:

I dont know why everyone is looking to tinker with their systems looking for a "fix" when the fix needs to come from the developers. If your systems were running fine before World Update 3 and post World update 3 you now have utilization issues then what makes people believe that changing drivers and tinkering with stuff is going to fix it ?

I understand the frustration and desperation but really. The solution needs to come from Asobo.

Just make sure you all send in your zendesk reports to show that this isn't some rando run of the mill pebcak error and they cant brush it under the rug. Like they tried to do yesterday with that farce of a twitch update.

You're exactly right 

16 minutes ago, Will Fly For Cheese said:

Don't bother - I've tried 3 different nVidia Drivers today and they all manifest the same circumstance with only the odd 2-4 FPS difference starting with rolling back from the latest to the famous one; 457.30 then the current one then one from a month ago. Same result each time. From that testing I deduce (my dear Dr Watson) it's not a Driver issue.

Ah! Thanks. 

My FPS was in the drink stuck at 8-15, just after the update, until I restarted the computer.  Then It came back to somewhat normal but had spikes off and on. Avg was around 40-50 with the occasional quick spike down to mid 20s. Did a successful flight albeit inconsistent performance wise.    I dont use Vsync, and have unlimited frames. Using Freesync. 

So this problem is still going on? I thought it was server side? Have Asobo even addressed it yet? 

10 minutes ago, fakeflyer737 said:

So this problem is still going on? I thought it was server side? Have Asobo even addressed it yet? 

They addressed it and put brushed it off as if it was only affecting a few systems.  Are you affected ? If you are did you zendesk it as yet ?

3 minutes ago, Maxis said:

They addressed it and put brushed it off as if it was only affecting a few systems.  Are you affected ? If you are did you zendesk it as yet ?

They never said they addressed it - what they talked about was whether they could hotfix it. Mods on the official forum said it is still under investigation.

4 minutes ago, DylanM said:

They never said they addressed it - what they talked about was whether they could hotfix it. Mods on the official forum said it is still under investigation.

 That's addressing the issue. If they didn't bring it up at all then they didn't address it.