Storyline for high-dpi monitors on Windows 8.1

Thanks for popping in to share Neil! I did want to let you know that replying to the forums via e-mail attaches your signature. You are welcome to pop in and edit if needed.

I'll check out the driver situation, thanks Neil!

At this stage I need to continue developing in Storyline for at least another 3 months while i finish a contract, so I'm happy to check out any ideas. As it stands, it looks like Im going to have to dig out an old dinosaur of a laptop, which kinda defeats the purpose of buying a shiny new Surface :(

Wow. I contacted Articulate in December about this issue when I got my Surface Pro, which I returned because of this issue. I was told the problem was because of the Surface Pro's irregular resolution. Fast forward 9 months when I finally get another laptop, with 1920 x 1080, which is probably the most popular resolution of laptops today...  

So I get the latest version of Storyline 2. It must be fixed by now... NOPE! STILL NOT FIXED!

Maybe your programmers could read this for the reason this is happening:

http://www.danantonielli.com/adobe-app-scaling-on-high-dpi-displays-fix/

HI ashley got any updates on progress?

Hi everyone,

I wanted to share a further update regarding our plans to add support for high density displays to Storyline.

For some time now, we’ve been working on adding support for high density displays to the next version of Storyline. Once preliminary support was in place, we invited a number of you to the Storyline Beta Program to help evaluate the feature.

While we’re now broadly satisfied that the feature works as intended, reaching this point has proven far more challenging than simply flicking a switch. Storyline does an incredible amount of custom drawing behind the scenes, including rendering complex slides with multiple effects, animation etc. Consequently, we’ve encountered numerous issues along the way (sometimes limited to obscure combinations of hardware and operating system), all of which have taken considerable engineering effort to resolve.

After extensive evaluation, we’ve determined that the engineering effort and risk required to re-implement the feature in Storyline 2 as an Update is simply too great at this time. In reaching this decision, we’ve been particularly mindful of the need to prioritize this feature amongst other upcoming bug fixes and other issues that we’d like to address through the Storyline 2 Update program. We’ve also considered the availability of viable workarounds for this issue – such as changing display resolution when using Storyline, or using Storyline on a standard density display as part of a multi-monitor setup.

While this news will understandably be disappointing to those of you affected by this, I wanted to underline that we remain committed to supporting Storyline 2 customers with regular Updates. Most recently, Updates 8 and 9 (May 2016) and 10 (July 2016) resolved a number of significant issues that broad sections of our community were encountering in areas ranging from the visual quality of slide notes to issues with the way courses communicate with an LMS.

I’d be happy to provide more context around this decision or discuss further individually with anyone who’s interested. We'd also encourage you to reach out to our customer support team should you need help with any of the workarounds suggested above.

Simon Taghioff
Product Manager
Articulate

Scott,

That manifest file solution is what I suggested a while back.  There are some issues with it though.  While it does fix the problem to a degree, there are certain things that get messed up (I don't know what personally, because I don't use the software, I just support it).  For my users I have just created two links to StoryLine, one with the fix, and one without the fix.  Basically just two different shortcuts, one with DPI scaling checked, one without.  They said this works well for them as they can use Storyline with the fix so they can see what they're doing, and then the couple of things that it doesn't work for, they just save, close, open in tiny view and do what they need to do.  

Simon,

So basically if we want StoryLine to work on modern hardware, wait for the next version and cough up $$$$.  Not awesome.  Will definitely suggest we look into other software when it's time to upgrade.

Simon

So Articulate decided the juice was not worth the squeeze.   I think Articulate failed to consider the users who use high resolution displays are (were) the demographic that group that is (was) most likely to purchase upgrades.   

That Articulate viewed this repair as an option speaks volumes about its lack of commitment to its products.   No support for Mac or quality displays, is the next version coming out in DOS?

-------

Nic

I meant to click "Mark as Helpful" but accidentally flagged your post.  Sorry!  My eyes are shot from looking at Storyline on a Surface.

You, sir, win for the day.  Well done.  Lol

Hello frustrated hi res laptop users of storyline2 - there has been a solution for this for some time now

I have a high resolution laptop and there is a perfect solution for this that works for me.

Maybe it has not been picked up because it does not fix the problem on the laptop  but  I find it impossible to develop learning material without two screens to work on at the same time anyway.  

I pluged in an external lower res monitor and set the resolution to 1920x1080 

in the display seetings also set the text size to 150%

in the properties of the storyline2 shortcut ie right click on the shortuct to storyline2 there are options you tick which ive highlighted below  to solve the issue

when you re start storyline using shortcut, minimise the dialogue and drag it onto the other screen then maximise it again and you should be all sorted

