Solved 4.37 - VR Artifacts and Flickering when Looking Over Right Shoulder
-
Having resolved some other minor issues, I have been able to get BMS 4.37 running in VR on my Quest 2, using the link cable, of course.
However, I noticed something strange as of this morning. When looking over my right shoulder, my VR headset starts to flicker and tear. The image will flicker to pink, black, and then return to normal after simply re-centering my head.
See my quick video of the issue on YouTube here:
Has anyone else encountered this issue? Anyone have a solution? This has been relatively consistent, and I am unsure of the cause.
-
@tsb247 please enable FPS counter and do that again (alt c + f).
Need to see the draw counter.
-
@Seifer - I recorded a new video with the FPS counter. Interestingly, I didn’t expect to see such low frames. Then again… VR.
Please see the link here:
What’s odd is that it was happening all morning, and I was unable to reproduce it for the newest video because the issue seemed to [somehow] resolve itself.
Note: Steam VR had an issue with a plugin at some point during my session, and it restarted and disabled the [standard?] plugin - “Gamepad Support,” or something along those lines. Following the closure of that SteamVR component, the issue seems to have gone away, for now. I’m not sure if there is a connection there or not.
-
Great, you reached the draw call limit. Quite clear, when you look back counter goes up.
Can you upload this mission somewhere so I can debug?
-
@Seifer - I was able to reproduce the issue again. The thing I changed was re-enabling the blocked “Gamepad Support” add-on in SteamVR. The only thing that had changed between the issue and not experiencing that issue was that add-on being blocked.
New Video here:
Question: What exact file do you need? This is a campaign mission. I’m happy to share via GoogleDrive if I know what I am looking for.
Thanks!
-
@tsb247 said in 4.37 - VR Artifacts and Flickering when Looking Over Right Shoulder:
Question: What exact file do you need? This is a campaign mission. I’m happy to share via GoogleDrive if I know what I am looking for.
Please do, (the campaign save file) and tell me which flight to take.
-
@Seifer - I think I have found the correct file(s). They’re from:
[…]\Falcon BMS 4.37\Data\Campaign
Here’s a link to the Google Drive: https://drive.google.com/drive/folders/1RFYe1Igy7lyvEvidxuYnM8tfJuX6sPAL?usp=share_link
If I did not capture the correct file(s), please let me know.
The first flight at the top of the frag order (DEAD) is the one where I am encountering the issue.
Thanks!
-
Thanks tsb247. I took a quick look at the scene (not sure if forum will be able to display it):
What is happening here is that this airbase seems very heavy. Probably a combination of too many objects and too many different textures, which break our batch of draws. Seems to be essentially a data problem
Now, what can be done from the user side. User can disable shadows. Out of 315k commands used to draw the frame, 139k are coming from shadows alone. In VR, things get even worse, because we are drawing the shadow map twice (yes, known issue, working on that).
Oh, and this is with environment mapping disabled, which adds 6 more rendering of the scenes and that F16 is expensive…
My suggestion to you and any other VR players out there (from https://forum.falcon-bms.com/topic/23871/couple-notes-to-vr-users) :
1- disable environment mapping. This is almost mandatory for VR
set g_bEnvironmentMapping 0 set g_bWaterEnvironmentMapping 0
2- If the above is not enough, disable shadow mappings. Yes, this makes a big difference in graphical quality, but at least you get things a lot smoother:
set g_bShadowMapping 0
Yes, I know. Probably not the answer you were expecting. Maybe things will get better in next update, I hope so. Sorry about that.
-
@Seifer - Thanks! I did notice that the issue seems to subside as I got further from the airbase. When I took off, the issue went away, and I didn’t see any more artifacts/tearing. In the interim, I will implement the fixes you listed.
Thanks again! I appreciate the insight, time, and responses!
-
-
-