Open MrAmericanMike opened 1 month ago
There is no visibility, although I assume you mean the "enabled/disabled" checkbox which would cause a MeshComponent not to display. Can you give me more of a usage example?
Lets say I want to select all this tires at once, as for now the easiest way is to drag a box and select all of them, but to achieve that, I need to "hide" the white dot that represents the floor, so I got into the floor component and "hide/disable" it.
While the white dot will still render and goes lightblue indicating it was selected, I can select all the tires at once and move them.
PS: Just noticed this leads into a different bug in which, while the floor didn't move, it's white dot did.
Will try to reproduce what happened here in a cleaner way.
I would guess the floor probably moved too and was just too big to really notice? Unless there is some bug where a visual isn't syncing up after a move. That said, the white dot selection thing is hopefully not a "long term" thing, at least not a "forever" thing. So I'd chalk this up more to "better box select not requiring exact origin point" with a combo of "multi-select from node hierarchy".
It would be nice to have some kind of indicator on the Node Hierarchy letting us know that certain components visibility have been turned off.