Forum Discussion
Bugs technique storyline 360 64
Bonjour à tous,
je voulais vous communiquer concernant quelques bugs détectés sur storyline 360*64. Je les cite ci-bas :
- Enregistrement manuel : parfois le storyline ne prend pas en considération l'enregistrement manuel du story.
- Déclenchement : dans certains cas, le déclencheur ne fonctionne pas. pour afficher un bouton suivant après terminer la lecture de vidéo youtube intégré sur storyline ( voir capture vidéo ci joint).
Mise à part ces bugs, nous avons détecté un comportement anormal de cette version de storyline 360.
Merci de m'aider à résoudre ces bugs.
Bien à vous.
Hello DIGI MOOV,
Happy to help investigate these issues for you!
It looks like you meant to attach a recording of the bugs in your post. Would you mind reuploading the video here so we can take a look? You can also use Peek 360 to create the recording if this is more convenient for you.
Please note that triggers don't work with online videos such as embedded YouTube videos since website videos play independently of the slide and aren’t controlled by the timeline. This is the expected behavior for YouTube videos in case this is the possible bug you were referring to with triggers.
I have recorded a video that does exactly what is said above about the bug. My "next button" is set with a variable to appear only once the content is viewed. It works well the first time, but if I go previous screen then come back the button "Next" does not come back. I cannot replay the scene, the button does not work. The variable is hide the next button when the slide begins, then put the next button to normal when the timeline ends. Here is the link to my video showing the bug: https://360.articulate.com/review/content/640996db-ad3d-4cc2-93b9-16dcd8e4e652/review
Can you help?
Hello Marie,
Thanks for sharing the screen recording! What is happening is indeed strange, and I'm happy to help troubleshoot.
Would you be willing to share your Storyline file with us so we can look at what you have set up? You may also share it privately by sending it along in a support case. We'll delete it when we're done testing.
