Search Issue Tracker

Fixed

Fixed in 2022.3.7f1, 2023.1.7f1, 2023.2.0a23

Votes

2

Found in

2022.3.0f1

2023.1.0b19

2023.2.0a17

Issue ID

UUM-37360

Regression

Yes

Editor crashes on VFXRenderer::AddAsRenderNode when assigning a Renderer’s materials toits to materials/sharedMaterials

--

-

How to reproduce:
1. Open the “VFX_Crash_Repo.zip“ project
2. Open the “SampleScene“
3. Enter Play mode

Expected result: Editor runs in Play mode
Actual result: Editor crashes on VFXRenderer

Reproducible with: 2022.2.0a15, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17
Not reproducible with: 2021.3.26f1, 2022.2.0a14

Reproducible on: Windows 10

Note: Reproduces with HDRP and URP

First few lines of the Stack Trace:
0x00007ff7586a8cf9 (Unity) VFXRenderer::AddAsRenderNode
0x00007ff75770e967 (Unity) PrepareRenderNodesOnMainThreadDeprecated
0x00007ff75770f5ca (Unity) QueuePrepareIntegrateMainThreadObjects
0x00007ff75770bd12 (Unity) ExtractSceneRenderNodeQueue
0x00007ff757761636 (Unity) CullResults::GetOrCreateSharedRendererScene

Comments (1)

  1. unity_AE917296600D30C30687

    Jun 16, 2023 08:22

    This issue happens to me after upgrading a project from 2021.3.24f1 to 2022.3.2f1. What's weird is that the VFX can still be played in the editor with the game running but calling VisualEffect.Play in a script will crash the program with the error above. Is there a workaround ? Thank you !

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.