LOD Issues in VR in SU3

[frank_m]

Hi everyone,

In SU3 1.5.25.0, the new LOD curve has also been activated for VR. As it is a significant improvement, I am fairly certain that the curve will be included in the final version of SU3.

Unfortunately, there are some problems with the A350 v1.1.3 and the new LOD curve in SU3 1.5.25.0 in VR: Several objects are invisible and therefore unclickable. It is impossible to start the plane due to the invisible battery switches.

Please see the attached screenshots. By the way, activating 'Debug Model LODs' and setting 'Force LOD 0' shows all objects and the plane becomes operational.

I think it would be worth addressing this issue in good time; otherwise, there will be a lot of complaints as soon as SU3 is published.

Regards,

Frank

Edited August 15 by frank_m

[maury1]

Hi Frank,

 

Tried your fix but it did not seem to work.  Can  you show us your debug screen so I can see exactly what I need to set up?

 

Mark

[frank_m]

It's easy. Please take into account, that this setting will influence the performance, since all objects will be fully drawn all the time.

[maury1]

Thank you sooo much Frank. That took care of it.  I am going to paste this in the Flight Sim forum.

 

 

[maury1]

Hi Frank

 

Again thanks for the tip. I cannot however save the settings. I need to do the fix each time I start the simulator.  Is this normal or is there a way to save these settings?  As always appreciate  your help

 

Mark

[Pepel81]

I have the same issue bout I have not SU3 for me the problem disappears when I choose TAA

[maury1]

Problem still persists in SU3 with TAA

 

At least we have a partial fix thanks to Frank_M

Edited August 17 by maury1

[Rene Feijen]

I can confirm I have the same issue in SU3beta VR.

[Rene Feijen]

The fix works, graphically, SU3 final release. But results in 15 fps instead of 40 fps, making it unflyable. RTX5090 VR. 

Edited August 20 by Rene Feijen

[maury1]

Frame rates for me okay in VR.  Just have to the LOD setup each time I start the Sim. Now that we have the final release hopefully inibuilds we take care of this issue.

 

[Rotorboy61]

Confirming I have the same issue. All fine in pancake mode, multiple missing textures in VR

[kato217]

Same issue here in VR

[ben4muk]

On 8/16/2025 at 11:44 AM, frank_m said:

It's easy. Please take into account, that this setting will influence the performance, since all objects will be fully drawn all the time.

Worked like a charm!  Thank you!  Was growing frustrated with this.

[ben4muk]

On 8/21/2025 at 12:18 AM, Rene Feijen said:

The fix works, graphically, SU3 final release. But results in 15 fps instead of 40 fps, making it unflyable. RTX5090 VR. 

What's your Shader Cache set to in the NVidia Control Panel?  I increased mine to 100GB in non VR and it sorted my stutters.

[Rene Feijen]

1 hour ago, ben4muk said:

What's your Shader Cache set to in the NVidia Control Panel?  I increased mine to 100GB in non VR and it sorted my stutters.

5GB, I have no stutters except for the A350 with this fix applied

[Rene Feijen]

41 minutes ago, Rene Feijen said:

5GB, I have no stutters except for the A350 with this fix applied

 

1 hour ago, ben4muk said:

What's your Shader Cache set to in the NVidia Control Panel?  I increased mine to 100GB in non VR and it sorted my stutters.

Set it at 100GB and now it is smooth!! Thanks!

[MPO910]

Me too seeing this. Also at PMDG777 same issues

[Eddie]

Hello everyone,

We're aware and will get a fix out as soon as possible. The issue is platform-level and affects most if not all native FS2024 aircraft; the way modularity works has changed and we of course need to adapt to said change. No ETAs on a fix, unfortunately, but it is a priority nonetheless.

Thank you 🙂 

[Torchwood007]

driving me insane trying to fly the whole A350 fleet but nothing works in VR - hope you can get a fix for this out soon 🙂

 

[Eddie]

11 minutes ago, Torchwood007 said:

driving me insane trying to fly the whole A350 fleet but nothing works in VR - hope you can get a fix for this out soon 🙂

 

More than understandable! You can pretend you're test flying a factory-new A350 with some panels missing in the mean time 🤪 

 

[ben4muk]

On 8/16/2025 at 11:44 AM, frank_m said:

It's easy. Please take into account, that this setting will influence the performance, since all objects will be fully drawn all the time.

Is there anyway to make the devmode changes stick when we start the sim again?  Right now, I need to go into dev mode and enable active lod's.  Is there anyway to make these changes stick till this is fixed?

[ben4muk]

21 hours ago, Rene Feijen said:

 

Set it at 100GB and now it is smooth!! Thanks!

Glad I could help 😉

[Rotorboy61]

On 8/22/2025 at 6:32 PM, Rene Feijen said:

5GB, I have no stutters except for the A350 with this fix applied

Fix worked for me (thanks!) but now getting CTDs about an hour in 😢

[mcphailtom]

@Eddie Just wondering if you have any take on this one as far as MS/Asobo being the ones liable for correcting the issue? Based on the discussion on the MSFS forums it really seems like at least some of the developers of third party aircraft were taken quite by surprise with this change. Both the A350 and PMDG's 777 are terribly affected and a number of other aircraft like the Citation X perhaps slightly less so but still not unscathed.

Is it really encumbant on you as devs to rework your aircraft if they are already using the SDK correctly? 

I work on a completely different type of software but if we did this to a customer by rug pulling our API with zero notice .... heads would be rolling.

Edited August 24 by mcphailtom

[Eddie]

On 8/24/2025 at 9:24 AM, mcphailtom said:

@Eddie Just wondering if you have any take on this one as far as MS/Asobo beings the ones liable for correcting the issue. Based on the discussion on the MSFS forums it really seems like at least some of the developers of third party aircraft were taken quite by surprise with this change. Both the A350 and PMDGs 777 are terribly affected and a number of other aircraft like the Citation X perhaps slightly less so but still not unscathed.

Is it really encumbant on you as devs to rework your aircraft if they are already using the SDK correctly? 

I work on a completely different type of software but if we did this to a customer by rug pulling our API with zero notice .... heads would be rolling.

Hello,

Unfortunately, the situation is a bit more complex. SU3's beta has been around for a while, and the LOD change has been present for some time. However, given the nature of beta environments, we chose not to rebuild the LODs for the aircraft based on a system that was still subject to change, or potentially addressed by Asobo directly.

This approach does carry the risk that the issue persists into the final release, potentially resulting in a broken feature, which is what happened here. While not ideal, we felt it was the most prudent path given the circumstances. That said, we are actively working on a fix, and it should be in your hands shortly. 

Thank you for your and everyone else's patience 🙂