Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.2.0a7
2019.3
2019.3.0f6
Issue ID
1220947
Regression
Yes
Crash on VFXTextureGenerator::ComputeSignalCurve or Gradient::EvaluateHDR when opening a specific scene
Reproduction steps:
1. Open the attached project ("1220947.zip")
2. Open "CrashScene" Scene
Reproducible with: 2019.2.0a7 (VFX 4.3.0), 2019.2.21f1 (VFX 5.16.1), 2019.3.3f1 (VFX 7.2.1)
Not reproducible with: 2018.4.17f1 (VFX 4.3.0), 2019.2.0a6 (VFX 4.3.0), 2020.1.0a1 (VFX 7.0.1, 7.2.1), 2020.1.0a24 (VFX 7.2.1)
Couldn't test with 2017.4 as there's no Visual Effect Graph for it
First lines of stacktraces:
0x00007FF6EA7C4F45 (Unity) VFXTextureGenerator::ComputeSignalCurve
0x00007FF6EA7E067C (Unity) VFXTextureGenerator::UpdateAnimationCurve
0x00007FF6EA7CA834 (Unity) VFXExpressionContainer::EvaluateExpressions
0x00007FF6EA7CF9A2 (Unity) VisualEffect::ProcessUpdate
0x00007FF6EA7E0578 (Unity) VisualEffect::Update
0x00007FF6A3DAFB36 (Unity) Gradient::EvaluateHDR
0x00007FF6A3DADFBA (Unity) VFXExpressionContainer::EvaluateExpressions
0x00007FF6A3DB343C (Unity) VisualEffect::ProcessUpdate
0x00007FF6A3DB25BB (Unity) VisualEffect::InitData
0x00007FF6A3DC088E (Unity) VisualEffect::SetVisualEffectAsset
Workaround: "Edit" -> "Visual Effects" -> "Rebuild All Visual Effect Graph"
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
- [HDRP] APV debug mode Validity Over Dilation Threshold doesnt take touchup volumes in account
- Performance cost of looping animations increases over time
- [HDRP] Recursive rendering refraction is very different compared to Rasterization/PathTracing
- [VFX] Skinned Mesh Renderer sampling first frame after culling in T-Pose
- Can't select color from Editor with color picker when Unity Editor is on Secondary monitor
Resolution Note (fix version 2020.1):
This crash was due to an unexpected expression graph serialized within the asset. We added an extra validation step to detect this kind of unexpected data.
With 2019.3, it can be easily avoided using "Rebuild All Visual Effect Graph" before open the scene. It isn't a problem in 2020.1.0a1 and later versions of that stream since compilation has been integrated into the importer.
Resolution Note (fix version 2019.3):
Fixed in 2019.3.6f1