LOD Issues in VR in SU3

[mcphailtom]

Thanks @Eddie .... I'm not sure it gets said enough but the work you guys do is great and the continued attention is top notch and much appreciated. Knowing that you're invested as a team is good enough for me 👍

[LineDX]

V1.1.4 SU3.. when open the doors you see across the fuselage. 

[frank_m]

Thats a complete different problem. It has an own thread in this forum. 

[olav1981]

Until a update all my Longhaul planes are gruonded, same shit with PMDG as the A350. The difference is that inibuild works on it, but PMDG customer service and the "clever support" says there, Send reports to Asobo..  its not theyr fault LOL Thank fully Fenix is stil working nicly 

[Fredst321]

Hi everyone,

Same problem for me (LOD issue in VR makes most parts of the cockpit disappear), except I can't apply the fix with shaders cache in Nvidia panel as I have an AMD graphics card. So I will wait for the fix 😉

[frank_m]

The workaround mentioned above has nothing to do with nVidia or AMD. It is a setting in the developer mode of the simulator. 

Edited August 31 by frank_m

[olav1981]

 

Inibuild, is there any new progress with this from your side?

The dev mode setting is terrible for me, yes the plane show corectly but 15-25 fps. So its useless.

Cant fly a stutter plane. 

[Janko]

18 minutes ago, olav1981 said:

 

Inibuild, is there any new progress with this from your side?

The dev mode setting is terrible for me, yes the plane show corectly but 15-25 fps. So its useless.

Cant fly a stutter plane. 

No, all energy and focus is on A340 😛

[Fredst321]

23 hours ago, frank_m said:

The workaround mentioned above has nothing to do with nVidia or AMD. It is a setting in the developer mode of the simulator. 

I knowi was refering to the posts about changing the shaders cache size in NVidia control panel. 

Concerning the workaround in dev mode with Lod's I don't want to try this regarding the impact on performances

So I prefer to wait for the Inibuilds fix 🙂

 

[olav1981]

19 hours ago, Janko said:

No, all energy and focus is on A340 😛

When did i start to listen to well educated Air India pilots LOL..

Indeed the A340 is a nice pice in progress, but we all know thats , its a other team working on that

[bradyoa]

Any news?

[maury1]

New update,

 

Did not fix problem.  May uninstall and try again.

Not optimistic

[mcphailtom]

Still seeing the same issues here as well. Looks "better" but still a lot of holes in cockpit and missing switches"

[mcphailtom]

Almost seems like it didn't make it into the patch despite notes maybe, when I said it looked better I think I was perhaps letting optimism sway my judgement. It pretty much looks the same.

[widgeboy]

Tried the update this morning, hasn't fixed the issue.  Did a clean re-install (deleted all ini files / folders etc) but that didnt work either.

[mcphailtom]

I also tried a complete clean install to no avail

[Simpilot]

Same here no change of problem in VR after installing 1.1.5. Cleared the WASM folder let it build up no change at all. Very disappointing and seems to be not an Addon developer issue alone. Updated the PMDG 777 yesterday. Same effect no change at all.

[mcphailtom]

I think PMDG said they have a few additional changes to come for a complete fix. Looks like it might be the same here

 

[ElRon]

It's a shame that such errors occur, since I believe Inibuild works with Asobo. Surely such problems should be known? I bought the A350 today and was disappointed that it doesn't work in VR at all! I buy planes that don't work. This workaround isn't exactly a good alternative, considering I read later that it causes CTD. So what's the proposed solution from Asobo or Inibuild? Amazing that there are no problems with Fenix!

Edited Saturday at 11:38 AM by ElRon

[Farlis]

Now I know what happened to my PMDG777 in VR. I had the same issue in VR and had no clue what was going on.

Now I see this thread and all makes sense.

[Fredst321]

Hi

Still the issue in VR.

What I did to make a fresh test :

1-uninstall textures optimized pack from inibuilds manager then uninstall the a350

3-clean shaders cache from windows cleanmgr.exe tool

4-clean shaders cache from AMD graphics card control panel

5-restart

6-install A350 without textures optimized pack from inibuilds manager

7-load the aircraft in FS2024 on the 2d screen (not in VR) variation no-cabin : on 2d screen it looks OK

9-switch to VR and still the issue

Note that I don't have these LOD problems with the native FS2024 version of A300-600R, and no problem too with the Fenix A320 (native FS2024 version). With the A321LR Inibuilds, some subtle and far less serious LOD problems depending on distance of the point of view from the panel.

In the A350, distances to display  more detail are inverted in VR : far from the cockpit all parts are displayed and active, in the cockpit, most parts and missing and switches inactive :

-as you can see on the third picture, in the cockpit, most parts are missing

-if you move the camera back to the entrance of the plane (2nd screenshot) you see some textures are now displayed again around overhead panel, highlighted in yellow

-if you move further back, (first screenshot) you can all parts are now displayed and active ! (highlighted in green)

Sorry for the quality of the attached pictures, I took them from VR

Hope this can help Inibuilds team to troubleshoot and fix

Edited Saturday at 02:08 PM by Fredst321

[Philipp Kirchgessner]

Hey everybody,

thank you for the latest A350 update. As I could read the update also included a LOD update. But with VR it still looks as it was before. Will there be further updates to fix this and will the planned A340 be ready for VR in MSFS2024?

[olav1981]

Same issues, just frustrating... 

[Bentree]

Same here....aircraft not flyable in VR. How could they write that this issue was solved in the latest update?

[olav1981]

10 minutes ago, Bentree said:

Same here....aircraft not flyable in VR. How could they write that this issue was solved in the latest update?

Yeah i rected at the same, got werry disapointed, when they say it was fixed, but its still the same, and spendt a hour with reinstalling and tryng to find if the  issue was with me.