Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Controller models fail to render in mono builds using unity 2022.3 #1095

Open
dfitt opened this issue Jun 23, 2023 · 3 comments
Open

Controller models fail to render in mono builds using unity 2022.3 #1095

dfitt opened this issue Jun 23, 2023 · 3 comments
Labels
Needs more information This issue needs more information before we can handle it

Comments

@dfitt
Copy link

dfitt commented Jun 23, 2023

Everything is fine in the editor, but controller models fail to show in builds (usually). Building with il2cpp fixes the problem.

It looks like steamvr is getting garbage strings from openxr for things like trackingsystemname and controllernames at first. Could be a load order issue.

You can repro by creating a new project in 2022.3 using the vr template. Then install steamvr. Go to player settings and set "allow downloads over http" to "allowed in development builds". Switch to the steamvr sample throwing scene. Controller models work in the editor, but will usually fail to show in a mono build.

@zite
Copy link
Collaborator

zite commented Aug 25, 2023

I wasn't able to reproduce this after launching a mono build a dozen or so times. If you're still seeing this can you post a steamvr system report (directly after the issue happens) and the unity log?

@zite zite added the Needs more information This issue needs more information before we can handle it label Aug 25, 2023
@dfitt
Copy link
Author

dfitt commented Oct 3, 2023

Sure - logs attached.

The mono build of the throwing scene did not show controller models and the held ball did not track with controller motions (but throwing still worked). The il2cpp build was fine.
Failure_monoBuild.zip
Success_il2cppBuild.zip

There's another unity user with the same issue here:
https://forum.unity.com/threads/steamvr-showing-wrong-headset-id-controller-render-models-showing-in-editor-not-in-a-build.1498628/#post-9384725

@MiddleManGames
Copy link

Yeah I'm having the same issue. Here's where I am with it.

I'm trying to use the SteamVR render models to display the controllers in game. This works fine in the editor and shows the right models. In a build the tracking and input is still fine, but I don't see any controllers.

I'm using the standard steamVR rig. I've tested with the sample scene included with the plugin and it's exactly the same. I've tried uploading to steam and running as a steam app and it's the same.

The problem seems to be how steamVR see the headset. In the editor I get this:

[SteamVR] Initialized. Connected to oculus : Oculus Rift CV1 : WMHD283N4005TS :: rift

In a build I get this:

[SteamVR] Initialized. Connected to 捯汵獵 : 捏汵獵删晩⁴噃1 : 䵗䑈〳丳〶㔰䙅 :: 楲瑦
[SteamVR] [Model] Render model does not support components, falling back to single mesh.
[SteamVR] Failed to load render model 捯汵獵损ㅶ损湯牴汯敬彲敬瑦 - InvalidModel
[SteamVR] [Model] Render model does not support components, falling back to single mesh.
[SteamVR] Failed to load render model 捯汵獵损ㅶ损湯牴汯敬彲楲桧t蹄䐄Ώਜࡄ䐃Јࡄ䐅ఈࡄ䐍จࡄ - InvalidModel

If I delete the 3 SteamVR folders from assets and load the project, then uninstall and reinstall OpenVR, then reinstall the SteamVR plugin, come out of safe mode, and do a build... then the build if fine and has controllers.

If I then restart unity and do another build, the build does not have controllers.

If I use a build that works and apply the steam DRM to the exe (even in compatibility mode), then the controllers stop working.

I've now tried using IL2CPP based on this post, and the build was fine, but again adding DRM breaks it.

In all these cases I have saved the builds and can consistently load them with the same results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs more information This issue needs more information before we can handle it
Projects
None yet
Development

No branches or pull requests

3 participants