2020.2.0b2: Player crashing in particle system

Unity Engine
,
1

Hi,

I’m getting a crash with a following stack trace:

0x00007FFDC1D964E0 (UnityPlayer) ParticleSystemRenderer::UpdateVertexInputLayout
0x00007FFDC3263898 (UnityPlayer) ParticleSystemGeometryJob::ScheduleJobs
0x00007FFDC236FAD4 (UnityPlayer) DispatchGeometryJobs
0x00007FFDC26D4B1B (UnityPlayer) CullScriptable
0x00007FFDC2C4E9A9 (UnityPlayer) ScriptableRenderContext_CUSTOM_Internal_Cull_Injected
0x000001A38AE27A06 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Rendering.ScriptableRenderContext:Internal_Cull_Injected (UnityEngine.Rendering.ScriptableCullingParameters&,UnityEngine.Rendering.ScriptableRenderContext&,intptr)
0x000001A38AE27943 (Mono JIT Code) UnityEngine.Rendering.ScriptableRenderContext:Internal_Cull (UnityEngine.Rendering.ScriptableCullingParameters&,UnityEngine.Rendering.ScriptableRenderContext,intptr)
0x000001A38AE278A3 (Mono JIT Code) [C:\buildslave\unity\build\Runtime\Export\RenderPipeline\ScriptableRenderContext.cs:267] UnityEngine.Rendering.ScriptableRenderContext:Cull (UnityEngine.Rendering.ScriptableCullingParameters&)
followed by project specific code

Are there known issues about this?
Asking before I try to spend 2+ days cutting down a full size project to a size fitting in a bugreport

The issue AFAIK is not present in 2020.1.5f1

2

Hi @Hyp-X ,

There is one indeed that was introduced in b2.

Editor crashes in ParticleSystemRenderer::UpdateVertexInputLayout when instantiating particles with Render type “Mesh”

We currently have a fix for this in review. If b1 works for you, chances are that it’s the same issue.

1 Like
3

Here’s the issue tracker link: Unity Issue Tracker - Editor crashes in ParticleSystemRenderer::UpdateVertexInputLayout when instantiating particles with Render type "Mesh

(Might take a few hours to work as I only just converted the bug to be public)

1 Like
4

According to 2020.2.0b4 release notes, this will be fixed in 2020.2.0b5.
Looking forward to it.

3 Likes
5

Hello, I have tried version 2020.2.0b4 and it keeps giving me this error, am I the only one or does it happen to more people?

6

Like I said it is NOT fixed in b4.
The release notes says it will be fixed in b5.

2 Likes
7

Beta 5 just came out, that was quick…