enhancement - when a mover exists for an object, indicate that on it's instance Mover tab

[ghramsey]

When mucking about in androidlab I moved the EMP and Molotovs from the loot room outside the android showroom.
I think I deleted them actually vs merely moving them off screen.

I replaced their locations with non-offensive pickup items noisemakers and flashbangs.
But in game the static renderings of the Molotovs and EMPs remained due to Mover entries.

Until I went in-game and found this though I didn't have any way to know the Mover existed for each. It doesn't show up in Unity.

Can you make it so the Mover tab lights up for the composite instance if a Mover exists for the object?
As it is the Mover tab on the molotovs are greyed out. All of the tabs are on this one in the screenshot,
but the other two have references and zone entries.

The Movers for the EMP and Molotovs were buried on the Required Asessets> Weapons>Base_TP folder.
On the Pickups composite and instances the Mover tab is greyed out.

This would also have helped when after porting that blueprint to Hab_Airport.
I thought the positioning had a bug until I thought about checking for a Mover entry which turned out to be correct.

[MattFiler]

To add to this - objects that have movers already contextually show the mover button, if none exist the button will be greyed out. The complexity comes from the fact that a mover is likely nested within a composite, as it's typically on the ModelReference inside.

Really this ticket is linked heavily to #268 - which is what I'm working towards long term - which is to display and calculate/write MVR data based on what has been applied within the tool, rather than treating it as a separate path.

[ghramsey]

Ah Cool! If you've got something in the works then this is moot.
And yeah, that's what I was after some indication that a nested mover exists on a composite instance.

It didn't occur to me to check in the two cases I noted on my original post until after the fact.
The EMPs and Molotovs actually took me by surprise having Movers at all.

How about a tool tip in the interim? When moving the instanced object around.
This is the main case where this even comes into play; when moving or deleting from it's stock position.
Something like "there are movers associated with this object" to alert people who don't realize the mover exists.

[MattFiler]

Sorry I missed this reply - I'm working on combining all the instanced data together and displaying it better as a part of #95, #268, and #144. I've seemingly finally managed to replicate the complex logic required to map all this data together, just need to figure out my problems with calculating the instanced positions and then ordering the data correctly to re-write it to the various resource files.

It might be a little bit before it makes its way to staging - and probably won't be any major updates for a while during working on integrating it all as it's a pretty huge change - but will keep the tickets updated as I go 👍

[ghramsey]

Ah!!! That sounds huge and also sounds like it's a massive undertaking.
No worries on this. You have bigger fish to fry..