Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.13f1
2021.1.12f1
2021.2.0b1
Issue ID
UUM-3786
Regression
No
Procedural Virtual Texture will sometimes become corrupted when using InvalidateRegion
Reproduction steps:
1. Open attached Project
2. Press Play
Expected result: The terrain has no artifacts
Actual result: Some of the terrain tiles sometimes are loaded in corrupted
Reproducible with: 2020.3.13f1, 2021.1.12f1, 2021.2.0b1
Could not test with: 2019.4 (Could not downgrade)
Notes:
Additionally can be reproduced by using a Free look camera and flying around at high speeds until an Artifact is noticed
The Artifact goes away after being Invalidated
Add comment
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
Resolution Note:
Will not be fixed for now, since PVT is in an experimental, unsupported state. Please reach out if this bug needs to be reopened and we can reassess the issue.
For now, though, it looks like there's a workaround of forcing a refresh by calling an EvictRegion() (instead of InvalidateRegion()) on the entire virtual texture, or on the region that got corrupted. If this is an editor-only corruption that does not occur that often, this may be a good-enough (clunky) workaround for now?