Plugins + Scripts VAMStory

[AGZXTT]

Hi, i might just be dumb, but i don't understand why, my dialog box disappear when i add material? Any idea? Thanks

 

[hazmhox]

Hi, i might just be dumb, but i don't understand why, my dialog box disappear when i add material? Any idea? Thanks

Ho! That might be an oversight, I fixed several situations like this, I might have missed one. You mean the background right?
Simply select the action that has the background that disappears, it will be reloaded. I'll try to find the situation where it's borked and fix it : )

More info on when this happens on your end?

 

[AGZXTT]

Ho! That might be an oversight, I fixed several situations like this, I might have missed one. You mean the background right?
Simply select the action that has the background that disappears, it will be reloaded. I'll try to find the situation where it's borked and fix it : )

More info on when this happens on your end?

Well everything disappear, background text and hide button. It happens when selecting any material, comes back if i set it to none but tbh i think it might be more related to me having made a mistake than the plugin itself i just can't figure why haha

 

[hazmhox]

Well everything disappear, background text and hide button. It happens when selecting any material, comes back if i set it to none but tbh i think it might be more related to me having made a mistake than the plugin itself i just can't figure why haha

Just selecting any material?
That's colorcorrect, that shit prevents VAMS to work at all due to transparency shenanigans : )

 

[AGZXTT]

Just selecting any material?
That's colorcorrect, that shit prevents VAMS to work at all due to transparency shenanigans : )

Yep any material, what do you mean by colorcorrect? Im still a bit lost on vam i have to say.

 

[hazmhox]

Yep any material, what do you mean by colorcorrect? Im still a bit lost on vam i have to say.

There's an asset called "colorcorrect" that changes the overall tone of the scene. The way it's implemented (super hacky) it prevents or can produce bugs when combined with VAMStory.
If it's not that, it's potentially something else interfering with the rendering order/UI of VAMStory.

 

[AGZXTT]

Ooooooh okay! It was loaded with the environment i used and missed it in the cua list, my bad i really tend to miss the obvious with vam, still feels overwhelming sometimes haha thanks for the help tho! i'll try to make a scene worth sharing around your plugin.

 

[hazmhox]

No worries

 

[fumesec]

Hey, thanks for the idea, i've tested it too. Looks like there's indeed troubles when changing backgrounds (remove/reload) : both butons got same backgrounds images (action 0 & 1), but it mess up when clicking on the buton as you can see on the 2nd screenshot. I tried to reaload again on action 1 the images, and it makes disapearing the one from action 0 'Background Light' (screen 3) but buton 'Main light' works fine again. Seems there is something the plugin doesnt like with using same images ? Hope this helps you figure it out

 

[hazmhox]

Hey, thanks for the idea, i've tested it too. Looks like there's indeed troubles when changing backgrounds (remove/reload) : both butons got same backgrounds images (action 0 & 1), but it mess up when clicking on the buton as you can see on the 2nd screenshot. I tried to reaload again on action 1 the images, and it makes disapearing the one from action 0 'Background Light' (screen 3) but buton 'Main light' works fine again. Seems there is something the plugin doesnt like with using same images ? Hope this helps you figure it out

It happens if you force reload the same image, but from what I had, if you simply scroll back on the action it should reload. It's a problem of the sprite being recreated (because I need to clear the cache).

You're saying by just "clicking" on it you have the problem, are you sure about that? 'coz I tested everything at least 10 times (and retested just right now on my clean VAM) and I never had that behavior. ( I'm talking in a "playback" situation without fiddling in edit mode )

 

[hazmhox]

Ok I found the source of my mistake, will fix that asap, I'll just add a Render Queue QoL on top before submitting.

In the meantime, the reason why it does that :

• For "Toggle Buttons", the current condition is "is there a On background". To avoid having problems :
  • For toggle buttons, add a On and a Off background, it should work properly : )

 

[hazmhox]

hazmhox updated VAMStory with a new update entry:

Hotfix/Bug Fixes & new rendering options

VAMStoryActions Custom

• Added Canvas Order global option to be able to sort panels when adding multiple scripts on a single empty atom
• Added Render Layer global option to allow placing UI in front of everything when using post process
• Removed the Toggle Button background using the off background on the on button (and vice versa) when having only one background (it was confusing after all)
• Fixed a bug when selecting a button background for...

Read the rest of this update entry...

 

[ccammell]

backgrounds! thanks for the great update!

 

[Dragontales]

Hi @hazmhox ! Not sure if this is a bug or if I'm just using it wrong, but in the VamStory Gaze plugin, when you set it to "Enable Random Weighting", with a min and max, the Gaze Weight doesn't seem to follow the Min or Max correctly. It seems to still go down to 0.01 and up to 0.68 and just back and forth between those two.

 

[hazmhox]

Hi @hazmhox ! Not sure if this is a bug or if I'm just using it wrong, but in the VamStory Gaze plugin, when you set it to "Enable Random Weighting", with a min and max, the Gaze Weight doesn't seem to follow the Min or Max correctly. It seems to still go down to 0.01 and up to 0.68 and just back and forth between those two.

The min is clamped to .01 or -.01 to avoid slight stutters when being exactly 0, this is normal.

