TheNexusAvenger / Nexus-VR-Character-Model

Maps Roblox characters to the VR inputs of players.
MIT License
66 stars 12 forks source link

Games using latest version of Nexus have broken movement system on Quest 2 and 3 #45

Closed emeraldminer299 closed 3 hours ago

emeraldminer299 commented 3 hours ago

I've noticed in many games using the latest version of the Nexus VR Character Model framework (using ctrl + F9 to check) seem to have broken joystick tracking on the Quest 3 and Quest 2. While yes these aren't MY experiences, it's still a prominent issue within any games containing it on these headsets. I don't see it on any games using an older version of Nexus however. I couldn't really pinpoint this when I added it to an experience to test it but when you move the joystick, say, forward, you'll go left, left goes up, so on so forthe. In games without Nexus VR (aka basic Roblox VR support) however, this is not a problem whatsoever which leads it to an issue with Nexus. If a developer with more experience in LUA than me, feel free to find it, but this is simply a report I'm providing. I can't pinpoint anything due to my lack of skill in reading code outside python.

TheNexusAvenger commented 3 hours ago

As of recent versions of Nexus VR Character Model (V.2.10.0 and newer), non-teleport movement controls are handled entirely by Roblox. Issues with this must be brought up to Roblox on the developer forum. For long-term compatibility reasons, Nexus VR Character Model will not handle character locomotion.