Plugins + Scripts Sim Setter (et al.)

Per a request, there is a new SheetSetter plugin as part of the package that can be applied to SimSheet atoms to save and restore their sim positions.

This also functions as a perfect test case for being able to save multiple sim states! I am referring to these as "bundles" because calling them "sets" would result in a lot of confusing wording.

The plugin begins with one bundle slot. More can be added with the Add Bundle button, and they can be deleted (down to a minimum of 1) with the Remove Bundle button. Bundles are named simply "Bundle 1", "Bundle 2", etc. Existing bundles will keep their number/name even if bundles before them are deleted, and new bundles will fill in from lowest available number; you could delete bundles 1-3 and the remaining would be "Bundle 4", and adding another bundle would leave you with "Bundle 1" and "Bundle 4".

There is a toggle to Apply Bundle On Select, meaning that any time a bundle is selected in the menu its sim data would be automatically set. When not enabled, the Set Sim option would have to be triggered after selecting a bundle.

Unlike the clothing-based SimSetter plugins, SheetSetter does not account for atom root position or rotation, and sim data is therefore stored as an absolute position in the scene space. This is a deliberate change to allow for easy repositioning of the atom root to generate different shapes for different bundles, without having to then worry about aligning it anywhere specific to then apply those bundles' data.

Presets can be saved as .sheetsim files, which are solely for SheetSetter and are not compatible with other SimSetter plugins. All bundled sim data will be stored when saved as a preset or in the scene. Small word of caution: since the SimSheet has over 10k vertices, and each vertex has to be saved as x/y/z coordinates of its vector3 position in plain text, scene save files and preset files will get relatively large very fast as more bundles are added. (Each bundle will add another 10.2k lines to the json file. I saved a test preset with 6 bundles and the file was over 2MB.)

If people find that this works well, I'll probably move forward with trying to use a similar system when I get around to making "the big one".

(Demo scene plugin version updated and included also, I hadn't realized it had been suppressed by only updating the plugin var!)

Since I haven't had time to actually work on the big version yet, here's a couple quality of life things I had already implemented, just so they're out there and available.

- You can now save and load presets. SimSetter can save and load files containing a single clothing item's sim position data. OutfitSetter can save and load files containing a set of clothing items' data, but can also save and load the same single-clothing files as SimSetter can, for more granular control on individual clothing items.

- "Set On Load" no longer uses a brute-force time delay on scene load, instead using a handler from the SuperController singleton to activate when the scene is fully loaded. I have yet to find any way to properly trigger the setting function on clothing sim reset, so the QueueSetSim triggers will still need to use a manually-set physics frame delay for things like pose changes. (Range for the delay is 0 FixedUpdate frames [0s] to 200 frames [4s] with a default of 50 frames [1s].)

Credit also added for creators whose work I've more directly referenced and used now that this has grown from a silly little concept utility to a more featureful tool. Thank you for knowing things better than I do!

This update adds the ability to queue loading of the sim for several frames, allowing for simultaneous triggering of things such as pose changes which would otherwise reset and override the sim. This is a rather brute force approach, adding an adjustable physics frame delay (50 frames, or 1 second, by default) between trigger and activation. These actions are only exposed for triggers (SimSettter: Queue Set Sim; OutfitSetter: Queue Set Sim, Queue Set Sim All) and don't have dedicated buttons in the UI.

As an extension of this, there is now a Set On Load toggle available. When this is selected, loading a scene should automatically queue the sim to be set after 1 second, eliminating the need to trigger it separately in the likely scenario that a clothing item is meant to be a certain way by default.

Behind the scenes, the way the data is stored has been changed to be more compact. This hopefully won't have any negative effects on scenes saved with previous versions, because in theory the only way the data would get crossed is by editing the plugin version directly in the scene json.

(These are all things I wanted to establish before trying to work on a version that saves multiple sim states, which I think I've got some better ideas now on how to organize, so hopefully can start on that sooner than later.)

There was also a small bug with the previous version of SimSetter.cs where loading into a scene would always push the log message about a clothing mismatch, because of the exact way it was checking against the uid. This shouldn't have caused any real problems, because it was then just using the fallback check to find the intended clothing item, but it was annoying and could be confusing. That issue should be fixed now.

Tested several situations and it all seemed to work alright, but I'll be on the lookout for errors. Let me know if you see any, especially ones happening at scene load.

Pushing out a fix for an issue where a clothing item wouldn't be properly loaded if it was packaged as e.g. .latest instead of .1. In situations like this, the load method should now split the package info off of the beginning of the uid path and iterate through the existing clothing items in the scene, finding whichever one contains the rest of the path. When this happens it will push a log message showing the discrepancy. This should account for version mismatches, but still relies on clothing items otherwise having the same path structure and name. (Demo scene also updated with newer version to prevent outdated dependencies; its contents haven't otherwise changed.)

Also included in the var is an additional script, OutfitSetter. This script functions about the same as SimSetter, but allows for multiple clothing items to be saved. Use the selection menu to select an item and then Add its sim. Saved items are listed in the text box on the right side. Saved clothing items can be updated individually or collectively. Selecting a clothing item will allow for the individual item's sim to be set, and there is also an option to set all saved sims at once. It is currently still limited to only one saved set of sim data, though.

Let me know if you notice any bugs or odd behavior!

Some minor updates to the plugin:
- Clothing item is now saved along with vertex locations, where previously you would have to select the clothing item to restore it or be shown an error.
- Text box added to right side of UI showing the name of the clothing item selected, because the full uid path in the menu can be hard to read
- Text box also shows which clothing item is saved, and how many vertices are stored.

I was not able to easily find a way to account for atom scale when saving and loading vertex positions; the method I tried ended up with some +/- variance that could cause issues in more sensitive scenarios. Open to suggestions!

Also included is a demo scene, to show the kind of scenario one might find this plugin useful for. Instructions are built in to the scene and it uses no dependencies, aside from the plugin, so have at it!