I’m really just wondering why it has the small hit on FPS. I like the feature but rarely use as I’m trying to maximize frames.
Will this ever be entirely fixed?
Are you talking about when it’s displayed in-cockpit? Anything that needs to get rendered and updated in real time will impose a CPU/GPU load and have to be paid in FPS.
No. just having the option ON in the menu bar, not even using it. The hit is most noticeable in glass cockpits (787 in particular). It’s gotten way better though.
I’ve never noticed a material drop in FPS and VFR is always on in my toolbar, but I fly mostly GA and some of the small bizjets. On the Longtitude and TBM, which have the max number of Garmin screens, I don’t see a difference with it on or off.
The jetliners are already imposing a huge fps load because of the sheer amount of glass instruments, so it’s hard to say if it’s related to the type of aircraft as well.
Yeah, in little things like that it’s fine. At it’s worst (pretty much release day) there was a 14FPS hit in the 787.
There are ongoing issues with the UI and secondary displays causing performance penalties. Either the UI library or the sim’s use of that UI library is not optimized. It’s just another part of the sim that needs more work.
My advice would be to disable the UI toolbar buttons that add the VFR map (and other features you don’t use), and use Little Nav Map instead. Since it runs on a separate process outside the simulator, it’s using CPU cores the sim can’t currently take advantage of, so the performance hit should be negligible if there’s any at all.
I’m actually hoping that the DX12 upgrade breaks the UI or their render loop in such a way that they’re forced to revisit this issue, but also multiple displays.
While the window is closed, the CPU still has do some work keeping the map pane updated as the plane moves around. If it didn’t, there would be a small delay (and stutter) each time you opened it.
I suppose this background rendering is disabled when you remove the feature from the toolbar.
Having said that, something tells me the thing could benefit from some optimization. Maybe already in in SU5, who knows?