-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Installation Failure Due to Space in Destination Path #2
Comments
As a temporary work around, open the installer with the |
Worked like a charm. Thank you for your help. |
Another notice related to pathing shenanigans. It would appear that is is unable to find any of the sound assets when using the application itself. Are the paths being used for them relative or absolute? My assumption is the latter. Perhaps going to relative pathing would alleviate most of the issues whilst running the application itself? |
The current version doesn't support wide paths, please make sure you've installed it in a path like |
No insinuation intended. It's just that relative/absolute pathing is something I noticed that always gets overlooked in the speed of development (from personal experience lol). Thank you for the information. |
Fixed internally; fix will be pushed in next update. |
I am going through the process of getting Amethyst installed and it is stalling on the "registering SteamVR Addon" section. I have determined that it is a result of the space in the installation path. Thinking about it, if this issue is present in this step, any other subsequent steps using the same path would also likely fail.
I would prefer to not have it in the root directory for organizations sake. (Though I have done it for the sake of testing)
Error message for reference.
F20220918 11:29:02.143900 13148 OpenVRUtil.Drivers.cs::RegisterSteamVrDriver:50] vrpathreg failed: Code: -2 Args: "adddriver D:\Program Files\Amethyst\Amethyst"
Let me know if you need any other log information, though I think the cause for this issue is fairly straight forward.
The text was updated successfully, but these errors were encountered: