Search Issue Tracker

Duplicate

Votes

24

Found in

2018.1.0a1

2018.1.0b10

Issue ID

1038035

Regression

Yes

Assertion failed on expression: '(srcData.GetChannelMask() & copyChannels) == copyChannels after exiting the Play mode

Themes

-

To reproduce:

1. Open the project, attached by the user (castlePrototype.zip)
2. Open the "Map" scene
3. Enter and exit Play mode
4. Observe the assert in the console

Expected: there is not assert after exiting the Play mode

Reproduced in 2018.1.0a1, 2018.1.0b1, 2018.1.0f2, 2018.2.0b4, 2018.3.0a1
Did not reproduce in 2017.4.2f2
Regression introduced in 2018.1.0a1

Comments (6)

  1. Classic-Niall

    Jul 29, 2018 18:39

    I have the same issue.

    I've found that not only was it Lighting but also Reflection Probe.

    Again, doesn't actually break the game, but it's nice not to have all these errors.

  2. eragon75

    Jul 18, 2018 20:32

    It is a problem with the UVs, select the object on hierarchy and with Select, search for Generate Lightmapping UVs and check on this property. I resolve the problem by this way...

  3. Talisman_Skulls

    Jul 16, 2018 07:30

    Put everything in the Hierarchy under an empty Game Object, then select Game Object, apply Static under Yes for children. Then uncheck it from Static and Yes, to apply to children. You can then remove everything from the GameObject and it removed the errors. For some reason in 2018 versions there is a a problem with Static features. I kept receiving this error (32 in fact) every time I) tested a scene and then exited. After using this work around the errors went away and have not returned.

  4. Quartzi

    Jul 13, 2018 19:46

    This Error for me shows up whenever I set an Object Static. I thought this error was because of Occlusion, but even after removing Occlusion the only way I got rid of the Error.. was to remove Static from every object in my Scene, any Object seems to trigger this in my case.

  5. Jakeiiii

    Jun 20, 2018 08:37

    I get about 30 of these any time I do anything that relates to any prefab (whether I search for one, select one, apply to one, etc.)
    They don't cause any problems, they're just there.

  6. NeanderthalMan

    Jun 08, 2018 04:31

    I had this start after importing my Character from the Previous version.
    The character is just the All Stars Character from the Asset store.
    Removing the Character has not fixed the issue
    and the error give no reason nor file that is causing it. Very frustrating

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.