You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back in february Locomancer was updated to use Unity 2017.3. Since then it causes a GPU hang immediately when rendering the first frame after the Unity logo. The Unity Logo shows fine in SteamVR, then in SteamVR it switches to the loading animation for Locomancer, it renders a frame in the preview window and then the GPU locks up.
It happens with my RX 480 with all the recent kernels and radv git versions since then, extended and direct mode.
Forgot to mention that someone told me some unity bugs are worked around with the environment variable RADV_DEBUG=zerovram.
Locomancer does indeed work with RADV_DEBUG=zerovram. So there's a good chance Locomancer just has to upgrade to a better Unity version in the future and this will go away.
Back in february Locomancer was updated to use Unity 2017.3. Since then it causes a GPU hang immediately when rendering the first frame after the Unity logo. The Unity Logo shows fine in SteamVR, then in SteamVR it switches to the loading animation for Locomancer, it renders a frame in the preview window and then the GPU locks up.
It happens with my RX 480 with all the recent kernels and radv git versions since then, extended and direct mode.
The text was updated successfully, but these errors were encountered: