Search Issue Tracker
Won't Fix
Won't Fix in 2021.2.X
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
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?
Resolution Note (2021.2.X):
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?