creator-companion icon indicating copy to clipboard operation
creator-companion copied to clipboard

[BUG] VPM cannot find supported editor for 2022.3.6f1 on Linux

Open Foxcapades opened this issue 1 year ago • 28 comments

Describe the bug

NOTE This is a new behavior as of 0.1.21 and persists in 0.1.22.

When executing VPM it does not use the editor as configured in the settings.json file. Instead, when executed it throws this error:

[14:27:43 INF] Found No Supported Editors
[14:27:43 INF] Unity is not installed.
[14:27:43 ERR] No Unity Editor found, you need to set this before you can make new projects.

Additionally, during execution it modifies the settings.json file and removes the value set to the pathToUnityExe key.

To Reproduce

  1. Install VPM
$ dotnet tool install --global vrchat.vpm.cli
Tool 'vrchat.vpm.cli' was installed with the latest stable version (version '0.1.22').
  1. Configure ~/.local/share/VRChatCreatorCompanion/settings.json
  1 {
  2   "pathToUnityExe": "/home/ellie/Unity/Hub/Editor/2022.3.6f1/Editor/Unity",
  3   "pathToUnityHub": "/opt/unityhub/unityhub",
  1. Execute vpm new.
$ vpm new Zoe.1 Avatar -p $PWD 
[14:27:43 INF] Found No Supported Editors
[14:27:43 INF] Unity is not installed.
[14:27:43 ERR] No Unity Editor found, you need to set this before you can make new projects.

Expected behavior

$ vpm new Zoe.1 Avatar -p $PWD
[14:36:31 INF] VPM Doesn't know how to look at Linux executables for version yet, so just returning true for PathIsValidUnityVersion(/home/ellie/Unity/Hub/Editor/2022.3.6f1/Editor/Unity)
[14:36:31 INF] VPM Doesn't know how to look at Linux executables for version yet, so just returning true for PathIsValidUnityVersion(/home/ellie/Unity/Hub/Editor/2022.3.6f1/Editor/Unity)
[14:36:31 INF] Unity is installed.
[14:36:31 INF] Let's create a project named Zoe.1 from the template /home/ellie/.local/share/VRChatCreatorCompanion/VRCTemplates/Avatar at the path /media/ellie/Ashley/3D/Projects/Unity/Zoe.1
[14:36:31 INF] Looking for Legacy Packages to Upgrade by Scanning Folders within com.vrchat.avatars
[14:36:31 INF] Looking for Legacy Packages to Upgrade by Scanning Folders within com.vrchat.avatars
[14:36:31 INF] Looking for Legacy Packages to Upgrade by Scanning Folders within com.vrchat.base
[14:36:31 INF] Resolved package com.vrchat.avatars ^3.5.x
[14:36:31 INF] Resolved all VPM Packages in /media/ellie/Ashley/3D/Projects/Unity/Zoe.1
[14:36:32 INF] Looking for Legacy Packages to Upgrade by Scanning Folders within com.vrchat.core.vpm-resolver
[14:36:32 INF] Looking for Legacy Packages to Upgrade by Scanning Folders within com.vrchat.core.vpm-resolver
[14:36:32 INF] Successfully resolved packages for new Project.
[14:36:32 INF] Project created!

(This output is tweaked from the 0.1.20 output to say ^3.5.x instead of ^3.4.x)

Screenshots

Before execution before

After execution after

Related Product

VPM CLI

Product Version

0.1.21, 0.1.22

OS

macOS / Linux

Additional context

The workaround I have for now is:

  1. stick with version 0.1.20
  2. create a project with vpm
  3. delete the ./Packages/com.vrchat.* directories from the project folder (as the older vpm installs outdated packages by default for some reason?)
  4. cd into the project root directory
  5. run vpm resolve project to install the correct versions of the packages
  6. manually add the new project to Unity Hub
  7. open the project in the 2022.3.6f1 version of Unity, hitting "Continue" when it warns about opening the project in a different version of Unity than it was created for.

Foxcapades avatar Dec 16 '23 19:12 Foxcapades