Search Issue Tracker
Fixed
Fixed in 6000.2.0a9
Votes
0
Found in
2022.2.0a4
6000.1.0b4
6000.2.0a1
Issue ID
UUM-3763
Regression
No
Error i->previewArtifactID == found->second.previewArtifactID' is thrown when assigning SG for the first time
This assertion was randomly and rarely reproducible for a couple of years at least for me, but recently it started to happen much more often and we had a few discussions about it in ADB team, there is a PR with the fix already in flight.
My repro steps:
1 Create new 3D HDRP project (or open existing one without Library folder)
2 Go to "All Materials" filter in Project Browser
3 While previews are generating - scroll in Project Browser and click on those materials which are generating previews
4 Wait a bit while more previews are generated
5 You should get those assertions in Console - if you don't - repeat from scratch
Old description:
{quote}How to reproduce:
0. Note: Reproduced using URP, reproduces only when creating and saving SG for the first time
1. Create VFX Graph
2. Create SG
3. In Graph Inspector, check Support VFX Graph' flag
4. Save SG
5. Assign it to the VFX
Actual result: Assertion failed on expression: 'i->previewArtifactID == found->second.previewArtifactID'UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) is thrown to the console
Reproducible with: 2022.2.0a4 (14.0.1), 6000.2.0a2, 6000.1.0b2
{quote}
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 6000.2.0a9):
Verified fixed on 6000.2.0a9