After reading that the developers have hit a wall i hope they dont remove this feature !!!!!

But where do I plug in the phone line for the 14.4k modem?

I've also had success of sorts with the fix above, however I've found that it does some strange things to the layout of objects in existing story files if I edit them in this environment - primarily text box alignment and bullet lists. Unfortunately it's not consistent enough to report to support.

Thanks Adam for sharing that workaround here. I know it's something a few other users have looked at utilizing, but it's worth noting that it's not a supported workaround. As such, Katrina that may be why you see some things not working as expected, but it's not something our team could offer support for if you're not using the DPI settings as described. 

I suspected as much, but until the developers give us an official fix, it's going to have to do :)

i have noticed the bullet point thing before and just went and re formatted them all uggh maybe they will not work when it gets sorted out or i move to another machine

ive tried to eidt an engage interaction in engage 09 and it does not work using above settings just wondering if the studio 13 has the same issues and is there a license upgrade path from 09 to 13?

Hi Adam!

This is a Storyline thread and I'm not following the issue you are reporting for Engage. What issue are you seeing with the bullet points? Do you have a .intr file to share that we could take a look at? I could upgrade and publish for you to see if it alleviates the issue you are asking about.

It may be best to move this conversation to a support case so that we can best assist. You can send the file here.

I wanted to try Storyline 2 but obviously after years of knowing about the 4k issue, Articulate still has not been able to solve the problem. I'll be uninstalling Storyline 2 and recommending that my school not consider this product.

It was so annoying I found a working solution and would like to report here:

This is motivated from a post here.

Please use this with your own risk as it may disturb your registry settings.

This is what i did to work:

Step1:

Press Windows Button + R, type “regedit”, and then click OK.
Navigate to the following registry subkey:
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide
Right-click, select NEW > DWORD (32 bit) Value
Type PreferExternalManifest, and then press ENTER.
Right-click PreferExternalManifest, and then click Modify.
Enter Value Data 1 and select Decimal.
Click OK. Exit Registry Editor.

Step 2: 

Now place this file (attached in this post) in the same directory as your storyline.exe .....

 C:\Program Files (x86)\Articulate\Articulate Storyline 2

It is working for my Windows 10 QHD!!

Thanks SS for sharing - and although it may work, I have to reiterate that any changes like the above cannot be supported by Articulate. So please use with extreme caution. 

So, to sum up... this issue is solved in the 360 version but not in 2 because you think it isn't worthy? 

That's what I'm picking up as well.  Great support! 

Hi Nicolas, 

The issue is solved in Articulate 360, as we were building that from the ground up while the issues with Storyline 2 and the high resolution machines were becoming more prevalent. Our team looked into using the same concepts and porting them back into Storyline 2 and after extensive evaluation, our Product team determined that the engineering effort and risk required to re-implement the feature in Storyline 2 as an Update is simply too great at this time. In reaching this decision, we’ve been particularly mindful of the need to prioritize this feature amongst other bug fixes and other issues that we’d had on the list to address within updates to Storyline 2. We’ve also considered the availability of viable workarounds for this issue – such as changing display resolution when using Storyline, or using Storyline on a standard density display as part of a multi-monitor setup. 

I also wanted to ensure you that we remain committed to supporting Storyline 2 customers with regular Updates. Most recently, Update 11 (Oct 2016) resolved a number of significant issues that broad sections of our community were encountering in areas ranging from a missing Storyline program icon to languages inconsistencies with built in states. 

Hi Ashley,

I think it'd be easier for us if we knew when we'd get some relief - short of buying a new monitor to lug to my client's office I cant use the lower density display monitor fix, and setting everything to display at a lower resolution really isnt helpful as it makes other windows practically unuseable (and as Im sure you know development often requires multiple programs open). Im muddling through with the unsupported 'disable DPI' semi-resolution, which is causing headaches because of the random quirks it causes to formatting.

I absolutely appreciate that these arent  a 'flick a switch' fixes, and can understand that Articulate wants to wait til #3 to release this fix, but the strategic decision to not provide estimated due dates of release are what's causing me the real grief.   If it's going to be fixed in the first quarter of the year, I dont mind hanging on a bit longer. If it's December next year, that presents much more of a problem. 

Hi Katrina,

I understand - and I do wish I had more information to share. I promise that we're not being coy about dates though, we just don't have a date locked down as it's still a bit more fluid as we look to what other features and or fixes could be included. 

The need of this particular fix is something that our team and the Product team are intimately aware of, and I'll continue to press the sentiment and need from customers such as yourself in our conversations with them. Thanks for continuing to share your honest and candid feedback with us here - as that's exactly what we need to know!