Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Assertion failed: Assertion failed on expression: 'kValidSceneObjectIdentifier == res'

Discussion in '2017.3 Beta' started by jwvanderbeck, Oct 1, 2017.

  1. jwvanderbeck

    jwvanderbeck

    Joined:
    Dec 4, 2014
    Posts:
    825
    Since upgrading to this beta from 2017.2 beta, I'm having this weird issue with certain prefabs from many asset packs and even from the Unity Standard Assets.

    Not all prefabs but a LOT of them, just selecting them in the project library will cause infinite spamming of this into the console:

    Assertion failed: Assertion failed on expression: 'kValidSceneObjectIdentifier == res'


    This only happens when selecting it in the project library. Interestingly once it is added to a scene, there is no problem.

    Anyone have any idea what that might be?
     
    jwvanderbeck, Oct 1, 2017
    #1
    irfanmahmud991 likes this.

  2. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    Hi jwvanderbeck,
    Could you please submit a bug report with a minimal reproduction case for this issue and reply in here with the case #?
     
    LeonhardP, Oct 2, 2017
    #2

  3. jwvanderbeck

    jwvanderbeck

    Joined:
    Dec 4, 2014
    Posts:
    825
    Huh I wasn't thinking of it as a bug so much as a change that required some updates to the assets, and was trying to figure out what that was, but sure I can submit it as a bug report.
     
    jwvanderbeck, Oct 2, 2017
    #3

  4. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    LeonhardP, Oct 2, 2017
    #4

  5. jwvanderbeck

    jwvanderbeck

    Joined:
    Dec 4, 2014
    Posts:
    825
    LOL I literally JUST submitted it, sorry.
     
    jwvanderbeck, Oct 2, 2017
    #5

  6. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    Thanks! Alternative reproducibles are never a bad thing to have.
     
    LeonhardP, Oct 2, 2017
    #6

  7. jwvanderbeck

    jwvanderbeck

    Joined:
    Dec 4, 2014
    Posts:
    825
    jwvanderbeck, Oct 5, 2017
    #7

  8. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    I've told the devs about the broken link. Should be fixed soon. In the meantime: we have a fix for this issue! It still has to go through QA, but could land as soon as b5.
     
    LeonhardP, Oct 5, 2017
    #8

  9. pants-xbox

    pants-xbox

    Joined:
    Oct 12, 2017
    Posts:
    1
    The issue is still in b8. Will it be fixed in b9? Is there a workaround?
     
    pants-xbox, Nov 10, 2017
    #9

  10. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    Unfortunately not. It still has to be backported. I'll ask the devs for more info on Monday.
     
    LeonhardP, Nov 11, 2017
    #10

  11. EddieChristian

    EddieChristian

    Joined:
    Oct 9, 2012
    Posts:
    725
    Still getting this error on B9
     
    EddieChristian, Nov 16, 2017
    #11

  12. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    There are no workarounds for this issue other than using a prior version of Unity. The fix is not going to be in b10. There were merge conflicts that prevented earlier integration which still have to be fixed.
     
    LeonhardP, Nov 16, 2017
    #12

  13. Vagrant-VX

    Vagrant-VX

    Joined:
    Sep 3, 2016
    Posts:
    8
    Found a workarounds for this issue
    jest uncheck "Auto Generate" checkbox in Lighting Settings
     
    Vagrant-VX, Nov 21, 2017
    #13

  14. Claytonious

    Claytonious

    Joined:
    Feb 16, 2009
    Posts:
    904
    Well, sure, if you don't need lightmaps. You get this same assertion error when lightmaps are baked, whether it's via auto or by manually baking. So, still looking forward to the fix.
     
    Claytonious, Nov 21, 2017
    #14

  15. charlesb_rm

    charlesb_rm

    Joined:
    Jan 18, 2017
    Posts:
    485
    Our devs are working on fixing this issue in 2017.3. It should make it in RC1 if everything goes as planned.
     
    charlesb_rm, Nov 23, 2017
    #15

  16. Rahd

    Rahd

    Joined:
    May 30, 2014
    Posts:
    324
    having this bug in 2017.3 , so the bug trigger at importing assets from other projects where some prefabs , scripts are missing
     
    Rahd, Dec 8, 2017
    #16

  17. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    Which version are you using? This should be fixed in the latest release. If it still occurs there for you, could you please submit a new bug report with a reproduction project?
     
    LeonhardP, Dec 8, 2017
    #17

  18. Rahd

    Rahd

    Joined:
    May 30, 2014
    Posts:
    324
    not occurring again . thank you :) again it's a minor bug , happens when i export assets from a project , but forget to include the prefabs or scripts . when i import it to the new project that bug keeps going in a loop , closing the project did fix it .
     
    Rahd, Dec 8, 2017
    #18