Plugins + Scripts VAMStory

[hazmhox]

Your background can be transparent. Text does not need to be transparent.

 

[Ghostwalden]

Your background can be transparent. Text does not need to be transparent.

I put the VAMStory Button it in front of an image, so I can click on the image and it triggers then the VAMStory button in front of it, which is completely transparent.
So, neither background nor text should be visible.

But I just found out, that there doesn't need to be a text in the textfield.
Just thought the basic text (type label...) would appear agian if I do not enter a text

 

[Toddy]

I added a slider to control the global speed in timeline. The Vamstory slider moves the test transition slider but there is no change to the animation speed. When I directly move the test transition slider there is a speed change. Is there a setting I may be missing to get it to function properly?

 

[donnylee]

can someone tell me why the story language changes into english automatically, always after the first load of the text displayed in my native language 1 sec. I remember it used to work fine

 

[hazmhox]

I added a slider to control the global speed in timeline. The Vamstory slider moves the test transition slider but there is no change to the animation speed. When I directly move the test transition slider there is a speed change. Is there a setting I may be missing to get it to function properly?

Can you show how you configured the slider?
Mary uses that everywhere, it works fine : )

can someone tell me why the story language changes into english automatically, always after the first load of the text displayed in my native language 1 sec. I remember it used to work fine

VAMStory does not handle any translation logic (either in the UI or in the scenes). If you have something like this happening, you're using a modded version of VAM or VAMStory, which has nothing to do with my original code/implementation.

 

[Toddy]

While attempting to recreate the issue to send you my configuration, I discovered the conflict was the second instance of timeline which shared the same empty as Vamstory. The fix was to simply change the segment/animation name in that timeline.

 

[hazmhox]

Perfect! Glad you found the origin of the bug : )

 

[Ghostwalden]

One of my VAMStory takes action at Scene Load.

I have two images (a normal and a dark one) that I can switch between with a VAMStory Toggle Button (Main Trigger).
Each of the Images has a separate VAMStory Toggle Button (Image Trigger) in front, which the Main Trigger turns on or off, according to the Image.
Each Image Trigger has a VAMStory Toggle Button, with Action to turn on and off the actual Image and turn off the other Image.

I hope you can understand to some extent what I want to say

When I save the scene now, with the normal Image on and the dark Image off and then load the scene again,
VAMStory turns off the normal one and loads the dark.

You can download the file here, if you want to have a look at it.

908.5 KB file on MEGA

mega.nz

So, I found out, that it has something to do with the Image Trigger of the dark Image.
When I turn off there (Image Lips Normal Off) on the On and Off trigger, it doesn't change at scene load anymore.

I know, it's a "double action", means the image is already turned on and off with the Main Trigger.
But I can't imagine, that this leads to problems.
I mean, the same is in the Image Trigger of the normal Image, which turns off there the black Image
and this double action, does not cause that scene load problem.

I mean, VAMStory shouldn't take any action at all, until something gets triggered, right?

 

[hazmhox]

It's the default state. You set the default state to off. When loading, it simply enforce what you told it to do : )

 

[Ghostwalden]

It's the default state. You set the default state to off. When loading, it simply enforce what you told it to do : )

Set the (default state ) to on did not help, but (do not execute triggers at start) below did

 

[hazmhox]

Set the (default state ) to on did not help, but (do not execute triggers at start) below did

That's different, it simply does not execute your button triggers at start.

Which means based on your video your default state is "off", and you save your scene with your cosmetics (pictures) on. VAMS will not trigger as you asked it, but the button will still be off. Which means the player will have to click twice to reach the proper state when first interacting with it.

So again : set your default state to the one you want at load and save your scene. Don't try to override what VAMS does for you.
AND on top, you can disable the triggers if you want to avoid triggering what the button is doing besides changing the button pictures state at scene load.

 

[Ghostwalden]

That's different, it simply does not execute your button triggers at start.

Which means based on your video your default state is "off", and you save your scene with your cosmetics (pictures) on. VAMS will not trigger as you asked it, but the button will still be off. Which means the player will have to click twice to reach the proper state when first interacting with it.

So again : set your default state to the one you want at load and save your scene. Don't try to override what VAMS does for you.
AND on top, you can disable the triggers if you want to avoid triggering what the button is doing besides changing the button pictures state at scene load.

Thanks for your reply hazmhox.

It seems to load and work properly when I turn on (do not execute triggers at start)

But I have not really understood this with the default state yet.
What exactly does this default state refer to?

The settings, as they are generally currently in VAM and the Scene? or on the On or Off triggers in VAMStory?

 

[hazmhox]

It seems to load and work properly when I turn on (do not execute triggers at start)

It's simply because you mitigated the trigger execution. Based on your video, being Default at off, the picture will stay active (because you don't execute the triggers) but the state of the button will not change to the proper state.

But I have not really understood this with the default state yet.
What exactly does this default state refer to?

It's like any checkbox system, it's the default state of the checkbox at start, either on or off.
It's not a VAM/Scene/Triggers thing... it's the state of the checkbox, so everything depending on that state also. If you have it checked, the checkbox will default to on and execute the on triggers at load if you did not disable them.

 

