Dankovic

Displays are really too dark for me too. It is hard to read anything in top part of displays. But I think that it is HDR issue. That could explain why so many don't have this issue.

Well thats the point... FSHud is stealing focus all the time... So we should just accept the fact that with FSHud we sacrifice GSync with single monitor setup? I know that there is clear technical reason for this. But it should not be excuse. FSHud should implement native msfs window if it is to be concidered functional addon.

But when not interacting with window it shouldt be in focus. If I interact with cockpit it means that msfs is in focus, and fshud window is just shown on top not meaning it is in focus. Anyway addon products should not brake basic platform functionalities. Who knows how many people bought expensive monitors with adaptive sync and not even knowing that with this addon it is not working.

Yes, that makes sense. But msfs window (I run in full screen mode) is in focus in this case. FSHud window si open over the focused msfs window.

Did anyone noticed that when FSHud window is opened or minimized in simulator, Adaptive Sync / GSync is not active? All integrated windows like GSX etc are working fine. My monitor (Coolermaster tempest gp27q) is working at 144Hz, and I lock my frames at 90. Monitors OSD reports 90Hz in simulator. As soon as I open FSHud window it locks at 140Hz ant start tearing and stuttering. I was going crazy for days why my GSync is not working. Until today when I started flight without FSHud and discovered this.

Opted out of beta, beta removed and performance is back. It was just terrible.. micro stutters, frame drops... Maybe they added ton of telemetry and debug version of code. Its ok, but unusable in this state.

SU13 beta hits performance hard. It will be hard to pinpoint this.

Yes... Its a problem. Huge drops that were not there before the update. this drops makes big stutters. Please lets not go to "30 fps is good enough". If it worked before on 90 locked and now we have this drops, something is terribly wrong. I hope its just early beta build. but then, in release notes there is nothing that could impact main engine so hard.

Its a stutter mess for me. With 4090 and FG On in Fenix, cant hold 90fps any more... drops to 30-40 for 2 seconds. Averages on 70 siting on ramp in LOWW. Before rock solid 90. Cleared cache, dxcache.... 😞

For me the main question is, where does this leave current Simulator? Are all fixes and improvements frozen now? Is this it for next 1 year? Why would they spend effort to work on obsolete simulator? For second I could think.. woow.. "they didnt put effort to fix all the issues because they were working on new generation." Time will tell...

Rwy12.. you say you have Frame Generation on!? Thats it. There is no special DLSS3 Setting to set. Frame generation is feature from dlss3. Enjoy your doubeled frames

Oh... this topics for next QA are really making me worry. Missions Localization World Update 12: New Zealand Points of Interest Airports Again, they are putting focus on things that, at this point, should be last priority. I still hope that roadmap next week will show big effort on core simulator.

Well, not going to argue with you. In this case it helped. In my tests, it had big impact even before dlss3. As is should technically.

It is not required to enable FG. GUI will disable FG option only if HAGS is not enabled. But, for it to function correctly is different story. I would suggest for 30 and 40 serie scards to have Resizable bare enabled. Even if not using dlss3.

Great to hear that!!! Hope you are feeling better now about your purchase 🙂 FG is real game changer. If only I didnt buy VR. Now I suffer again with fps and image quality hunting, but can not go back to 2D where after 20 years, finally, all is perfect. I hope that DLSS3 FG will be supported in VR in near future.