question

The newer Oculus and Vive still have the same controllers as the older versions. All of the VR controllers are pretty standardized at this point. The main differences in newer versions vs older versions of VR headsets are improvements in the motion sensors and display (less screen-door effect). See Does FlexSim support the new Oculus Rift S?

If you want to change how you move around in VR, you are welcome to change how you move around. You don't have to use the default teleportation mechanism. The movement code for 3Dconnexion mice, Xbox controllers, and VR controllers is defined in the tree. You can see and modify it however you want.

See the following nodes in VIEW:/standardviews/documentwindows/Perspective>eventfunctions

• OnPreDraw (calls the input functions below and sets a timer for repainting when the model isn't running)
• OnDraw (draws the VR teleportation indicators)
• XboxInput (controls the view based on Xbox controller inputs)
• TouchInput (controls the view based on VR controller inputs)
• OnStick (controls the view based on 3Dconnexion mouse inputs)

My VR headset recommendation for FlexSim right now is the Oculus Rift S. That’s what we use in our office and at conferences where we demo VR with FlexSim on laptops.

The Oculus Rift S runs smoothly at 80 FPS with asynchronous spacewarp kicking in if you drop between below 80 FPS.

Other VR headsets (such as the HTC Vive and Windows Mixed Reality headsets) require 90+ FPS in order to avoid headache-inducing judder.

Because the Oculus Rift S uses asynchronous spacewarp, you can render bigger models more comfortably than you can with other headsets. With other headsets, you need to be very careful with optimizing your model’s framerate to ensure that it stays above 90 FPS.

For example, if your model runs at 30 FPS, it will feel laggy but workable in an Oculus Rift headset. In another headset, the view will feel so slow and broken that you will want to remove the headset as fast as possible.