Hi,
I was trying to change the "Background" value through "Set Variable" in playmaker but that doesn't work. I guess that variable is not "public". Is there any other way to access it?
I'd like to control the transitions through playmaker, so I have better control about the fade-ins and outs and cleaning scenes. If there is not a way, then I'll stick to the sequencer.
Thanks!
VN Framework: Access to variables with Playmaker
Re: VN Framework: Access to variables with Playmaker
Hi,
In the next version, i'll make it so you can use Set Variable to change the background variable.
In the next version, i'll make it so you can use Set Variable to change the background variable.
Re: VN Framework: Access to variables with Playmaker
Thanks Tony!
Re: VN Framework: Access to variables with Playmaker
Another question:
I'm trying to run some Lua code using the "Run Lua" action in Playmaker.
The code works when I run it from the node using Dialogue System, but it doesn't work when I run it from Playmaker.
I'm trying to run some Lua code using the "Run Lua" action in Playmaker.
The code works when I run it from the node using Dialogue System, but it doesn't work when I run it from Playmaker.
Re: VN Framework: Access to variables with Playmaker
Just as a side note: I managed to accomplish the same goal using a couple "Get Lua Field" actions to get the information needed and put it together using the "Build String" action of Playmaker. Then I show the alert with the right variable created by the previous action. It's a bit longer but it works too.
But I'm still curious about the Run Lua not working.
But I'm still curious about the Run Lua not working.
Re: VN Framework: Access to variables with Playmaker
Is "DisplayedName" supposed to be "Display Name" by any chance? Are there any warnings or errors in the Console window?
Re: VN Framework: Access to variables with Playmaker
"DisplayedName" is a variable I created in Dialogue System.
No errors displayed.
Actually, I think my second approach is the best way to do what I need, so I don't have any hardcoded variables and I can access them by playmaker depending on the object I'm interested...
So no worries Tony.
No errors displayed.
Actually, I think my second approach is the best way to do what I need, so I don't have any hardcoded variables and I can access them by playmaker depending on the object I'm interested...
So no worries Tony.