I’m new to the forums (my first post), wasn’t sure whether to put this in the Linux experimental area or this one – feel free to let me know if all Linux bugs and inquiries need to go there.
In short, I added the Google VR SDK to a new 3D project, but when I go to Build Settings, change platform to Android and click “Switch Platform”, Unity opens a new dialog window saying “Hold On” and freezes at various times when it gets to .png files within the Google VR SDK, forcing me to close the program and restart it. I can’t successfully get it to switch to Android platform with the Google VR SDK asset package presently imported.
Is there a fix for this?
(Running Unity 5.6b3 build on Arch Linux x64, built from AUR & Pamac, Gnome 3.22.2 desktop environment.)
Depending on what texture compression the project is using for Android, compressing textures can be really really slow, especially a large texture can take minutes to complete.
How long did you wait when Unity froze while re-importing a .png file?
The CPU looks almost idle in my System monitor, which I’m interpreting as no real indication of activity from Unity. Currently I’m over 15 minutes into the test, and Unity is still hung up on that file during re-import/Platform Switch.
It’s been over 30 minutes, and still Unity is hung up on re-importing those files (specifically, the same file I mentioned in my above post). I can’t imagine realistically waiting this long - on a machine with high-end specs - without assuming that something isn’t working right.
UPDATE #1: This bug is not present in the Windows build of 5.6.b3. The “Switch Platform” process worked seamlessly, so it appears to only be an issue with the Linux build.
Someone was able to offer me a work-around: switching texture compression from ETC (default) to something like ATC will make the platform switching progress bar reach the end without issue. I honestly don’t know the difference between texture compression methods, but it’s definitely a bug that ETC is causing the progress to freeze on certain .png’s (which I included in the bug report).
I can confirm it’s also happening on my end in 5.6.0xb6 on Linux Mint 18.1 64-bit, Cinnamon 3.2.7 desktop environment, using Nvidia 367.57 proprietary graphics.