Is it broken in your specific scene, or even in the default and/or empty scene? If you save the scene with the plugin added and then reload the scene, does it still explode?Yeah, latest (1.22.0.13). I have also checked file integrity just to make sure I'm not missing anything.
I consider this version "good enough" to no longer be considered a preview. I've been using it long enough in all my personal scenes to be quite satisfied with the functionality it offers.
The main new feature are...
Triggers
These come in two variants.
State TriggersView attachment 582982
This is a new component, available on all atoms. As with all other components, disable/enable it, or reorder...
huh?nice, always wanted a cuck chair simulator
I am glad someone else finds this plugin useful. Honestly it's the plugin I enjoy developing the most, even if it ends up not being used too much because it might be too technical and confusing. I'd like to make a series of tutorials for it one day, but I don't have that much free time for VAM ; and I'd rather work on improving the plugins when I doHi,
this plugIn speaks to my inner nerd/technical side.
SO Thanks for making and Sharing all this!
Have a big scene underway already with VamStory/director, mega amount of logicBricks, BL-PoseMe, Timeline etc.
Decided today am going to slowly integrate this plugIn and see how to streamline.
First test was making a super simple mascara run triggered by BL stim (be alot more complicated when done).
Spend several hours going through your detailed info.
The tifa wetness vid really made it click, where you show Lerp etc.
And in DildoDemo, saw you used CoreControl as ReceiverAtom. So duh, i used that and set up trigger in BL.rml.stim.
So got my first mascara run on and off based on Stim using your PlugIn.
Did this with logic bricks before.
So now will have to slowly see what works better where.
Really enjoyed your various dress state possibilities too.
Will be super curious to see how can work in variables for a more feature rich story!
So Thanks! Alot!
Can SOO relate to first focus being on 'improve the plugIns".I am glad someone else finds this plugin useful. Honestly it's the plugin I enjoy developing the most, even if it ends up not being used too much because it might be too technical and confusing. I'd like to make a series of tutorials for it one day, but I don't have that much free time for VAM ; and I'd rather work on improving the plugins when I do![]()
Assuming I understood the question properly.Can SOO relate to first focus being on 'improve the plugIns".
Having difficulty even imagining trying to 'support' this complex plugIns with how to tuts.
That said, Examples sure were helpful (and taking the time to understand your approach).
Playing with it more today, i ended up with a question.
Maybe answer is there, but having troubles finding it.
re: my 2 'states" Mascara Run On & Off
It seems they are all atom position based, when made the 2 states? (fyi: did not click capture at all)
In middle of couch anim, and on state change she moves to where created mascara state.
It's 100% the change in state. Visually confirmed it.
Q: When loading a state, is there a way to disable loading the pose position - from when you made the state?
Tried under settings with both sync (both of them Direct vs PoseMe), but no change.
Tried subState - ON - interpolate DAZ bones & rigidbodies - again no change.
(just trying things to see what happens)
Or should i be doing this simple alpha change otherwise?
(Is cool how you can "change/bump" the stim rate at same time via state.)
This update adds one new feature
Splits Atoms
Split Atoms allow you to add the same Atom under SceneDirector's controls any number of times. Each Split Atom can control different set of the Atom's properties, and each has its own set of States.
How
First add a scene Atom to SceneDirector the usual way, this is called the Primary Atom. Then you can add any amount of its "splits" on the Split Atoms tab.
Split Atoms control the same atom in the same...
Hey, Thank you for clarifying that. Good to know Placement right down to Spring strengths for eg.,Yes, it is possible to include whatever components and properties of any atom you choose in captured states, that's up to you. Placement is the component that handles positions/poses, it controls:
- Positions and rotations of all controllers, DAZ bones and rigidbodies (whichever you choose in the component's settings, it defaults to capturing controllers, for person atoms also their DAZ bones, and for CUA objects their rigidbodies iirc)
- On/Off/etc states of all captured controllers
- Controller parenting
- Many of the controller physics settings (spring strengths etc)
Yeah even if I never do the tutorials for SceneDirector, I should probably at least add tooltips to most of its controls. It's easy for me to know what does what since I wrote it, but probably not so much for anyone else. Especially now that I started adding ctrl+click shortcuts to things (I also really need to add those to the various delete buttons so I stop deleting states by mistakeHey, Thank you for clarifying that. Good to know Placement right down to Spring strengths for eg.,
How come i didn't try the check mark toggle -- kinda like sometimes somethings under your nose and ya don't see it.
Think i just didn't twig with 'placement', though i should have; my brain in VAM is glued to Position or Pose i think.
Part of my 'poor excuse' > it was a very long day already.
Looked at everything else.
The rationale of the new 'split atoms' update sounds like just up my alley.
Am so looking forward to playing with this!!
Well, it's top-drawer kind of you to even share all this already. This is a huge toolbox really.Yeah even if I never do the tutorials for SceneDirector, I should probably at least add tooltips to most of its controls. It's easy for me to know what does what since I wrote it, but probably not so much for anyone else. Especially now that I started adding ctrl+click shortcuts to things (I also really need to add those to the various delete buttons so I stop deleting states by mistake, but that would 100% need tooltips first)