Animated Gif File issue |Some dot appear

Hi,

When I publish my storyline file the gif displays either like this, some small red dot appear at the bottm of the gif file.

Actually its not appear when I view the file directly.

I am Using the Storyline 3 latest veriosn (Update 3), and the Gif file created using Animate CC - 2017.

This will happen for the all gif files.

  

 

 

 

Thanks!

Regards,

Hari

 

19 Replies
Ashley Terwilliger

Hi Hari, 

Are you using Storyline 3 or Storyline 360? This issue is still open in Storyline 360, and also not yet fixed in Storyline 3. Fixes are deployed first and often to Storyline 360, and then rolled into larger updates of Storyline 3. 

Any discussion linked to a bug report is flagged on our end so that we can update you once there is more info to share! 

Nicholas Pinkham

We are still seeing this issue in storyline 360 but have a fix. Before we understood the issue better, we would place a small shape over the unwanted pixel, but this was tedious. We are using small animated arrows that are about 20x20 pixels, created in Adobe Animate.

However if we create the same animated gif but with 4px of padding around all the edges of the image, at 28x28 pixels, the unwanted pixel in the corner does not show up. 

I'm not sure why having 4px of empty pixels around the border prevents the image glitch from happening, but I hope this can be helpful in solving the issue.

Jo Zhou
Alyssa Gomez

Hi Nicholas,

Thanks for the head's up! I just retested a file containing a GIF, and I noticed the purple dot wasn't visible anymore. I'll bring this up to our product team to get further confirmation. When I get an update, I'll pass it along to you!

Hi Alyssa, any update on this? We are using a storyline 2, and can still see lots of white dots in our GIFs...

Nicholas Pinkham

Hi Alyssa,

Thanks for your reply. My team is very curious about this bug. It has cost us many hours of our time, troubleshooting and applying the fix to dozens of courses. It might not be a stretch to say we have spent more money fixing this bug than we have on storyline licenses.

We also couldn't help but notice that this bug existed for over a year, but not long after I posted my fix for the issue, it was addressed in a storyline product update. We would very much appreciate it if we knew what was the cause of this issue. Thanks.