Unity Issue Tracker - Crash on VFXRenderer_Render when both Visual Effect and Outline Components are added to a GameObject

Won't Fix

Votes

0

Found in

2021.3.32f1

2022.3.13f1

2023.1.20f1

2023.2.0b18

2023.3.0a13

Issue ID

UUM-55526

Regression

No

Crash on VFXRenderer_Render when both Visual Effect and Outline Components are added to a GameObject

--

-

Nov 07, 2023

Reproduction steps:
1. Open the attached "crash_IN-59284.zip" project
2. Open the "\Assets\Scenes\SampleScene.unity"
3. Enter the Play Mode
4. Observe the crash

Reproduced with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a13

Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested

Note: Reproducible in Player

First few lines of stack trace:
0x00007FFBCC9412A6 (Unity) VFXRenderer_Render
0x00007FFBCB93D667 (Unity) BatchRenderer::RenderBatch
0x00007FFBCB933EE8 (Unity) BatchRenderer::Add
0x00007FFBCBB0048D (Unity) ScriptableRenderLoopDraw
0x00007FFBCBB0141E (Unity) ScriptableRenderLoopJob

Resolution Note:

The issue come from the user script changing the material list of the VisualEffect renderer.
This is not supported in VFX graph, and it can be avoided by checking the renderer type on the user script before modifying the materials list

Log in to vote on this issue

Comments (1)

toddw

Feb 28, 2024 19:22

How hard is it for Unity to protect devs like me from spending days trying to isolate the cause of this crash since there is literally no useful information logged when this happens?

Is this hard?

public Material[] sharedMaterials
{
get { return ... }
set
{
if (this.GetType() != typeof(VFXRenderer))
{
... = value;
}
}
}

Search Issue Tracker

0