Hi. Also a vote from my side. Pimax 8K user
This is a very short request to fix the frustum culling projecton calculation when in VR using any headset with none parallel displays. It is not an OpenXR dependancy; please do not confuse this request!!
Currently when using any VR HMD with none-parallel displays MSFS frustum culling is incorrect causing artifacting at the edges of the display, very likely due to the way the in game code reads and incorrectly processes the projection matracies provided by OpenXR without respecting the cantered panels. This seems like such an easy fix but without it all HMD’s with none parallel displays dont work properly unless using a compatibility mode workaround which uses circa 30% rendering performance overhead.
It is something which was brought up in a previous thread which has well over 70+ votes but which seemed to be misunderstood by the MSFS support team & as such I please request your development team read this again.
All information is available on the previous thread here, please take time to read this, particularly towards the end of the thread: Support for Wide FOV VR headsets (removing Frustum Culling issue)-
Please also take note the VR Development Update never showed that this issue was raised as it only ever noted 2-3 votes when in fact this post had over 70 and there are several other threads around the forum related to the same issue.
Thankyou very much for your time and for considering this,
Just give this a push up. Pimax 8K and Index user here. Please support canted displays with wide fov natively as well as improve the aggressive culling. This totally kills the otherwise fantastic experience in this sim. Nothing to do with OpenXR or SteamVR. Thank you.
Asobo and Microsoft please look into this VR FOV issue.
The new VR integration into MSFS is just incredible. VR really brings this already fantastic flightsim experience into a completely new world of realism, but for the wide FOV headset owners this bug is killing us.
Please look into resolving this issue for us VR flight simmers
Pimax please fix this… 8KX user…
I believe this is a more general VR problem solely due to FS2020.
In effect, with the last few SteamVR version you can limit the FOV and when I reduce it to 50% in SteamVR with the Index, I can see FS2020 is over-culling the objects too early on the sides. In other words: with SteamVR FOV set to 50% trees (for example) are disappearing before reaching the edge of the view when turning the head around.
NB: In my opinion there is a logical possibility the game could be under-culling objects with any VR device with more than 90 deg FOV therefore. If this is the case, the game could actually be delivering lower performance in VR because it would be processing unnecessary objects.
NB: The inverse effect if happening with the selection of object LODs. In short, it displays highest details (lowest LOD) if the object is at 45 deg from center, and the next LOD (lowest details) if the object is at the center.
Here are more details about this (with screenshots):
LOD Problems - Distances revisited - #38 by CptLucky8
I don’t know whether this has anything to do with the many other LOD problems, but it seems these are still prevalent and still not fixed.
- 61475 Photogrammetry, Ground Textures and LOD ring distances
- 66041 Vegetation impostors/objects ring distance algorithm failing in HIGH or ULTRA depending on the species.
- 70848 Terrain LOD distance is using the square root of its value.
Well, it runs ok with my 8kx, but only with deactivated parallel projection. So there always is “cullum frustrating” visible in the sim. That is so sad, because it disturbs the immersion badly.
So please, it should not be too difficult, to support wide FOV. The MSFS is, where the 8kx can shine… right now very rough around the edges. So Asobo… this can be done without too much trouble. And never underestimate the number of VR users. The next generation of hedasets will bring bigger FOVs. So this is needed.
Thanks for your hard work in advance!
Moderator Edit: Merged from another topic.
Frustum culling creates the issue where the left and right edges of the FOV are “flickering very badly”, I think it is a function of the geometry appearing and disappearing on the edges of the MSFS camera frustum for optimization purposes.
In order to fix it we have to enable the parallel projection inside the PiToll, that would be ok if it did not take a significant toll on the FPS.
Can MSFS fix this issue for VR HMD with large FOVs.
If you experience the same issue, can you please vote.
I just got a response from a Zendesk ticket I opened concerning this exact issue I have with my 8KX.
What a disappointing and weak response I got from them.
Basically, not our problem cause Pimax does not support OpenXR (so false), take it up with Pimax not our responsibility
What a way to run away from supporting your customers.
You might want to reopen your Zendesk ticket because what I’m documenting above has nothing to do at all with Pimax.
I’m documenting FS2020 object culling algorithm is wrongly culling objects prior they reach the culling planes to the side when setting SteamVR to 50% FOV with an Index.
I’d suspect the same algorithm isn’t culling objects after they reach the culling planes to the side when using more than SeamVR 90% FOV with an Index, therefore leading to poorer performance processing necessary objects.
PS: Actually other similar problems manifest themselves much closer right in the cockpit. This might have nothing to do with frustum culling itself, but it might be related to more general LOD/culling problems:
TL;DR: object visibility depends also on the viewing angle, it might be visible at 45 deg to the side and disappear when viewed directly at, while being at the same relative distance to the eye in both cases.
My Zendesk ticket is about the Pimax and the frustum culling issue that forces the use of parallel projection.
They keep giving me the same answer every time I reply to their response to the ticket:
“Pimax does not support OpenXR natively therefore not our responsibility, talk to Pimax”.
I have talked to the proper people at Pimax about this issue, they have confirmed it is an issue MSFS has to fix on their side and has nothing to do with OpenXR.
I have found good threads on this forum that are reporting this issue for Pimax.
I’m out, I will patiently wait and hopefully they will resolve this issue someday.
Any further news on this, have they mention it at all in blogs or interviews etc?
With SU5, there is still the culling problem but this time it has shifted sides!
With SteamVR FOV 50% and the Index:
Before: it culls the objects too soon at the outer edge of the views (left on left view, right on right view).
After: it culls the objects too soon at the inner edge of the views (right on left view, left on right view)
Unfortunately Pimax just posted on their forums they reached out to Asobo and were informed they have no interest in a collaboration with them so it sounds like Asobo has absolutely zero intent in supporting wide fov headsets…
and a few months later:
so what’s next?
Pimax maintains its Asobo that needs to fix it and Asobo maintains that its Pimax that needs to fix it meanwhile were left with no solution and seemingly nothing being done by either side to remedy this.
Pimax might have something to do on their end, it doesn’t change the fact FS2020 code is wrongly culling out objects and this shows with the Index for example.
Prior SU5, when using a FOV < 90deg, you could see Trees culled too soon at the outer edge of both eye.
Since SU5, when using a FOV < 90deg, you can see Trees culled too soon at the inner edge of both eyes!
There is definitely something wrong here, and I wouldn’t be surprised there is a link with this FS2020 bug and another one: [BUG] Shader code ‘viewdir’ and shadow/light rendering are inconsistent on right eye
The Culing in the Pimax in FS2020 is on a completely different level. Huge blocks are shifted around 15-20% of the field of view. The angle of canted displays of the index are significantly smaller. and the index is automatically maintained by PP, so that it hardly appears there.
And yes, the problem can only be solved by Asobo, by changing the viewports. A little intervention.
Other software manufacturers using OpenXR have also solved it quickly. But apparently Asobo has little interest in supporting some hardware that is not branded by its client. At least that’s what it looks like for me.
“Will be examined” When?
@OlieTsubasa443 Any update on this at all please? From the sounds of it Pimax seem to believe Asobo are unwilling to resolve this problem, despite Pimax themselves offering to assist Asobo with how to fix the problem. https://community.openmr.ai/t/vr-game-x-pimax/36634/2
Yes, we need a solution soon as possible. Any work around until then ?