Jasima/lvra.gitlab.io
1
0
Fork 0
mirror of https://gitlab.com/lvra/lvra.gitlab.io.git synced 2024-11-09 18:10:25 +01:00
Code Issues Projects Releases Packages Wiki Activity

Unity: ALCOM fixed drag-and-drop crash

Browse source
This commit is contained in:
hypevhs 2024-08-14 08:09:13 +00:00
parent a7fc5f5448
commit 988810b66f
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/docs/vrchat/unity.md
View file

@ -102,11 +102,9 @@ WAYLAND_DISPLAY="" dolphin
An ALCOM-launched instance of Unity can crash after trying to drag-and-drop an item (within Unity, ie. not external programs).
This will likely be fixed by ALCOM v0.1.14.
This [issue #1346](https://github.com/vrc-get/vrc-get/issues/1346) was fixed by ALCOM v0.1.14, so just update.
https://github.com/vrc-get/vrc-get/issues/1346
Analysis: ALCOM has a different environment than the rest of your system, mostly by virtue of being an AppImage. This means the Unity subprocess that it spawns will inherit its crummy vars. The one at fault here is likely `GDK_PIXBUF_MODULE_FILE`. Unfun fact: This causes several other problems too (such as GTK-themed menubars and context menus on a KDE system), but I'm not sure the cleanest way to unset those vars yet. A wrapper script around the Unity binary?
Analysis: ALCOM has a different environment than the rest of your system, mostly by virtue of being an AppImage. This means the Unity subprocess that it spawns was implicitly inheriting its crummy vars. Unfun fact: This environment inheritance causes several other problems (such as ignoring the user's GTK theme for menubars and context menus, especially on a KDE system), but I'm not sure the cleanest way to unset those vars yet. A wrapper script around the Unity binary?
### VRCFury builds lock up the editor