How come all us users find incredibly obvious issues but Asobo is clueless?
The assumption there is they didnât find them.
1 Like
ok thx , I will take a look
I seriously doubt they are clueless. Itâs something else.
2 Likes
Yes..I tried identical flights, identical everything and got 45 to 50 fps in both windowed and full screen mode and VR with a RTX 3080 Card , i9, 64Gb Ram.
It is something I have never even considered a performance hit and would have thought windowed might be less resource hungry not the other way.
Quick trip on the googleâs⊠Windows 10 Full screen optimizations might have something to do with this. Will have to play with it when I get back in town.
should note, Iâve never messed with this on the exe or in windows settings; fresh install to boot, but worth a look I think:
Asobo / MS Also recommends shutting this off:
Now Iâm really curious. 
Anyone else getting extremely low frames on third party aircraft? (only LOD 00).
For example, Iâve loaded my own aircraft, the DR250 Capitaine. Things are going ok for a minute or two, but as I look around the cockpit I notice the frames quickly dropping to 10fps, the ms under that going to 100ms, and MainThread shooting up to 200ms if it can get there.
Normally I get 50fps with only a 10ms burden on the mainthread, with a simple aircraft like this.
This wasnât an issue before the hotfix, and itâs doing my head in!
Loading to a different aircraft from the aircraft selector in the dev menu resolves it. But Iâve completely rebuilt the aircraft using the DR400 elements, except the changed model, with the same result.
Changing between windowed and fullscreen increases the FPS for 1 second, then it comes right back again.
Anyone else seeing this?
Still good after looking around.
As soon as the aircraft moves, especially if I look around, it all turns red.
All other items have been removed from communityâŠ
I think the ATC altitude bug is back! After WU6 it was definitely gone but after the hot fix I am seeing again. Iâm being informed by ATC that I am for example â300â below assigned altitudeâ despite altimeter being set correctly and cruising at assigned altitude. Anyone else getting this?
1 Like
Are you flying over mountains, or flat terrain ? There seems to be a relation with ground level.. I donât use ATC myself, but Iâve noticed the 500 Feet warning repeat more often over mountain terrain. Especially when I use elevator to fly low.
@Parorng canât confirm with Goose, I run only ONE third party freeware aircraft, Grumman Goose. Frame rate is slower than Cessnaâs but I donât see 10FpS over Skerries, with the Goose. And it remains flyable >20min, I did not keep the FpS counter on all the time.. so I canât be sure if it keeps proper values during flight.
Btw itâs interesting you have this bug AND also the source code of the aircraft and (Wasm? Html?) gauges. Maybe thereâs a way with trial and error to pinpoint the cause of the issue ? Work around it.. update it..
Windowed and full screen should not make any difference. There is no true full screen as we remember from previous games. The âFull Screenâ mode in MSFS is merely a borderless full screen window.
That would be why it is called, âFull Screen Windowâ mode.
Just replaced everything with the default DR400, except for the airframe model. Itâs something to do with that model I guess (or the Blender export of it), as everything else is identical to the DR400âŠ
Itâs only affecting it on the ground, when youâre moving, AND looking around. The performance doesnât restore if you then get airborne, or stop looking around. This doesnât happen on the DR400 though! 
BUT, reselecting the aircraft from the Aircraft Selector restores its performance again. If youâre in the air (never touching the ground), you can look around and no issues whatsoever. Once you land though, back towards 10fps!
Very strange indeed. Ugh!
Edit: Further testing - replaced the whole model with the DR400 one again - itâs not the model lol. 
Bed time - SU5+ has been a disaster for me!
For a very specific case
Having your monitorâs DPI set to a value other than 100% can cause issues with Microsoft Flight Simulator.
I like the âhelpâ they provide. First step: Find Flight simulator.exe
Well good luck with that, itâs buried and hidden in read protected folders 
Not that easy to find the executable without a bit of workâŠ
1 Like
DISABLE FULL-SCREEN OPTIMIZATIONS
Having your monitorâs DPI set to a value other than 100% can cause issues with Microsoft Flight Simulator. As such, we would recommend disabling display scaling on high DPI settings for Microsoft Flight Simulator.
To do this, follow the steps below:
- Find FlightSimulator.exe.
- Right-click on FlightSimulator.exe and select âPropertiesâ from the pop-up menu.
- Select the Compatibility tab.
- Select Change high DPI settings and then select the Override high DPI scaling behavior. Scaling performed by: Application check box.
Yes, sure, âhow can I access the folder where FlightSimulator.exe is locatedâ would be the most important step to put first in my opinion, unless of course Zendesk is officially recommending indirectly that all FS2020 customers should have been wiser purchasing the game on Steam rather than on the MSStore?
2 Likes
Yes, exactly. And that is the correct approach.
But you agree that it can get it so filled over and pumped up with mods that all the work by the devs to harmonize its components, make stuff more stable - just isnât relevant anymore.
The WU6 including this 1.19.9 patch are very good, developers are trying.
But then, slap a couple of mods like this one I mentioned up there - who can guarantee it will still all work well just the way the devs tweaked it.to?
1 Like
Yes - partially, I am not sure yet, but after I reset all the Assistance settings to âTRUE TO LIFEâ and thus completely disabled the AI piloting - not a single issue anymore.
Still, I would like to try a few more things. Did you work it out on your machine ? Any changes ?
Anybody having issues with ATC on xbox? Not getting hardly any climb/descend instructions for my flight plan. Didnât have that before WU6.. 
Itâs not bad advice tbf, the Microsoft store always has been a dumpster fire.
