Naturalis v1.1.0 (Patreon)

Hi! This is the finished v1.1 non-beta version, though it's not yet officially in early access.

Change log relative to v1.1-beta4

Improvements to packaging clothing profiles

Improved the way clothing profile presets are detected by VAM for the purpose of creating an AddonPackage aka .var file.

Short version:

Clothing profiles are treated similarly to native preset types (like clothing presets, appearance presets etc) when it comes to packaging and loading files from packages. Creators can include clothing profiles inside the same var packages as the files that reference them, and things should work properly on the user's end. This was important to do to ensure the system is usable for creating and consuming VAM content.

Long version:

If you select a profile and save the scene, and then package the scene file and click "Prep Package" in the VAM package manager, the manager will notify about the preset file being missing from the package - just like with any native preset type. The button to auto-fix references works as well for the purpose of auto-adding missing local clothing profiles preset files.

The same applies to target profiles (used in the target profile transition feature introduced in beta 4). If you select a target profile in the current profile and save the profile, when you package the profile the package manager will complain about the target profile file being missing until you add it.

Additionally, saving a scene or in-plugin preset that references a local clothing profile and then saving said scene/preset along with the profile into a var package will work correctly. When you load the scene/preset from the var, the profile is correctly loaded from the var as well since the scene now references the profile in the var rather than the locally saved profile. Just like with native preset types in VAM. This also works with target profiles (where you save the profile and targer profile in the same var). There's only one limitation that I know of - Plugin Presets (the ones you manage via Plugin Presets tab in VAM) that reference local clothing profile preset files won't load the profile from the var package if the preset and profile are packaged into the same var. Best use in-plugin presets instead!

Other changes

• Added a triggerable LoadClothingTargetProfileWithPath action. This can be used just like the LoadClothingProfileWithPath triggerable action, but it will load the target profile
• Resetting a morph back to the value it had in the previous calibration will now reset the calibration pending state (i.e. calibration is not needed if the morphs that the plugin monitors for changes have unchanged values)

Fixes

• Fixed blank page issue when navigating to TittyMagic Breast Weight window
• Various technical changes to reduce memory usage overall, and to patch up memory leaks. The major memory leaks occurred when the plugin UI was open in certain windows like Clothing or a physics parameter's window where the currently active values were continuously updated to the text fields in those windows.
• When using the Auto-update.cs script, the plugin id number (e.g. plugin#1) is now retained and all of the triggers in the scene or other plugins referencing the plugin's triggerable parameters will work as usual
• Fixed TittyMagic Hard Colliders window not showing the All Colliders Mass value
• Fixed flickering "(unsaved)" text in BootyMagic clothing window when profile is unsaved
• Fixed misaligned UI elements in BootyMagic clothing Additional Settings window

I'm currently not aware of any other bugs, at least not ones that I could reproduce on my installation. As usual, if you find something, let me know. If you can come up with a step-by-step to reproduce the issue, even better - that makes it infinitely easier for me to fix.

___________________

The below unfinished items remain on the trello board, these will be moved to the v1.2 to-do queue in some form.

Clothing profile additional physics parameter adjustments

This is a too broad, essentially it's an investigation item - i.e. test different physics changes and see if they look good if part of a clothing profile. If not... no change.

Investigate automatically preventing nipple clipping

I have an idea for how to implement this but it's most likely a bit too time consuming to do at this point in v1.1 development.

Investigate linking clothing adjustment profile with clothing item preset

The idea here is that you could set the default profile for an item on a per-preset basis. E.g. if you have a shirt with a preset that has tight and rigid sim physics, and another preset with loose sim physics, you'd want a different clothing profile to be automatically applied for each preset. So instead of the overall default preset being applied, it'd apply the preset specific one when that preset is loaded. It's not entirely clear how this could be implemented - ideally, the profile to use would be stored as part of the preset itself, but that's not feasible since the preset's handling is part of VAM itself can plugin's can't really change that behavior. It'd need to store the preset info in the profile instead, and then somehow detect when a preset is applied and find the correct profile to apply. This one's also too time consuming to do in v1.1.

Focusing on the public early access release posts and documentation next!

-everlaster