-
Notifications
You must be signed in to change notification settings - Fork 164
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
Play mode error when SteamVR is imported #34
Comments
I've actually ran into the same problem and do not have the confidence in my troubleshooting enough to fix it after trying and failing more or less. I thought it was something on my end. Switched back to the old SteamVR pkg after that for all my VR projects :( |
Hi. On the one hand Assets/TiltBrushExamples directory is extremely old and no longer compiles with the latest SteamVR. Since it doesn't really have anything to do with being able to import Tilt Brush .fbx files into Unity, we'll probably delete it from any future .unitypackages we build. Even without that code, you'll be able to take a fbx, drop it into your Assets folder, and get all the Tilt Brush materials and shaders properly assigned to it. |
Thank you for your help. To clarify, I should import the TiltBrush SDK, except the Assets/TiltBrushExamples. And I should be able to import the fbx file and it will animate/run with the latest Steam VR plugin. |
Yes, that's correct; except the the fbx importer doesn't require the SteamVR plugin. Only that old example code required it. Here are the simplest steps to get up and running:
|
Hello, there is a question I want to ask |
Should be fixed with latest .unitypackage |
Hi, an issue I am having is that when I import the SteamVR plugin, there are a number of compiler errors in the console which prevent me from playing the scene. All I have in the scene is a camera rig, a directional light, and a Tilt brush export. My apologies, I am new to coding, VR, Unity and Github. It seems to work fine before I import the SteamVR plugin.
Thank you in advance!
The text was updated successfully, but these errors were encountered: