Closed hoverAdev closed 1 year ago
Both tools (VCC and CLI) were downloaded and installed today. VCC is version v2.1.1 and CLI is version 0.1.16, which should be the latest at time of writing.
I am also experiencing this issue. I am a new user to CreatorCompanion and the VRChat SDK in general.
After clicking 'I already have Unity' on the next page and selecting Unity.exe in my D drive, this error shows up:
I am also running Unity 2021.3.24f1.
Closed to merge issue with #305.
Describe the bug Creator Companion / VPM CLI refuse to recognize my Unity installation, despite
vpm list unity
not encountering the issue. Using the 📂 icon in Creator Companion to select the editor fails as well. The same error occurs when manually setting the path insettings.json
, in which casepathToUnityExe
will be reset to""
.To Reproduce Steps to reproduce the behavior:
Expected behavior I expected any of the tried methods to correctly identify and set the Unity Editor path.
Screenshots
Desktop (please complete the following information):
Additional context I believe the most likely points of error are the fact that the version of Unity (2021.3.24f1) may be one that is unsupported, and that is somehow causing an error. However, I do not know what in the nature of this newer version would cause this. Another possible failure point is that Unity is installed in a nonstandard location, and not on the C drive. If VCC cannot recognize Unity installations on secondary drives, such as my G drive, that could also be responsible for this error. Lastly, it is of note that I am running Windows as a guest VM under Unraid 6.11.5. While I cannot imagine how this VM status would cause this error, it is true that VRC does not run on this guest, which likely makes it very different from the typical setup used with VCC.