If the fix for the landing bug hasn’t been created at the time of the SU beta release, it becomes part of whatever SU Beta cycle that is next. So assuming the SU3 was already planned at the time of the bug being verified, we could eventually see it show up in SU4. And who knows maybe the bug is a much more complicated fix then anyone of us know.
I am currently testing something that was introduced in the dev menu to see if the bug goes away. In dev mode, you can go to debug and select “Use new LOD curve”, which is less aggressive LOD draw and reduces popping of scenery objects and last minute loading. The only problem is it comes at a cost of about 10-15 fps, sometimes 20 if you’re in a very heavy scenery. So for those who are already at 30-40 range without FG, it’s not a beneficial fix. Still testing it out anyway to see if I notice an improvement.
Ahh I dunno. I think if a regression suddenly appears in a beta like this one did in SU2betas, they really should know what caused it and should fix it asap.
There’s no point just doing SU after SU and leaving all the regressions, that’s just adding to the already monumental mountain of bugs there are.
And there are so so many of these regressions. I mean I flew the CJ4 and TBM today to try them, the aircraft look absolutely atrocious compared to 2020. It’s just night and day difference. They need to stop adding new stuff and concentrate on putting everything right. It’s a big old mess.
Regarding the new me LOD Curve. For me anyway, it doesn’t solve the low FPS when very close to the runway, it’s exactly the same.
I flew the PMDG 77F in the newest build today, VHHH - PANC. 9 hours 20 minutes block time, 8 hours 58 minutes flight time, and about 10 hours or so total sim run time, give or take. The only issue I encountered for the entire flight was when I disconnected the AP to land at about 800’ AGL, my cockpit camera began drifting - for whatever reason, the analog thumbstick on my Boeing yoke suffers from inconsistent and unpredictable drift, but only in MSFS 2024. In 2020, I don’t have any problems with it at all. It’s like ‘24 is reading phantom inputs or some kind of cross-talk between axes. I’ve already put a pretty big deadzone in place for that thumbstick but I’m guessing I need to just unassign it entirely.
But the sim was solid from takeoff to landing. I did not attempt to use any AI or 3rd party traffic. I would normally fly with BATC injecting traffic using FS Traffic and FSLTL models but given reports of instability with FSLTL models, I didn’t want to risk ruining a long haul.
I have had this exact issue too. I think in 20 and 24 but can only say for sure in 24. It’s not aircraft specific. I think it’s poor QC on the Boeing yoke TBH
Tell me this- do you also get it if you turn the yoke full deflection? (As if to roll the aircraft)I get it then too but cannot recall which way at the moment.
It may not be related, but I noticed something similar in 2020 when playing with the camera position options (height, center, zoom) and natural head movement.
Try disabling natural head movement and playing with the camera controls to see if the issue recurs.
Toggle ATC Window Button doesn’t activate the window, but i can close the window with the button.
In the Needles Landing Challenge i still have the extreme uplift problem, also a human stands in the middle to annoy me
Extrem performance issues on landing before touch down, weird no problems in the landing challenges.
There are so many problems…
I was quite reluctant to go back to beta again, but after several testimonials that the traffic lights are now quite visible in SU3 BETA, I decided to go back to beta. And the traffic lights really are very good, now I can see the air traffic a few miles away, another really good change for us Brazilians is that the ATC is now speaking good Portuguese, I am very excited about SU3 BETA, so I decided to help Asobo/MS again in the development of this simulator, because now I see great potential for improvement in quality and performance.
Nice smooth flight in the Comanche today, was getting screen tearing on my lg oled without a frame limit, so now locked it to 30fps with AMD fsr x2, so that gives me 60fps.
Is it ok to use AMD FSR with my nvidia card (4070ti super)
Not quite sure if I should be using dlss frame gen.
You can use either. It doesn’t matter. There have been previous posts from some users saying they prefer AMD FSR over NVidia FG. I can’t say because I’m slogging it out on a 3090.
There’s also lossless scaling too which offers 2x and 3x FG, but it sits external. In FS2020 I used to target 20FPS locked then use lossless scaling 3x FG to make that an incredibly smooth 60FPS. It made places like Aerosoft’s EDDF with AI traffic run smoothly for me. I find FG only good if you have a predictable base FPS though. No point in 2x ing something that is sluggish to begin with.
Obscure CTD cause identified, on my system at least: have GSX linked into the sim, and I cannot load the default Asobo Max into the default Gaya KATL. Instant CTD as the Fly Now button appears or starts to appear after loading in.
Oddly, I can load into the same aircraft at KDFW. I can load the PMDG 777-200ER into KATL.
I cannot load the Max into KATL so long as GSX is in my Community folder.
