Naturalis v1.2.0 (49.var)

Alright, v1.2 is now considered done. This is a soft launch, I will update the Hub post once I have made a new features showcase video and updated the documentation.

Changes

Ignored clothing items

I went through all of the freely available clothing items on the Hub that were irrelevant to the plugin but weren't correctly region tagged, and manually added them to an exclusion list.

As a result, about 1000 free items are no longer shown in the Clothing tab's clothing item popup - things like makeup, hats, accessories, jewelry and piercings, gloves, boots, cum splats etc. It's not perfect, but it's better than nothing. Obviously, the list will easily go out of date as new items are released, and it doesn't exclude any paid clothing. Ideally, clothing authors would tag their items with the correct body region tags - anything that has some region tag but not "torso", "full body" or "hip" is automatically excluded.

Fixes/other

• Fixed memory leaks when drawing visualizations
• Optimized memory use when updating text fields in the UI, e.g. things like current values of physics parameters.
• Ensured that loading an in-plugin preset saved in v1.0.x is converted properly when loaded in v1.2.x
• Ensured that migrating from TittyMagic 5 to Naturalis v1.2 using the auto-upgrade script works properly
• Prevent error when saving scene/preset when the plugin is not yet initialized (e.g. when the plugin is added to a disabled person atom, and the atom is not enabled before saving the scene)

V1.3 plan update

Trello is updated: https://trello.com/b/AcnDeqFr/naturalis-public-roadmap

All remaining to-dos for v1.2 are moved for v1.3. Looking at the v1.3 plan, it seems the scope has once again crept up upon me.

Granted, the 2-month development time for v1.2 was impacted a lot by the fact that I've been developing v1.3 alongside it, and that v1.2 involved a lot of non-feature technical work as well (improving code quality etc.) which should not be the case for v1.3. Regardless, since I want to keep a somewhat consistent development time per new full release, it might turn out to be necessary to move some features to v1.4 depending on how quickly progress can be made, and how much time I end up spending on other plugin work. That's something to think about next year though. For now, let's focus on making the most of the remaining year!