Upload fails with temp directory on case sensitive filesystem SDK3 World 2021.03.22.18.27
gallium
What happens: SDK3 worlds fail to upload when Unity's temp dir is on a case sensitive filesystem. The .vrcw file does get correctly built in the correct location. The error dialog indicating something is wrong provides no hint as to why. There are no errors in the editor log.
What is expected: The world is built & uploaded
Steps to reproduce: Mount a case sensitive filesystem on AppData/Local/Temp and attempt to build & upload a world.
Log In
owlboy
This old against-the-VRChat-TOS user-made patch for the SDK _appears_ to show that there isn't a lot that needs to be done to make the build process work on case sensitive file systems:
Coreforge
This still happens, and prevents building worlds on linux (and probably MacOS as well).
When building the plain udon example, the sdk creates "/tmp/DefaultCompany/clean-avatar-project/scene-standalonewindows64-udonexamplescene.vrcw", and then copies "scene-StandaloneWindows64-UdonExampleScene.vrcw".
Using a case insensitive file system (e.g. ciopfs) fixes this issue, but it would be better if the SDK didn't rely on this.
From a quick look, it seems like at least part of the problematic code is in precompiled binaries, so I don't know where exactly it would have to be fixed.
owlboy
Coreforge Just to note, on a standard macOS install, the SDK builds worlds and avatars fine.
gallium
owlboy It's likely the same as it was last I used Mac OS for most stuff, where HFS+ is case insensitive by default so nothing needs to be done there.
Still, the fix is insanely trivial.
owlboy
gallium APFS now, but yeah!