[Ghostwalden]

It's simply because you mitigated the trigger execution. Based on your video, being Default at off, the picture will stay active (because you don't execute the triggers) but the state of the button will not change to the proper state.

It's like any checkbox system, it's the default state of the checkbox at start, either on or off.
It's not a VAM/Scene/Triggers thing... it's the state of the checkbox, so everything depending on that state also. If you have it checked, the checkbox will default to on and execute the on triggers at load if you did not disable them.

Ah great, I guess, now I understood how to manage those two options.
I just didn't expect, that VAMStory triggers anything at all on scene load
But fortunately there is a checkbox for this

It really can get a bit complicated sometimes when multiple triggers refer to the same object.
In this example, I had to prevent VAMStory of the Dark Lips Image trigger from executing triggers at start.

Otherwise, it would have turned on the dark lip image in one state when starting the scene or created a double-click situation in the other state,
because the Hamburg image turns on the image of the Dark Lip and the trigger of the Dark Lip again.

But the important thing is that it works now

 

[Ghostwalden]

Another problem, whitch I encounter with the Director Plugin of VAMStory is,
that it doesn't load what it should at scene load.

In this scene, I only have normal button in VAMStory.
No toggle buttons that can perform an action at scene load.
I only have that one Scene Load trigger in VAMStory Director.
When I test the trigger in VAMStory Director or use it in my scene, it works perfectly,
so the trigger itself is fine.
But when I start the scene, VAMStory Director loads some VAMStory UI
and hide some.
Non of the VAMStory UI ist set to stat hidden at scene load.

Any idea what might be interfere here?

 

[hazmhox]

I don't know what's your goal so it's hard to say.

 

[Ghostwalden]

I don't know what's your goal so it's hard to say.

My goal ist to trigger a relay trigger at scene load with VAMStory director.

The relay trigger itself works fine and does turn everything on that sould be visible at scene load and turns everything off that shouldn't be on.

I added this relay trigger to the VAMStory Director and when I test it there, everything works fine,
but when i load the scene, some VAMStory UI's are visible and some are hidden, but not as they should be according to the relay trigger.

 

[hazmhox]

I don't know why you're using a relay trigger for this.

Director is made to handle that sort of stuffs. And since relay probably has a different "load" speed, this could induce issues (maybe?).
Create a Director trigger that turns your UI on/off whatever you need.

Call this trigger in your starting trigger of Director (be careful to not loop triggers as there is no way to prevent infinite looping).

 

[Ghostwalden]

I didnt create that relay trigger especially for the VAMStory Director.

Instead of adding tons of triggers to the VSDirector, I thought, I could add that relay trigger, which I use in my scene, to the VSDirector.
That would have made it a little easier.
Even with possible adjustments, there would be one place less where changes would have to be made

It's still a bit weird, because the test trigger in the VSDirector executes everything correctly, but then no longer when starting the scene.
I thought that maybe there was something else that I had overlooked.
But fortunately there are always different ways.

In this case, I have now simply switched all VS UI panels that should not be visible when starting the scene to start hidden.

But the most pleasant, of course, would be if the most uncomplicated and simple way worked.

 

[hazmhox]

I don't see how configuring a relay trigger is less complex than a director trigger.
At the end of the day, you're setting everything you need (let's say hide for each of your UI) in both. And you're calling it.

Sometimes I have a hard time understanding how your brain works

 

[Ghostwalden]

I don't see how configuring a relay trigger is less complex than a director trigger.

I didn't say, that configuring a relay trigger is less complex.
The relay trigger is a part, that I use for the scene itself.
He controls the appearance of a certain area and since it is precisely this area that should be active when starting the scene, I wanted to add that trigger to the VSDirector as scene load trigger.

At the end of the day, you're setting everything you need (let's say hide for each of your UI) in both. And you're calling it.

It seems to look quite like it...
It would have just been very comfortable if I could have triggered the already existing relay trigger with the VSDirector

Sometimes I have a hard time understanding how your brain works

I'm sorry, but I'm not a native english speaker and my english is really basic. But I try my best and a lot of Google translator
So it certainly does not always come across as I would like to say it.

 

[donnylee]

Can you show how you configured the slider?
Mary uses that everywhere, it works fine : )




VAMStory does not handle any translation logic (either in the UI or in the scenes). If you have something like this happening, you're using a modded version of VAM or VAMStory, which has nothing to do with my original code/implementation.

Problem fixed, it was a translation plugin I forgot so long, I deleted it, and everything works fine, thanks for your tip.

 

[hazmhox]

hazmhox updated VAMStory with a new update entry:

Gaze Update, QoL & Bug Fixes

View attachment 535839
VAMStoryActions

• Fixed a bug where you couldn't set the value of an action multiple times in a row if the slider value was the same as the new value.
• Added new static POIs for @atani
• Added new animated POIs
• Added two new buttons on the side of the UI to focus the atom and to toggle the action panel
  
  View attachment 535840

Tools...

Read the rest of this update entry...

 

[Mutatta]

Is there a way to reorder Vams Director triggers? I tried to do it in the json directly but that just messed things up :/

 

[hazmhox]

Nope. Order does not matter very much anyway.