We are using Enscape 2.3.2.1447-g5243138a (preview) for Revit 2019, with the Samsung Odyssey. An auto-movement, that is without user input, occurs. The viewer in VR is moved to the 2 o’clock position, with respect to the viewing direction, at a constant speed. There seems to be no way to stop the movement. This occurs also with the current stable Enscape for Revit version.
Framerate and image-quality are otherwise good, on AMD 1700 + 1080Ti, but not being able to stand in a place is inconvenient. A client even reported VR sickness. No such problem with the same file (e.g. Revit demo house) when connecting a Vive.
Demian, thank you for looking into the issue. It does not occur when visualizing models in Unity or Twinmotion with the Odyssey. However, yesterday your firm published a new preview version, and the auto-movement did not occur with that one.
This was just in time for a client presentation. Happy to report they were amazed to see the design in Enscape VR. One of their comments was that ‘it must be cool to be an architect these days’. When everything works properly, your engine graphically dwarfs what’s possible in Twinmotion, and to an extent also Unity. Issue resolved, as it seems.
The issue has reappeared in the current beta. It indeed seems controller related. No auto-movement occurs with just the right controller is turned on. Once the left controller is turned on, a constant movement is triggered. We can make do with just using the right controller. However, having full functionality would be preferable.
I will also use the feedback function. Just posting this here to see if someone else is experiencing this issue. Again, I am seeing this issue only in Enscape (standalone). It does not occur in other VR environments.
I have tried with the last 2.2 and 2.3 versions, and on two different computers, a Razer Blade 15 (1070) and a PC (8700K, 1080Ti). I also tried to enter various scenes from within Revit and as a standalone. Also tried different rooms. The issue keeps occurring, but only in Enscape (not Unreal or Unity).
However, the auto-movement in the 2 o’clock direction of the controller joystick can sometimes be stopped by moving the left joystick ever so slightly in the opposite direction, to counter the movement. The auto-movement then stops for a while on the PC. This can’t be done on the Razer Blade. There, the unwanted movement is constant whenever the left controller comes on.
Hope someone with an Odyssey can join this conversation. I am not sure what’s at fault here, my hardware or the engine.
Based on your description it’s likely that the controller’s slightly miscalibrated and that other applications are using a higher threshold value before interpreting the controller reading as movement input. If you have the chance to test it with a different controller you could verify that. We could of course raise the threshold - we’ll see what is feasible without sacrificing responsiveness for other users.
