Improvements to the Level Viewer

[MattFiler]

I want to do some updates to the Level Viewer project to make it more useful when working with the Commands editor.

Today I pushed some changes to improve the lighting and update it to the latest CathodeLib changes, but the workflow is still an issue. I'd like to get it to the point where you just open Unity and don't touch it, and any changes you make in the Commands editor are reflected across to give you a 3D visual of where positions are.

Things to look at:

• Currently selected objects in the Commands editor should select in Unity (this is already kinda implemented, but a bit janky)
• Moving something in the Commands editor should move it in Unity
• Deleting something in the Commands editor should delete it in Unity
• Adding something in the Commands editor should add it in Unity
• Everything in the hierarchy should be hidden to prevent tampering (perhaps even lock objects in Unity side so they can't be dragged, to make it clear the transforms are one-way)
• Ideally, performance would be better. Might be worth looking at Graphics.DrawMesh to see if that helps. By default, I should make sure nothing is selected improve perf on first launch (the highlight is laggy).
• Stretch goal: visualising triggers and positions of non-renderables would be great

Once these are done, I'd like to include it as a project within the OpenCAGE download which can be launched via the Commands editor if Unity is installed (and also provide help for installing the correct Unity version).

[ProjectHSI]

Everything in the hierarchy should be hidden to prevent tampering (perhaps even lock objects in Unity side so they can't be dragged, to make it clear the transforms are one-way)

I feel like this should be optional, just to allow users to preview transforms and stuff (or reflect from Unity to Commands Editor?)

[MattFiler]

Yeah I'd want the transforms to be reflected back in the Commands editor if you could move things in Unity otherwise it'd get confusing and there'd be room for things to be transformed incorrectly vs what's saved to disk. Will keep it in mind!

[ghramsey]

Some of the improvements might be working a little wonky since the update.

It's closing the hierarchy list when I select any composite except the root node in the commands editor.
If I search the list also vanishes the list sometimes. Going back to root restores the list.
This used to keep the list at all times.

Also, when I used to click on an object like a door after a bit of clicking through
it used to show me the entity. Now, it's showing only the model reference.

As I click on it too something blinks the data field, but then it goes away immediately.

This might be how I've got Unity setup. IDK.

If you need more I can try and take some video clips.

[MattFiler]

Some of the improvements might be working a little wonky since the update.

It's closing the hierarchy list when I select any composite except the root node in the commands editor. If I search the list also vanishes the list sometimes. Going back to root restores the list. This used to keep the list at all times.

Also, when I used to click on an object like a door after a bit of clicking through it used to show me the entity. Now, it's showing only the model reference.

As I click on it too something blinks the data field, but then it goes away immediately.

This might be how I've got Unity setup. IDK.

If you need more I can try and take some video clips.

I'm basically rewriting the Unity stuff for this, so hopefully those issues will be resolved. Will let you know when it's available on staging to try out :)

[MattFiler]

Quick video showing progress so far, you can now load levels/composites, select entities, and have their positions and renderables update realtime: https://discord.com/channels/1116018062630592593/1116020662272807049/1359261738104520814

I need to fix the path implementation in the script editor so that you can correctly step in and out of nested composite instances, but otherwise this is all looking good.