I’m experiencing weird texture errors when moving the camera or simply moving around in my game.
I’ve recently bought a new laptop that has the Snapdragon X Elite as CPU (which is ARM-based) and am using the emulated verson 6000.0.26f1 for x64. I’m currently making a game for a school project with multiple other students and no one else has this issue. Because we’re using Wwise as a package I can’t use the native ARM64 version of unity 6, because that in in itself has a bunch of bugs, but even disregarding that the textures are also buggy on the native ARM64 version of the unity editor.
The project is 3D URP, and the texture errors happen during runtime and in the scene view, it’s also not a problem of custom textures, since it happens with normal URP textures as well.
I’ve tried a new project using the built-in unity render pipeline, and the texture errors are gone, so it’s probably a URP problem.
Hey, can you check with Compatibility mode in URP and tell me how it goes? Project Settings > Graphics Settings > URP > Render Graph > Enable Compatibility mode
Wow thanks that worked perfectly! Will this have any big impact on the unity project overall? Because if it has too big of an impact I might not be able to use it since it will also affect my colleagues. It said something about not being able to use shader graphs, I don’t think we’re using any now, but if we ever do it might not be ideal.
Hey, this was not a fix at all, just a debugging step, sorry for the confusion… Compatibility mode is the old rendering path with URP. Default one in Unity6 is Render Graph, which is enabled when Compatibility option is untoggled, it brings many improvements and should be preferred.
ARM-based CPU with GPU integrated (like yours) on Windows laptops are fairly new, they can use a different rendering backend in Unity (render pass) that is enabled by default when using Render Graph (and not with Compatibility). This rendering backend should be optimal with your hardware, but it looks like something is broken.
Long story short, this is a bug and we will fix it, please file a bug ticket to Unity with a minimalist repro case and mention your hardware and the fact that it only happens on URP Render Graph. In the meantime, you can still use the Compatibility mode while the bug is investigated.
Hi Rudolf, thank you for highlighting this issue. Would it be possible to try whether using the native arm64 version of Unity instead of going through the emulation layer fixes the issue?
Running the Unity Version 6000.0.26f1 with the native Arm64 version still shows the bug, I don’t know whether newer version fixed it with the native Arm64 version, but atleast the 6000.0.31f1 emulation version hasn’t fixed it yet.
Thank you for clarifying. We will investigate a bit further on our side.
In the meantime, some ideas to work around the issue:
It could be worth trying to override the graphics API. It’s possible the issue only occurs with certain APIs.
The Compatibility mode could be a temporary solution. However, this locks you out of some features, like writing Render Passes using the modern Render Graph API. Compatibility mode also will be removed from Unity in a future version, so this is really only a temporary workaround.
