Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.2p2
Issue ID
786889
Regression
No
[WSA] Changing terrain texture at runtime getting visual artifacts
When changing terrain texture on runtime, texture data seems to get corrupted, rendered with wrong colors or sometimes not appearing at all. Some analysis on this issue has been done and it seems that after the texture switch constant buffer is corrupted somehow - it contains very big values (something like 1e8 as before switch values were under 10). Those values are finally used in shader when doing texture sampling and pixels are invalid.
Reproducible on 5.3.4f1, 5.3.4p3, 5.4.0b14 versions.
Repro GIF:
https://gyazo.com/e85e2f388421b903e1fd64e4ccc0da2e
Repro steps:
1. Open project "TerrainTextureTest.zip
2. Open the test scene and play it. Press buttons visible on screen to swap existing textures or to generate textures from scratch.
3. Build to WSA 8.1 or WSA Universal 10 platform with .NET backend (with IL2CPP backend there is no visual issue).
4. Build and run generated project on PC or tablet.
On WP10 phones issue ir not reproducible. Also, issue is not reproducible when using IL2CPP backend for WSA Universal 10 platform.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment