Are the triggers in the order shown in the box linked to Standard 1? If so, the program would change Standard 1 to FM when FMCOMP = True. However, since one of the other variables would also = True, the shape would immediately change to the state associated with that. The change would happen so fast you wouldn't even see the FM state. If this is the case, just change the order of the triggers.
It's also possible that there's something wrong with one of the triggers (either the one that adjusts the FMCOMP variable or the one that changes the state of Standard 1).
This sort of troubleshooting is just guessing without seeing the .story file. If you upload it, someone might be able to solve the issue.
Here are the best practices for uploading a .story file:
Only include slides that are related to the problem.
Be sure 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 post with the attachment (if you haven’t already done so):
1 Reply
Are the triggers in the order shown in the box linked to Standard 1? If so, the program would change Standard 1 to FM when FMCOMP = True. However, since one of the other variables would also = True, the shape would immediately change to the state associated with that. The change would happen so fast you wouldn't even see the FM state. If this is the case, just change the order of the triggers.
It's also possible that there's something wrong with one of the triggers (either the one that adjusts the FMCOMP variable or the one that changes the state of Standard 1).
This sort of troubleshooting is just guessing without seeing the .story file. If you upload it, someone might be able to solve the issue.
Here are the best practices for uploading a .story file: