November 3, 2025Nov 3 1 hour ago, MarcG said: Like previous betas the early performance benefits have slowly dropped off, did a flight last night and it was more stuttery than I've had during this beta period and this has been reported elsewhere. General FPS was slightly down but still better than SU3s offering, so whilst it may not be fabulous it's still pretty good....just hope it doesn't drop off anymore. Not trying to be contrarian but I flew last night and I thought it was performing better than ever before. Even landing at Heathrow with live traffic was smooth, stutter free and even the runway markings were crisp and in focus...🤷♂️
November 3, 2025Nov 3 2 hours ago, MarcG said: Like previous betas the early performance benefits have slowly dropped off, did a flight last night and it was more stuttery than I've had during this beta period and this has been reported elsewhere. General FPS was slightly down but still better than SU3s offering, so whilst it may not be fabulous it's still pretty good....just hope it doesn't drop off anymore. Weird, on my end I’ve had less stutters
November 3, 2025Nov 3 2 hours ago, MarcG said: Like previous betas the early performance benefits have slowly dropped off, did a flight last night and it was more stuttery than I've had during this beta period and this has been reported elsewhere. General FPS was slightly down but still better than SU3s offering, so whilst it may not be fabulous it's still pretty good....just hope it doesn't drop off anymore. Nope, performance is great. Your setup is messed up.
November 3, 2025Nov 3 Yeah, performance is great. Sitting at LFPG right now, full traffic, 4K ultra, the Fenix, GSX, live weather.. the works. Getting 90-110 fps (framegen on), and it's perfectly smooth. 9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen
November 3, 2025Nov 3 2 hours ago, DD_Arthur said: Not trying to be contrarian but I flew last night and I thought it was performing better than ever before. Even landing at Heathrow with live traffic was smooth, stutter free and even the runway markings were crisp and in focus...🤷♂️ Yeah nice 👍 I think being in VR I'm more susceptible to minor changes in performance as they can become so obvious (as I stated others have also seen a slight drop off since beta began). There's also a million and one other mitigating scenarios, it was the weekend of course so perhaps the servers were loaded more last night. Like I said though it's far better than SU3 so that's all that matters, still room for improvement of course 🙂 Edit: Lots of chat in this thread recently about performance in betas for example; https://forums.flightsimulator.com/t/performance-regression-since-su4-beta-2-stutters-sluggish-panning-lower-fps/ Edited November 3, 2025Nov 3 by MarcG Pico Neo3 Link VR - Windows 11 64bit, Gigabyte Z590 Aorus Elite Mobo, i7-10700KF CPU, Gigabyte RX 9070 XT OC 16gb (AMD GPU), 32gig Corsair 3600mhz RAM, SSD x2 + M.2 SSD 1tb x1 Saitek X45 HOTAS - Saitek Pro Rudder Pedals - Logitech Flight Yoke - Homemade 3 Button & 8-directional Joystick Box, SNES Controller (used as a Button Box - Additional USB Numpad (used as a Button Box)
November 3, 2025Nov 3 The Shift-C pop up has been officially declared a bug, and the fix is coming in an upcoming build (it may not be the next build though): Quote Hi folks, Thank you for all your bug reports. A bug in 1.6.21.0 caused this UI prompt to inadvertently appear in modes such as Free Flight when it was intended to appear at certain moments when playing in World Photographer mode only. The dev team has already resolved this bug internally (pending testing and validation from beta users, of course), and a fix will be included with a future SU4 test build. At this moment I’m unsure if the fix for this issue will be included in the next test build or not, but it will be coming in an upcoming beta build. Thanks, MSFS Team FYI, it was never a design decision and I have no idea why some people were adamant that this was a deliberate design decision by the MSFS team. Edited November 3, 2025Nov 3 by abrams_tank i5-12400, RTX 3060 Ti, 32 GB RAM
November 3, 2025Nov 3 8 hours ago, AnkH said: The "funny" thing (for me, it is more of a sad story...) is: the thread about this Shift + C nonsense quickly got over 1000 votes, while the annoying snow coverage bug present since they introduced snow into MSFS2020 is still creeping around below 300 votes and open since several years. It baffles me how priorities are set amongst simmers nowadays, they are obviously more disturbed by a Shift + C message than generally bugged live weather snow coverage. Interesting... Lets be real here: The Shift+C UI will intrude on you on EVERY flight. The snow coverage you will only notice in summer and when you actually fly where there is no snow in real life at the moment. Edited November 3, 2025Nov 3 by Farlis
November 3, 2025Nov 3 1 hour ago, JonathanC said: Yeah, performance is great. Sitting at LFPG right now, full traffic, 4K ultra, the Fenix, GSX, live weather.. the works. Getting 90-110 fps (framegen on), and it's perfectly smooth. I am really new to this FG thing and DLSS. Can it be used with VSYNC in game with monitor at 50 or 60HZ ? Is it mandatory with your system ? What is native FPS ? Thanks Michael Moe Michael Moe
November 3, 2025Nov 3 14 minutes ago, abrams_tank said: The Shift-C pop up has been officially declared a bug, and the fix is coming in an upcoming build (it may not be the next build though): FYI, it was never a design decision and I have no idea why some people were adamant that this was a deliberate design decision by the MSFS team. Maybe because they have made a few dumb decisions in the past? Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
November 3, 2025Nov 3 11 minutes ago, abrams_tank said: The Shift-C pop up has been officially declared a bug, and the fix is coming in an upcoming build (it may not be the next build though): FYI, it was never a design decision and I have no idea why some people were adamant that this was a deliberate design decision by the MSFS team. Is it any less disconcerting though that this was an actual bug? How much confidence can you have in a software development team, when a bug that is immediately apparent to 100% of the user base upon initiating any flight is released to the general public?
November 3, 2025Nov 3 1 minute ago, PlumCrazy said: Is it any less disconcerting though that this was an actual bug? How much confidence can you have in a software development team, when a bug that is immediately apparent to 100% of the user base upon initiating any flight is released to the general public? jfc there's no talking with you people. It's.. a.. beta It didn't go out to the 'general public' it went out to people who consciously opted into an optional beta. Edited November 3, 2025Nov 3 by Tuskin38
November 3, 2025Nov 3 7 minutes ago, Christopher Low said: Maybe because they have made a few dumb decisions in the past? They have. But this was pretty obviously a bug. They generally don't make new design decisions in the middle of a beta. The design decisions all come when a beta is first dropped. Midway through a beta, they are usually trying to clean up bugs. It's pretty obvious if you pay attention to all the previous SU betas for MSFS 2020, and MSFS 2024. Edited November 3, 2025Nov 3 by abrams_tank i5-12400, RTX 3060 Ti, 32 GB RAM
November 3, 2025Nov 3 2 minutes ago, PlumCrazy said: Is it any less disconcerting though that this was an actual bug? How much confidence can you have in a software development team, when a bug that is immediately apparent to 100% of the user base upon initiating any flight is released to the general public? Released to BETA. Not to the general public! SU3 is the general public release, I hope you UNDERSTAND THAT. Edited November 3, 2025Nov 3 by abrams_tank i5-12400, RTX 3060 Ti, 32 GB RAM
November 3, 2025Nov 3 Yup, it was a bug, which will be fixed in a future release. The 1 minute ago, Michael Moe said: I am really new to this FG thing and DLSS. Can it be used with VSYNC in game with monitor at 50 or 60HZ ? Is it mandatory with your system ? What is native FPS ? Thanks Michael Moe I don't use DLSS for anti-aliasing. Only for framegen. Under Anti-Aliasing, you can choose TAA, FSr3, or DLSS, I use TAA.If you have framegen on, it disables Vsync. Hasn't made any difference to me, I like it with Framegen on. Native frames are half of what I see with framegen, so in my example above it would be 45-55 fps native. Mandatory? No, I could easily run it native, but I like the super smooth feeling I get when I'm getting 130 fps in flight. 9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen
November 3, 2025Nov 3 16 minutes ago, Michael Moe said: am really new to this FG thing and DLSS. Can it be used with VSYNC in game with monitor at 50 or 60HZ ? No. As soon as you go for FG Vsync is disabled.
Create an account or sign in to comment