Help with Display Settings - Published SL Files

I work with display settings on my computer at 150%. When I work on Storyline files, I am at 150%. When I'm ready to publish, I change my computer display settings to 100%. I then complete the publishing and zipping process. When I upload my zip file to a SCROM on my LMS, sometimes the display settings on the SCORM file are fine but other times the text overlaps and everything is wonky on the screen. Is this a publishing error that is causing the overlapping on text? What seems to be the problem? I'm trying to figure this out. Is it the fact that when I work on the Storyline files my computer display settings are at 150%? Does anyone know? Any information would be greatly appreciated. Thanks in advance.

9 Replies
Emily Ruby

Hi Sandy, 

Are you referring to the slide zoom level or your system's settings? If the latter, and Windows is using a different DPI setting than the recommended 96 DPI (100%),  you may experience erratic behavior, such as:

  • Elements of the application are misplaced or distorted.
  • Objects are misplaced or distorted when previewed or published.
  • Zoomed images don't work as expected.
  • Font sizes are incorrect after using the translation features.

If you're talking about the slide zoom, this should be ok in Storyline 2, but in Storyline 1 caused issues in regards to resizing or moving elements. 

RECO Education

Hi Emily

My display system settings when working on the Storyline 1 files are 150% which is 144 DPI but when I publish I'm at 100% system display settings which is 96 DPI. I publish at 96 DPI. Is the problem caused by me working at 144 DPI? How can I fix the issue on the file. Do I have to work in the file as well at 96 DPI? I have visual problems and need to work at 144 DPI as 96 DPI is too much strain on my eyes. If I convert the file into Storyline 2, will that correct the issue?

 

Thanks Sandy

Ashley Terwilliger

Hi Sandy,

As Emily mentioned you'll need to work and publish at 96 DPI or 100% display settings. You mentioned you tried this on another computer whose default was 96 - was it the same file you were working on or a brand new file? The same file may still be exhibiting odd behavior based on the previous system settings - so if you're still having difficulty in a brand new file please let us know. 

Ashley Terwilliger

Hi Sandy,

As Emily mentioned before, working at a different DPI setting can cause issues in the file itself and once a file has an element of corruption, there is not always a way to fix it. You could try importing it into a new file as described here to resolve the behavior. Also, if you'd like us to take a look you could share the .story file here as well.