Search Issue Tracker

Fixed in 5.0.X

Votes

5

Found in

4.3.0b1

Issue ID

571060

Regression

No

EditorOnly tag doesn't work on disabled objects

Assets Management

-

To reproduce:
1. Open project EditorOnlyTagBug
2. Build and run the scene EnabledObjectsWithEditorOnlyTag
3. Inspect the memory usage of the executable with the task manager (mine was about 13mb)
4. Build and run the scene DisabledObjectsWithEditorOnlyTag
5. Inspect he memory usage - it's about 40mb

Comments (3)

  1. JohnnyFactor

    Feb 17, 2019 09:52

    This seems to have come back in 2018.3.6 (maybe earlier). I have a Canvas with image components, all with EditorOnly tags and they are included in iOS builds when disabled.

  2. ColinDarkwind

    Jul 10, 2014 16:26

    As was mentioned above, this one is a little dangerous. In our case, we have UI compositions on sprites in the scene that are tagged editor only. Those sprites end up pushing a lot of memory into the scene if they were accidentally disabled.

    There is too much risk for human error to push extra memory into the scene and app. Without this fix, we really can't trust the EditorOnly tag for content in our scene. That was a nice feature. It would be nice to have back.

  3. topsekret

    Jun 27, 2014 02:18

    This is very annoying. Our company has to have a special prebuild process to destroy disabled EditorOnly objects. There are probably lots of people out there that don't even realize this is a problem and are unaware they are wasting memory on device with disabled EditorOnly objects.

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.