Nothing to take a look at. Just reporting a bug. If you create a variable, give it a default value or update the value through a trigger later, reference that variable inside of a marker or hotspot within a 360 image environment, the variable reference shows as %[variable]%. It's as if the 360 image environment doesn't know to try to populate variable references. Displays erroneously in this way in preview or as a published course.
I have tested this on my end and am also seeing the value of variables aren't displayed in markers when those markers are in a 360 Image environment. I've tested this in Storyline 360 (Build 3.59.26702.0) and Storyline 360 (Build 3.60.26947.0).
I'll log this as a bug with my team and link this discussion so we can keep you updated!
5 Replies
Per standard use, if you have a text variable that is blank, nothing will show.
Try inserting the reference from the Insert > Reference menu option, as spelling and case are significant.
Not the problem. Spelling and case are correct. Reference is not showing as blank, rather the reference is showing as itself. Eg, %firstName%
The reference is working as expected elsewhere in the course - only not in the 360 image hotspot.
That's different. I think the course that is most likely to get you an answer is to attach the .story file here, so somebody can take a look.
Nothing to take a look at. Just reporting a bug. If you create a variable, give it a default value or update the value through a trigger later, reference that variable inside of a marker or hotspot within a 360 image environment, the variable reference shows as %[variable]%. It's as if the 360 image environment doesn't know to try to populate variable references. Displays erroneously in this way in preview or as a published course.
Hello Curtis!
I have tested this on my end and am also seeing the value of variables aren't displayed in markers when those markers are in a 360 Image environment. I've tested this in Storyline 360 (Build 3.59.26702.0) and Storyline 360 (Build 3.60.26947.0).
I'll log this as a bug with my team and link this discussion so we can keep you updated!