Forum Discussion
True/false variable triggers suddenly not working
Hello everyone. This is my first time posting. Thank you all in advance for the help.
I'm working on a videogame-style course, when you start the course you can choose your character's appearence between two options, and your character stays the way you've choosen for the entire course, but suddenly at the end of the course it stops working and it will only show one of the styles.
Okay so it works like this: When you start the course you have to pick between style a (false) or style b (true), the preset is false. The character is custom-made, so it has all custom-made states to match different views and movements for both styles. The way it works is that if youve choosen any of those styles, all the state changes triggers depend on the true or false variable.
I haven't set that variable change anywhere else in the course, but it works everywhere except on the last slides of the course. On those slides suddenly the only style that shows is style b (true) even if you picked style a (false).
The weird part is that on the same slide you have two different places where you can see the character:
1) your character profile picture that is set on the master slide (having there the triggers that allows it to show the correct state depending on the style you've choosen) and
2) The interactive "sprite" that does actions around the slide videogame-style.
That profile picture WORKS PERFECTLY, implying the true-false variable hasn't changed, it shows the correct style everytime, but the sprite only shows style b.
So if the player choose style a (false), at the final slides he's gonna see his profile picture with style a (false) but his character will show in style b (true), even when all the triggers stated that the character will have style b state if TRUE and style a if FALSE.
I really don't understand how this happened, why it only happens in those three final slides? The character is copy-pasted from slides that are STILL WORKING.
I'm currently working on a work-around but it still frustrates me.
(I'll probably won't be able to upload the course bc its really heavy)
Thank you!
It's virtually impossible to troubleshoot an issue like that without seeing the file. Best guess is that there's something wrong with the trigger. That could be the wrong object, the wrong state, and/or the wrong condition(s). So double-check those.
If you still can't find the answer, prep a copy of the .story file, and upload it for troubleshooting.
Here are the best practices for uploading a .story file:
- Only include slides that are involved in the problem.
- Be sure all objects, layers, motion paths, and variables have meaningful names.
- If there is proprietary content, replace or delete it. For example, replace proprietary text with ipsum lorem text.
- Be sure to clearly describe the following (in the file and/or in the question posted in the discussion):
- What you want to happen
- What is not happening that should happen
- What is happening that shouldn’t happen
- What you have tried
Seems like it's some kind of bug, I literally copy pasted the character and its triggers and interactions onto another slide and it started working in that slide, copy pasted it back in the original slide and worked.
And in the question I already described the problem. Player chooses "style A" character, during all the course the character stays as "style A" on different interactions and triggers, except on the final slides, where suddenly the character changes to "style B" unprompted, the character was being copypasted from different slides where it worked.
Judy is not asking to see the .story so she can know what the problem is. You already described that. She is asking for the file so someone can look at it and tell you WHY it’s doing what it’s doing, and how you can fix it.
However, according to your second post, it appears you have found the solution. If you can make it function by re-creating the object, that indicates some sort of corruption somewhere in the slide, object, or triggers. That is not an infrequent occurrence in SL, and, as you discovered, has a pretty simple fix.
