I hate to say it, but I think there may be a problem with colliders loading in correctly on scene load. I've been building a scene with two models, both with this plugin. Every time I load the scene, the Penis Colliders are not visible. If I reload the models Preset with collider editor, it doesn't resolve it. The only way is to individually reload the Collider Editor plugin itself on each model, and then Load Preset within Collider Editor.
-This appears to occur more frequently, if the model was loaded into a scene by Merging scenes. No matter what you do after the initial merge, this is inevitable to occur to both models every time you reload the scene there after.
There is another thing that happens, however I have been unable to notice a consistency to it, to track down a possible cause/interaction- But the Gen3 Collider sometimes will load in way out of position. Adjusting the "Up Offset" to put it back into position again will resolve it temporarily, however it needs to go far outside it's normal offset range to resolve. If you save the Collider preset, when you reload it, again it's way off axis. So I'm assuming some how on the original load, is thinking Gen3 needs to be somewhere else. Again I haven't seen a consistent situation to reproduce this bug, but I'd say there is a 30% chance, that when I go through reloading all the Collider Editor Plugin's on the two models, and reloading their Presets, it happens on one of them 30ish % of the time. One way I've found to alleviate the possibility of it occurring(by a fluke), is I made a quick animationpattern that adjust the the morphs of the penis, that changes it's size and length. Sort of like a flaccid and erect slider. If I adjust the shape and size of the penis, after loading the scene, AND THEN reload Collider Editor, then Load Preset(for collider), it will result in Gen3 not being placed off-axis in the "Up Offset." Doing things in that order has resulted in Gen3 never being out of it's correct positioning.
Hopefully this is fixable, as I don't believe it happened in some of the previous builds. I haven't tested to see if this occurs with just a single model in the scene though. My focus has been to use two models with it this whole time.
EDIT: Has anyone else noticed this? Or is it just me?