playing around with it on an existing scene with a bunch of other plugins to see if it can play nice with little adjustments. broke damn near everything, even something as basic as penis alignment. which is an achievement since i usually found ways to compromise between plugins with similar functions
- autogensthruster - only used for alignment. deeper hijacks it, but for some reason does not even do the job of keeping genitals aligned at all
- expression blushing and tears - suppresses everything outside of its functions. not surprising penis support + deeper just confuses the hell out of where the penis is supposed to be. penis support off (aka use deeper's aligning helper by itself) doesn't do anything, playing with autoradius mult doesn't do anything
- autobulger - also hijacked by deeper. deeper's implementation works, but doesn't do visible in/outs and just bulges the belly in place. pretty sure it's a consequence of penis alignment not working, but limited adjustable options to compensate in deeper as far as i can determine (manually adjusting genital depth override can simulate what autobulger's doing, but *manual* really?)
- bodylanguage - no conflicts so far, but maybe because i've disabled anything not related to pose saving there. pretty sure the atoms would go haywire almost immediately if fillmeup forces + deeper are both active at the same time
- performance improvements? potato computer, never noticed anything, neither better nor worse
tl;dr you might be better off starting scenes from scratch instead of trying to integrate the plugins
Hi borniketok5000, I'm very surprised about all you said after all the test I'v done, loading other creators' scenes, creating my owns.
This not means my plugin is perfect, as I said in the overview I'm open to listen people to improve this plugin.
-Genital alignment is a complex goal, and you are right by design and testing I chosed to handle some cases like what autogensthruster do. What you define 'hijack' has been removed in version 1.0.4, it was a plus of a plus, so no problem to touch that part.
- expression blushing and tears: I'm investigating right now about my plugin and scenes with expression blushing and tears plugin, last thing I want is conflicts between plugins
- autobulger: Initial idea was to replace the effect with my morphs and logic, using the autobulger plugin values and disabling it, since v1.0.1 this is different, user get to choose.
- bodylanguage is a nice feature plugin, although is quite a difficult plugin to play along in term of compatibility as developer (tbh), I investigated around before my distribution and at this very moment my plugin and BL plugin can work together nicely. My plugin does not apply forces the same way like BL, if you encounter physics expplosion 99% is not my plugin to cause it, that's for sure.
- About performance i'm not sure about what you are referring to: many hours spent to reduce cpu and memory consumtion. If you are encountering heavy performance issues with my plugin, you can try turning useless thing off and see if anything goes better.
I have both a power pc and a quite old notebook, used both for testing the performance inpact and improve critical parts, but if there is an area you say is causing perf problems let me know and I'll try to improve that area.