Chronometer broken on A320 and A321 Neos
i couldnāt agree more. When you are in VR such labels are ruining the immersion
Same here. Actually i can say no ctdās in years with MSFS2020/2024. Now Instant ctd when using dev mode.
1.6.19.0 Smooth T/O from KPHX. No extra traffic loitering on the runway. No stuttersā¦..excellent!
Currently running a flight in the PMDG 777-200ER from ORD to SFO. Iāve had some quick audio stutters on the ground and during initial climb, but no actual stutters in gameplay or framerate as far as I was able to tell. Frames are locked at 60 (30 in the sim, plus DLSS framegen). Sim is otherwise running well.
This is my exact setup. 30FPS locked (seems better when I do this in NVCP or app.), then I use lossless scaling to 2x FG that to 60FPS. (Lossless scaling adaptive mode is smoother for me than FSR FG). I also have a 120Hz refresh rate and use DLSS performance mode and output at 4k. This beta 1.6.19.0 is smooth and relatively stutter free for me too. Might be the smoothest SU4 build to date.
Iām wondering if the ground textures have been improved in this version. It feels like the terrain, especially from cruise altitude, looks a lot more detailed and crisp ā I can see more cliffs and definition in the mountains, for example. On the other hand, it seems Iāve lost about 10ā12 FPS. Previously, I had plenty of headroom with the frame rate locked at 45 FPS, but now it sometimes drops below 40, even down to around 36 when flying low and near the cloud base.
Could anyone confirm or refute my observation?
Quest 3 Virtual desktop godlike
Textures ultra, Tlod 220 olod 170
Clouds high, shadows low. Else ultra
Rtx4090, i7-14700, 64Gb
Atc appears to be issuing takeoff clearance so early as if itās by reservation. Atc issued a takeoff clearance to an aircraft pretty much from the tarmac and gummed up everyone else at the runway threshold
It seems that VRAM is being released faster in this beta build. The garbage collection may have been optimized.
Iāve noticed quite a few posts about performance lately. From a devsā and CMsā perspective, it might be more helpful if feedback on performance improvements or degradations was shared in the thread linked below. This way, everything stays in one place and is easier to track.
I also noticed someone reported a CTD. Itās good that itās being mentioned - the more reports, the better.
However, CTDs are considered bugs, and bugs should be reported in a new dedicated thread. You can create such a topic in the section linked below.
Latest Sim Update 4 Beta | MSFS 2024/CTDs topics - Microsoft Flight Simulator Forums
Please donāt take this as a scolding - SU4 beta is really important for all of us (kind of a āmake or breakā moment for MSFS 2024, if I may joke
). Keeping things organized just helps the team track down issues faster - and Iām sure none of us would like them to dig through thousands of posts in this topic just to find one critical bug.
Do you guys have a timeline on when the AMD graphic black blob situation will be addressed? but we appreciate your hard work.
Couldnāt agree more. ![]()
Itād also be super helpful to post the system specs so itās easier to spot any patterns, like whether AMD vs. Intel on the CPU side, or AMD vs. Nvidia on the GPU side, might be influencing things, when half the users are really unhappy and the other half is totally hyped about the same build.
Yeah, I usually go as far as exiting FS, then restarting the system, not just the program. If I donāt, more often than not things are glitchy and I end up restarting anyway.
+1 Iām seeing parts of terminals and the ground flashing white and flickering. Donāt see it at cruise but on the ground it is quite a common occurrence
Iāve read both the introduction to this type of post and the section on performance. Firstly, itās not a bug, and secondly, it doesnāt necessarily relate to FPS, as stated in the description of the performance section. Unfortunately, I specifically mentioned VRAM. Thatās probably not general enough. Of course, I could copy that into the performance section as well. But strictly speaking, according to the definition, it wouldnāt really fit anywhere.
By the way, thereās no need to mention the āDEVā. You can rest assured that youāre not the only one.![]()
Major stuttering with TBM-850 near the ground on landing two CTD and micro stutters with the Tobi looking around - this was a major step backward imo. Suggestions?
The labels that Asobo use are just too much in general. If we damage the landing gear on landing, we need to find out ourselves, like real pilots do. When weāre ouside the plane, we donāt need a constant reminder how to get in the cockpit (very intrusive in VR). If we crash, the plane should crash, it shouldnāt need a message to say weāve crashed, meanwhile resuming the flight. And now the latest one telling us (in VR) that weāre disconnected from the controllers, when any movement of the controller will automatically resume connection. etc.
There should be an option to switch off all such messages.
Iāve been plagued by this CTD since beta .13, itās still happening.19 and seems to be getting more frequent. Iām getting it with nothing added to community too. Yet I know many who have not even had one CTD on these beta builds. I canāt figure it out.
I am getting this wrong direction in .19 at multiple airports. Pain for IFR as you wind up in the wrong direction for a planned route. Good news is that at least at NUQ the AP LNAV did a proper procedure turn in the 787 to get back on route.
I feel this as well. Canāt quantify it, but everything looks a bit sharper. I thought I was imagining it but now Iām sure something has changed for the better.
