- Newest
- Most votes
- Most comments
I am afraid but I do not think, this is a bug.
The whole layering system is part of the cold Entity system. As far as I know, new entities are attached to the main layer (for now) and thats it. I think, AZ will change it in that regard, as they will remove the layering system at a later point completly.
If you want to save your Entities as a cluster or hierachy, I advice you to look into the slice system. This is fully supported (and actually made) for the new Entity Component system and workes quite well :)
Yes I thing soo. But the problem is that currently even when you working with legacy elements then you are disturbed by it. I am awaitinf for new components to replace old ones ...
That's wright. I am not demanding to fix it wright now. I know that will take time. I just want to notice for Amazon that there is a place to do something with it (as a user and tester). Amazon team will know the best what to do with it ;) Of course I would like to use a new components and system, but until it will be finished it will take a time :)
I feel you there. However, I noticed some unwanted behaviour when using legacy entities. For example, old particle effects that used to work, flicker. Or if you use a high amount of legacy lights, some buffer that holds handles to those lights is not iterated over correctly.
But then again, transition from one huge system to another is not a thing that is made over night, the studios need time to adapt to it (if they are reacting to changes at all or leave it like it is).
The new entites they put in, work pretty nice tho, so if you commit to it, you get around a lot of unwanted and unexpected behaviour.
Thanks for the feedback on this. Yeah, transitioning takes some time but you should see a lot of nice improvements with 1.7 and beyond. Thanks for being patient with us.
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- Accepted Answerasked 7 years ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 months ago