Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

2018.3.0f2 - Assertion failed on expression and computer crash

Discussion in 'Editor & General Support' started by KospY, Dec 17, 2018.

  1. Taurdenga

    Taurdenga

    Joined:
    Dec 24, 2016
    Posts:
    2
    +1 on 2019.3.0f6, seems to happen every once in a while too.
     
  2. MajorBulldozer

    MajorBulldozer

    Joined:
    Mar 14, 2014
    Posts:
    5
    I had the same problem on my side, version 2019.3.1f1.
    What worked for me was to disable Graphics Jobs.
     
  3. AlexWige

    AlexWige

    Joined:
    Mar 30, 2015
    Posts:
    5
    +1 on 2019.3.1f1, very often when particle systems fire
     
  4. oyokuva

    oyokuva

    Joined:
    Jun 21, 2019
    Posts:
    2
    "Could you please send a bug report " ... like it means something . I am still getting the same error it has been 2 years and unlimited number of updates. Unity team don't have time to fix the bugz because they are trying to add new things to satisfy the management as they are in a panic challange with Unreal . This is turning into a cold war against Unreal , and I have a guess about who will be casting USSR.
     
    MartinWorker and hertz-rat like this.
  5. qiufeng8866

    qiufeng8866

    Joined:
    Apr 18, 2015
    Posts:
    3
    Same issue on 2019.3:0f6 ,cuase by Trail renderer

    change the "Graphics APIs for Windows" from DX11 to DX12 . it work for me. thanks
     
  6. MartinWorker

    MartinWorker

    Joined:
    Feb 24, 2015
    Posts:
    12
    this crashbug is still exists in the latest version.. insane.
     
  7. Ava42

    Ava42

    Joined:
    Aug 4, 2012
    Posts:
    33
    2019.3.4f1 still recive:
    Assertion failed on expression: 'task.rasterData.vertexBuffer == NULL'
    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)
     
  8. MartinWorker

    MartinWorker

    Joined:
    Feb 24, 2015
    Posts:
    12
    the problem is still exists in 2019.3.5f1 our game is still crash randomly
     
  9. Elhimp

    Elhimp

    Joined:
    Jan 6, 2013
    Posts:
    75
  10. lolaswift

    lolaswift

    Joined:
    Jan 10, 2019
    Posts:
    151
    second that
     
  11. dval

    dval

    Joined:
    Jul 25, 2012
    Posts:
    24
    I can reproduce this error by toggling between Shaders `Particles/Standard Surface` and `Moblile/Particles/Multiply'.

    To create the error:
    Using a new 3D project in unity, (Any version?):
    • Import Post Processing
    • Import the Unity Particle Pack.
    • Load the Main.scene for the Particle Demo
    • Hit play
    Assertion failed on expression: 'task.computeData.buffer == NULL'
    UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)


    Digging in I found it in the 'Dissolve' example, Flakes particle system.



    The error about Vertex streams not matching.

    I also clicked that `Apply to Systems` button. That did not fix the shader. Instead it seems like it tries to change names of the streams requested from the particle system. But, if they're not present in the shader to begin with, changing the names won't help. Just speculation.

    I fixed the error in 3 different particle systems, Flakes, Embers, Smoke (as the prefabs are titled in the project) by simply changing the shader for each system, and all the errors about vertextData.buffer and computeData.buffer went away.

    So, it seems like this is caused by outdated shaders?
     
  12. Steven-1

    Steven-1

    Joined:
    Sep 11, 2010
    Posts:
    455
    interesting, I'm gonna see if I can get rid of these errors (and crashes!) the same way.
     
  13. MarlonNG

    MarlonNG

    Joined:
    Mar 22, 2020
    Posts:
    1
    in my case y had this issue using a line renderer, in execution a frame missed the second point making advice show after notice i put a provisional second point when to prevent missing in any frame and the advice dissapeared
     
    dval likes this.
  14. OffLineTech

    OffLineTech

    Joined:
    Jul 18, 2017
    Posts:
    1
    I had the same error, I have a ball that rolls and leaves a trail behind.
    It has two objects that seem to be responsible for that trail (I m not sure I didnt make this prefab),and I noticed the this object had a box collider and by deactivating it the error got away
     
  15. mirek-burkon

    mirek-burkon

    Joined:
    Jul 4, 2015
    Posts:
    3
    Reproduced in 2019.3.10f1. The error seems to occur when PS Render mode is set to Mesh and particles are set via
    SetParticles(), no post processing involved
     
  16. Angel_Monroy

    Angel_Monroy

    Joined:
    Jan 6, 2020
    Posts:
    1
    I'm only using particle system and solved it by changing the material and trail material in the Renderer to Default-particle.
    upload_2020-4-28_15-39-51.png

    I understand it may not work for everybody, but it did for me and hopefully somebody else.

    (Using 2019.3.11f1)
     
  17. gosolo2

    gosolo2

    Joined:
    Feb 17, 2013
    Posts:
    6
    This is what worked for me using Crest Ocean System, URP, Unity version 2019.3.0f6 with particle system on in a flying ship, and Post Processing enabled on the Camera. Pimax 8 ( Open VR ), VR enabled and no Azure Sky ( unfortunately ).

    1- I had on my original Camera on the game and I created a new Camera on word space ( 0,0,0 ) coordinates.

    2- I copy the Camera Component Values from my new Camera and past Camera Component Values on my original Camera.

    3- I deleted the Camera from where I copy the Camera Component Values. Save the scene and the problem went away.

    * I tested over 32 times and the problem didn't come back
    * I compiled the game and the game runs smoothly
     
    Last edited: Jun 7, 2020