Reverting back to this version has solved my problems for the time being, which tells me it is specifically a software issue with the most recent update. The issue is only while in Enscape VR.įor the time being, I was able to download Enscape version 3.1.2 +55592 from their Version History page and reinstall it to my system. There are no issues with shaking or tracking in the headset, otherwise. Even taking the headset off and laying in on my desk still causes shaking in the viewfinder of Enscape. It is almost as if the sensitivity of movement in the headset is significantly higher than it should be. The workstation I am using is equipped with an RTX 3080, with the latest drivers, and running Revit 2020.2.5. Unfortunately, with 3.2 installed, the issue persists even with those options disabled. This was initially an issue in the 3.1 update of Enscape, however, disabling RTX raytracing and DLSS would fix the issue. In the REVIT section Canon_WYK /associates notes 2 parts issue:Īfter upgrading to Enscape 3.2 I am experience terrible jutter and shaking within the Oculus Quest 2 via Airlink while using Enscape VR viewer paired with Revit 2020. The issue isn't stuttering in the sense of skipped frames or inconsistent frame-rate, it is more that the head-tracking sensitivity is so high it is like walking around during an earthquake with the whole screen shaking.ĭemian Gutberlet, sorry if you have this already on the list (I need a fix soon). However, in 3.2 the issue is there even with the toggles off. Toggling the features off would stabilize the headset. In Enscape 3.1.2 the issue was only present when the toggles for RTX and DLSS were turned on. I believe it is something to do with the interaction of RTX and DLSS with the Quest 2 over Airlink increasing the movement sensitivity (or something similar). I was able to revert to the previous enscape version and the stuttering is gone, with the Quest 2 over Airlink. The loss of resolution and framerate was significant with the Quest 2 over link cable, however, Airlink has worked nearly flawlessly for me.
I do not have a link cable, currently, as I actually tried to use one and returned it. If Quest2 is still jittery with a cable then it may help narrow down the issue. Trying the cable could eliminate a Variable of the wireless connection.
0 kommentar(er)
