MrFuzzy

Well, I wouldn't say that the Fenix is performance friendly if it lowers your framerate by 25-30% after "adjustments" with respect to Asobo's A320 and the same addons... With Asobo's aircraft, default airport and without FSLTL, I bet that your framerate would be around 40-45 fps with TLOD 200 and your GPU fans would start spinning happily 🙂 Unfortunately these addons are heavy and the 9900K is quite old. I think that what we are seeing here isn't new and there's not much to investigate, really... P.S. Just one more thing: what frequency is your RAM running at?

Welcome to the pit 😄

What about Asobo's A320 @ default EGCC? You killed the external software but you are still using heavy aircraft and airport addons. Are they updated to the latest versions? I was reading that Fenix has improved its framerate a lot in the last version, check it out. I cannot check for you because I don't have these addons, but I haven't experienced any performance loss since WU14.

Same here. Reverted as well and the toolbar at the top of the screen is gone... same for another user. All, be aware that it's NOT possible to revert to the previous build completely. Please vote here: https://forums.flightsimulator.com/t/toolbar-missing-after-exiting-su13-beta/604979/7

I've done all this but SU13 beta still causes some stutters for me... on takeoff and landing, and (seldom) in flight. SU12/WU14 was 100% smooth. Hopefully the final release will not be affected.

It's not a MSFS issue: there's input from one of the control peripherals and the mouse cursor is meant to disappear every time input is detected. It's a feature, not a bug. If that were not the case, people would complain because the cursor stayed and ruined the immersion 🙂 As suggested above, increase the dead zones in the Controls section to avoid background noise from input peripherals.

Avionics can, and hard... do you remember the first release builds in which the glass screens refresh rate was synced with the framerate? A workaround in an XML file made them refresh every two frames and that made us gain 15-20 fps with airliners. Hopefully the stuttering will go away in the following beta updates and the final version.

No info as of now, pointless thread...

Never had any of these issues in 3 years / 1300 hours... but I have the Steam version. I had my logbook wiped with SU5 and SU7 though. It seems that the MS Store version has always been problematic.

I don't understand the point of these manipulations. What's the point of upscaling and then downscaling to get to the same native resolution? I just tried in GPU limited conditions and TAA + native performs much better than DLSS Quality + 1.5 secondary scaling for me.

Between Ferrara and Treviso there are at least 3 versions of Bing textures, depending on the altitude the photos were taken from... AI should prevent such artifacts... https://streamable.com/f6ypap

Maybe a large part of the graphics development team is now working on FS2024? As for server capacity I don't know... the issues are reproducible and come out in the same areas and to the same extent at different times. Look at my Guinea screenshots and the other user's video shot in May. In a route that should have been checked by Asobo because they made that bush trip! Also the tile swapping in the Courchevel area is 100% reproducible and very evident in the corresponding landing challenge. This issue affects so many areas in Europe now... And the tile progressive darkening at low altitude occurring basically everywhere? This is negligence: after 5 good sim updates (6-11) we are again seeing regressions.

I agree with you, my considerations were limited to graphics quality only. Performance, flight model and aircraft fidelity have improved a lot since release, graphics has deteriorated after the XBox version release.

The pre-alpha was particularly impressive... this was 4 years ago:

Yeah, this too is happening much more often lately. I took these screenshots yesterday from the Guinea bush trip, a planned activity that Asobo created in an area where (supposedly) they have flown and should have noticed the issue... This mess was already here in May when another user flew above it, so it's not related to City Update France:

Ugh... I've flown many times in that area in the past and it was OK. The tile swapping issue occurs in many parts of Europe since about 6 months and it got worse after City Update France. There is a thread on the official forum. Please vote here: https://forums.flightsimulator.com/t/aerial-ground-tiles-changing-popping-in/547197/131

With respect to TAA I notice finer detail with DLSS Quality too. What keeps me from using either this or DLAA are artifacts in water... DLAA and DLSS both produce a pixelated band that advances with the aircraft when flying on water. I've taken the below screenshot (crop) just now with DLAA:

I have the Premium Deluxe and the total size of the MSFS packages (the "official" folder) with all the world updates and only the aircraft included for free, is 306 GB.

Yes, and that's one of the things that nVidia Reflex does. If nVidia Reflex is not available for a certain game, you're right: better to manually limit the framerate slightly below the maximum refresh rate of your monitor.

Yes, it does.

I reiterate that with a GSync monitor, VSync intended as "GPU waits for monitor refresh to deliver the next frame" occurs ONLY when the framerate exceeds the max refresh rate of the monitor. Within its VRR range there's no additional input lag regardless of the VSync setting because the monitor always refreshes in sync with the GPU.

GSync tells the monitor to adapt dynamically its refresh rate to the number of fps that the GPU is delivering. But when the GPU delivers more fps than the maximum refresh rate of the monitor, you can have 3 cases, depending on the respective VSync setting: - VSync on: framerate is capped at the maximum refresh rate of your monitor; no tearing - VSync off: framerate exceeds the max refresh rate of your monitor and you have tearing - Fast Sync (nVidia): excess frames are discarded, monitor works at its maximum refresh rate and NO tearing occurs

It is. The refresh rate counter built in in my monitor perfectly keeps pace with the framerate. When you have GSync active, the VSync setting kicks in when your framerate falls out of the GSync range of the monitor. Having a 120 Hz refresh monitor, I have GSync between 1 and 120 Hz and VSync caps the framerate at 120 (116 with nVidia Reflex). If I disable VSync, should the framerate exceed 120 fps, I would have tearing. With GSync + VSync you have GSync in the VRR range of your monitor AND prevent tearing in case the framerate exceeds the refresh rate of your monitor.

LOL My every day experience refutes that, but feel free to use any other settings.

I am using it. With framerate capped at 48 fps, monitor refresh is 48 Hz and it's super smooth. I may leave everything uncapped and run the sim at 70-80 fps / 70-80 Hz but then the fans would get loud with no benefit for FS. When I play first person shooters I leave it uncapped to maximize responsiveness but for a flight simulator it's not needed...