Plugins + Scripts VAMStory

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

hazmhox said:

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

Click to expand...

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

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

Toddy said:

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?

Click to expand...

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

donnylee said:

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

Click to expand...

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.

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.

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

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.

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?

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

hazmhox said:

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

Click to expand...

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

Ghostwalden said:

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

Click to expand...

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.

hazmhox said:

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.

Click to expand...

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?

Ghostwalden said:

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

Click to expand...

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.

Ghostwalden said:

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

Click to expand...

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.

hazmhox said:

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.

Click to expand...

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