Plugins + Scripts SceneDirector

[Geraldo]

Yeah, latest (1.22.0.13). I have also checked file integrity just to make sure I'm not missing anything.

 

[Foost]

Yeah, latest (1.22.0.13). I have also checked file integrity just to make sure I'm not missing anything.

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?

I can see this happening if you try to add it as a Session Plugin, it's not designed to work as such. But it should not happen when it's used as a Scene Plugin (or added to an atom, it does not really care).

 

[Foost]

Foost updated SceneDirector with a new update entry:

v6 - triggers and stuff

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...

Read the rest of this update entry...

 

[ouroborolapse]

nice, always wanted a cuck chair simulator

 

[Foost]

nice, always wanted a cuck chair simulator

huh?

 

[FantasiWrapper]

Hi,
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!

 

[Foost]

Hi,
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!

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

 

[FantasiWrapper]

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

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.)

 

[Foost]

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.)

Assuming I understood the question properly.

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)

1. If you do not want to control the person's pose by SceneDirector at all, just turn off the Placement component for the atom:

The atom's states will then capture or apply any of the Placement features.

2. Alternatively, you can turn off Placement for individual states:

The result is the same, but only for those specific states.

On in short, the checkboxes on the individual component section separators completely enable/disable those components, that's probably missing from the docs on the first page. I'll need to clean it up one day.