Zoom regions not functioning

Oct 04, 2017

Does anyone know what makes zoom regions randomly stop working? They show on the slide, but some randomly stop working in the publish and preview. I delete them and then add them in again, but they seem to just stop working later. Anyone know what could cause this? I'm using them for software training.

47 Replies
Alyssa Gomez

Hi Traci, sorry you're running into trouble with your zoom regions! I can help you figure this out. Can you tell me a bit more about your file?

  • What version of Storyline are you using?
  • Is the file saved to your local hard drive? 
  • Does the same thing happen in a new Storyline file, or just this one in particular?
  • Where are you hosting the output after the file is published?
Traci P

Hi Alyssa, Thanks!

So this is what I have discovered. 

Storyline 360 or SL3. Both cause the issue in the HTML5 ouput. 

The file is saved locally. I can see the issue in the preview, local publish, and 360 review site publish outputs. This only happens in the HTML 5 output. Flash works fine. 

It happens with any new files and the current one I'm working on. I haven't dared to open up an older file that was working correctly in the past. 

In testing I've discovered that if the zoom region is for the full slide, it doesn't show at all in the output. If the zoom region is for the partial timeline, the screen shows the full slide then jumps to the zoom and looks glitch. 

This only happens in the HTML 5 output. 

I'm troubleshooting as much as I can because I'm on a deadline for a client. I've asked two other storyline users to test. One is experiencing the same issue. Another is not. I can view the files published by the user who is not experiencing the issue and the outputs look fine on my computer. 

I submitted a small portion of my initial file with a ticket yesterday. 

Let me know if there is any other info you need. 

Thanks!

Traci

Leslie McKerchie

Great news everyone! 

We just released another update for Articulate 360, and included a few important fixes that you'll see in the release notes here

The item you'll be interested in is:

Fixed: Zoom regions wouldn't work in HTML5 output when they were set to start at the beginning of slides, and they caused test-mode screen recordings with hotspots to fail.

Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Also, be sure to check out Arlyn's video and visit our What’s New page!

Ashley Terwilliger-Pollard

Hi all,

The issue where zoom regions wouldn't work in HTML5 output if they were less than a second in duration, and they wouldn't always return to their initial states when revisiting slides was also fixed in the update to Articulate 360 released this morning. You can follow the same steps above to update. 

Crystal Horn

Hi Traci.  I'm sorry you're hitting some issues!  I did a quick test with our latest build of Storyline 360 (3.11.14249.0), and a zoom region at the start of the timeline seemed to work fine for me in both Flash and HTML5 output.  I also tested zoom regions lasting less than a second.  Check out my web-hosted project here.

Would you like to share your .story file so we can have a look?

Traci P

Hi Crystal! Thanks! You're right. I can't replicate this on a new file. But on all the files I'm in the middle of (started before I did the upgrade) I'm getting the jumps. I tried deleting out and adding new zoom regions. I have a set of 6 or so large software demo modules that are working through reviews that now have this issue. Is there a fix?

Here is what I see on a current file with a zoom region inserted previously. 

https://360.articulate.com/review/content/23fef694-c4b5-48f6-bf0c-711d70ff32d0/review

Joyce Hensen

I'm working with a file that I just updated from SL2 to SL3.  Zoom regions that worked perfectly before don't show in SL3, or jump in and out at strange times.  I didn't change anything when updating the file to SL3.  I did try (on one slide) deleting and adding back the Zoom region.  That didn't have any impact.  I'm on a deadline to update an existing course that will only be viewed through an LMS, and need the zoom to work.  How do I get this issue resolved?

Traci P

@Joyce, Last I heard from the ticket submission is that they have noted it as a possible bug. Sadly my workaround was to remove all my zoom regions, make new slides, paste all the content to each new slide, and then redo the zooms. Not ideal so I hope there is a fix asap. I'm working in 36o though. Have you tried just pasting your slides into a new shell?

Leslie McKerchie

Sorry that this is impacting you as well Joyce, but I do see the report that Traci referenced (thanks for the update by the way).

I will add this thread to the report as we track user impact and so that we can update here when we can.

I wanted to share some information on how we define bugs and how we tackle them when they occur.

Tom Roth

Any updates on this issue? I have the latest SL360 (3.12.14647.0) and am experiencing similar issues where the zoom region will randomly jump around a bit. If I delete the zoom region and recreate it then it may work fine or it may not. 

But another zoom region issue is that it won't zoom in as much as I've set it to when using the zoom transition speed set to very slow. Instead it just zooms a little bit and stops far short of where it's set to zoom to. This happens in the preview and in output. I've played with creating a brand new SL file and that didn't help. Upon testing further I have found the zoom region does zoom where I tell it to as long as I don't use the very slow transition. So using slow, or medium transition work but as soon as I set it to very slow it'll not zoom in as much as it's supposed to. I hope this bug can be addressed in the next update.

Leslie McKerchie

Hi Tom, 

It looks like the specific issue that we have reported that is still unresolved on this thread is where the slide displays quickly, then jumps to the zoom region that is set at the start of the timeline. Is that the issue you are referring to as well?

You're describing another issue I'm not familiar with. I'd advise to share a couple of samples with our support engineers here so that we can take a look.