And the min and max are two values between which it will randomize each time it's gonna trigger a gaze. So let's say you have 0.5 and 0.8 as min and max, everytime the character will start a gaze, the possible values will be 0.5, 0.6, 0.7 and 0.8 (or any decimal value between the mix and max really, this is just as an example )

So if you wanted the gaze to always directly look at you, put 1.0 and 1.0 in min and max.

But obviously the goal is to have variations between each gaze, so just experiment with it.
The idea to quickly iterate on your settings, is to lower drastically the pause and hold time to let the character often go back and forth between looking at you or not.

To summarize :
- Enable Random Weighting always starts at 0 ( 0.01 )
- It will wait a moment based on your pause settings
- then trigger a gaze which values that are randomized between min and max
- hold the gaze
- then go back to zero
- pause... etc...

 

[Dragontales]

The min is clamped to .01 or -.01 to avoid slight stutters when being exactly 0, this is normal.

And the min and max are two values between which it will randomize each time it's gonna trigger a gaze. So let's say you have 0.5 and 0.8 as min and max, everytime the character will start a gaze, the possible values will be 0.5, 0.6, 0.7 and 0.8 (or any decimal value between the mix and max really, this is just as an example )

So if you wanted the gaze to always directly look at you, put 1.0 and 1.0 in min and max.

But obviously the goal is to have variations between each gaze, so just experiment with it.
The idea to quickly iterate on your settings, is to lower drastically the pause and hold time to let the character often go back and forth between looking at you or not.

To summarize :
- Enable Random Weighting always starts at 0 ( 0.01 )
- It will wait a moment based on your pause settings
- then trigger a gaze which values that are randomized between min and max
- hold the gaze
- then go back to zero
- pause... etc...

Ah....I was using it incorrectly. lol. Thanks for the explanation.

 

[frozenhash]

would it be possible to add the Render Layer toggle also to the base story plugin?
at some point it was a UI element, but in of the updates it was changed and now dialogue boxes are hidden by objects if they overlap

besides that ... best plugin evaaaaa!!!

 

[hazmhox]

at some point it was a UI element, but in of the updates it was changed

It was a bug, hence it was fixed

I'll add that at some point in a QoL. But the render layer only works with post process enabled anyway as mentionned in the plugin.
And since it's world UI first and foremost, at the moment, I don't really have the incentive (nor motivation) to add a secondary camera to render the UI.

 

[DarwinsTripod]

Yo. Congrats on the fantastic work.
I have encountered a problem again and i don't remember what i did to fix it but i'm encountering it again.

So I've got some UI buttons set up on a menu In VamStory. I have a toggle switch that attaches it to the camera. but I've noticed when looking down it clips through the floor and the buttons disappear making it unable to click on them. In an old scene of mine I have it so they always visible regardless if something is in between the camera and the button but i have no idea how i set it up. Is anyone able to shed any light on the situation.
Thank so much.

 

[hazmhox]

Yo. Congrats on the fantastic work.
I have encountered a problem again and i don't remember what i did to fix it but i'm encountering it again.

So I've got some UI buttons set up on a menu In VamStory. I have a toggle switch that attaches it to the camera. but I've noticed when looking down it clips through the floor and the buttons disappear making it unable to click on them. In an old scene of mine I have it so they always visible regardless if something is in between the camera and the button but i have no idea how i set it up. Is anyone able to shed any light on the situation.
Thank so much.

Previous post.

VAMStory is a world UI, that behavior is normal. It's not made to be "considered" as a viewport UI.
The day I'll add the UI layer to the other plugins I just added to Actions Custom, it could work only if you have a post process in the scene. But beyond that, there's no way around without me changing the way the UI renders.

 

[DarwinsTripod]

Previous post.

VAMStory is a world UI, that behavior is normal. It's not made to be "considered" as a viewport UI.
The day I'll add the UI layer to the other plugins I just added to Actions Custom, it could work only if you have a post process in the scene. But beyond that, there's no way around without me changing the way the UI renders.

Fair enough.
Thanks very much for your input. I’ve got it working on an old scene of mine. I think I just copied a sub scene or something across and edited it there. I’m currently struggling to get it working again but I know it’s possible.
I wouldn’t know how to set up the post process myself so I’m getting a little lost as I can seem to successfully copy it across again regardless. Congrats on the plug in.

 

[hazmhox]

Fair enough.
Thanks very much for your input. I’ve got it working on an old scene of mine. I think I just copied a sub scene or something across and edited it there. I’m currently struggling to get it working again but I know it’s possible.
I wouldn’t know how to set up the post process myself so I’m getting a little lost as I can seem to successfully copy it across again regardless. Congrats on the plug in.

You just need to have either Post Magic or Moyashi enabled on an empty atom on the scene ^^
It's quite easy! If you can't figure it out, ask : )

 

[DeadMaroz]

Is it possible to add Render Layer global option to main VAMstory and Actions plugins? Would be grateful))

I want to make UI behave like it belongs to screen space - not affected by postprocessing or light. And render over any objects in worlds space, and be clickable. Before version 30 it behaved like that (if post processing plugin was added to the scene). That bug (as for me, it was a feature ) was fixed in v31.
Or it can be implemented different way and i missed something?

 

[hazmhox]

Read the last messages : )

 

[DeadMaroz]

Read the last messages : )

Yes... I didn't read carefully. Then I'll stick with version 30 for now, with this wonderful bug. The solution is a bit cumbersome with attaching to the camera, but it works.