I don’t know indian ocean, but I know this effect from north sea: less fps over water then over land. In my case changing from NVidia driver 457.09 to 465.89 helped. You don’t tell your graphics card - maybe you have AMD?
I7-9700 - Windows 20H2
2080TI Nvidia 465.89
32/9 5120x1440
32Go
KPWM Portland east cost to KMVY in emergency land in 28M (Cranland) with 6fps (make me seek :()
Turn off computeur, start again and finish with more than 30fps with PA28 Arrow JF.
8700K delidded and runinng at 5Ghz all cores incl AVX2 totally stable even under extended stress tests.
64GB RAM
1080Ti/11GB
1920x1200 monitor
No problems with any other apps incl heavy timing critical apps like audio studio software.
I think it’s just bugs which have been overlooked as the A-team are now all working on DX12. Meantime the B-team are trying to do the fixes on the old DX11 legacy code to keep this working until DX12 is released later this year.
I notice the dev plan used to say Summer 2021 for DX12, and now only says 2021.
DX12 is totally different monster. DX11 ran addons will have to be recoded for DX12 compatibility. I personally also see dx12 having issues running 6gb graphic cards. Depends how much VRAM msfs will take up. You may not be even able to fly MSFS is you don’t have a 10GB graphic card or more. Gonna be hard to say til the sim is actually on DX12
For your issue on the FPS I have been having drops by 90% at certain time of flight usually 56 mins in I get 90% frame loss for a min and half then it goes back up every 30 to 45 mins after that same issue. Something is triggering a call from the sim that causes it to drop frames.
I dont have the ship addon and the only thing in my community folder is the aerosoft crj550/700
Hopefully this issue will be resolved!
Gonna be hard to find out what the culprit is. We may need DR. Gregory House to find it
Meanwhile the computer itself and any other apps like LNM continue to operate fast and smooth, but it’s impossible to press buttons in the sim cockpit, so I’m iced up and can’t operate the switches to turn icing on, yet the sim isn’t actually crashed. This has been going on for at least an hour now, after 4-5 hours of perfect flight from India to Kuala Lumpar, over the sea again.
Tomorrow I will try again without the Ship AI package active.
Edit : Later… I just noticed the entire sim is running slow, not just fps, but time too. The sim/plane clock on the Garmin is now almost an hour behind where it should be. Hmm.
And I notice that my system is using a lot of ram. I have 64GB physical and no swap file. Anyone understand what committed means - I have 62.6GB committed out of 63.9GB, but still 17GB available. How can it be almost totally committed and stil have 17GB free?
And please, no lesson about needing a swap file. I haven’t used a swap file in all my many applications for many years, and I’m not about to change that just because the sim has a bad bug currently.
Also notice the minimal use of CPU 19% and GPU 12%.
Edit: Later again… I thought I’d try closing LNM. That caused the sim to CTD. So maybe this is a simconnect error with LNM and all the ships in the Ship AI mod? Just thinking out loud.
Will redo the flight tomorrow with Ship AI disabled and see what happens.
Imagine it using dx12 and having to deal with it taking up VRAM and just not being a able to play it… something is calling for it to use all the RAM could be a memory leak like how there was in fsx until lockheed p3d v3 came out and fixed it and it was no longer an issue. Lockheed also made sure that anything in a 50-100nm away from the plane going away would get deleted from the cache in the scenario.