Does anybody know if Storyline 2 supports Hi-DPI displays?
I have a Lenova Yoga Pro 2, which has a 3200 x 1800 display. The original Storyline doesn't support this resolution, so I have to down-res my display to 1920 x 1080. I have made a feature request for this a while back, but with the release of Storyline 2 I doubt I will ever see this supported in my version.
OK, so after I posted this, a section with "related content" appeared.
Seems there were a few other posts on this....the comments were from a little while ago, so I am wondering if anything has changed? From what I have gathered Storyline 1 & 2 both require 96 DPI and can only support up to 1920 horizontal resolution.
I ran Storyline 1 on a 27" iMac which is 2560 x 1440, which is more than 1920. Running two BenQ LEDs at same resolution with Storyline 2 with no problem currently.
Storyline 1 resizes text boxes and changes font sizes when opening a file built pre-MacBook w/ retina. Yet, anything I build in Storyline 1 on this setup remains fine.
Well yeah I can run Storyline 1 at 3200 x 1800, it just gets hard to look at. Like impossible. This is a terrible oversight on Articulates part. I image your resolution problem has the same problems, but since it is not much higher than 1920 x 1080 it's not as noticeable.
So I basically paid a premium for a laptop that I have to downgrade to work with Storyline. If anyone else is considering a new monitor or laptop, go with a 1920 x 1080. Or buy that higher res display, and use a different authoring software that can take advantage of the higher resolution.
You may find that user interface elements in Articulate Storyline are small and difficult to read on high resolution monitors—generally, monitors that display more than 2,000 pixels in width. We're working to improve performance on HD monitors. In the meantime, you may need to reduce your screen resolution while working in Storyline.
Unfortunately there isn't an update to share at this time, but it is something our QA team is continuing to look at and investigate. Once we have additional information to share we'll be certain to include here.
I do not have an update to provide on this issue and we do not share product roadmaps or timelines. We do have this thread tied to our report so that we can update when applicable.
Would be great if this can be fixed soon as I'll be having a sharing with fellow colleagues & clients on the advantages of using Articulate Storyline 2 to create rapid e-packages.
I will just add that it is completely unacceptable that Articulate STILL has not addressed this.
For crying out loud, my original comment was 11 months ago. Hi-DPI monitors have been available for years. The fact that a graphics driven program still has no clue how to address high resolution at this point laughable.
It's just a feeling I have, but I think maybe they are rolling a lot of fixes like that into the next version of SL. This may not be an easy change to make with the framework used to create SL2, just guessing on that one.
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.
12 Replies
OK, so after I posted this, a section with "related content" appeared.
Seems there were a few other posts on this....the comments were from a little while ago, so I am wondering if anything has changed? From what I have gathered Storyline 1 & 2 both require 96 DPI and can only support up to 1920 horizontal resolution.
I ran Storyline 1 on a 27" iMac which is 2560 x 1440, which is more than 1920. Running two BenQ LEDs at same resolution with Storyline 2 with no problem currently.
Storyline 1 resizes text boxes and changes font sizes when opening a file built pre-MacBook w/ retina. Yet, anything I build in Storyline 1 on this setup remains fine.
Well yeah I can run Storyline 1 at 3200 x 1800, it just gets hard to look at. Like impossible. This is a terrible oversight on Articulates part. I image your resolution problem has the same problems, but since it is not much higher than 1920 x 1080 it's not as noticeable.
So I basically paid a premium for a laptop that I have to downgrade to work with Storyline. If anyone else is considering a new monitor or laptop, go with a 1920 x 1080. Or buy that higher res display, and use a different authoring software that can take advantage of the higher resolution.
Hi Marc,
You may find that user interface elements in Articulate Storyline are small and difficult to read on high resolution monitors—generally, monitors that display more than 2,000 pixels in width. We're working to improve performance on HD monitors. In the meantime, you may need to reduce your screen resolution while working in Storyline.
Hello Ashley,
I have the same problem, any update regarding this issue ?
Hi Fadi,
Unfortunately there isn't an update to share at this time, but it is something our QA team is continuing to look at and investigate. Once we have additional information to share we'll be certain to include here.
When will the update to solve the resolution be ?
Hi Thomas!
I do not have an update to provide on this issue and we do not share product roadmaps or timelines. We do have this thread tied to our report so that we can update when applicable.
Thanks for the response.
Would be great if this can be fixed soon as I'll be having a sharing with fellow colleagues & clients on the advantages of using Articulate Storyline 2 to create rapid e-packages.
I will just add that it is completely unacceptable that Articulate STILL has not addressed this.
For crying out loud, my original comment was 11 months ago. Hi-DPI monitors have been available for years. The fact that a graphics driven program still has no clue how to address high resolution at this point laughable.
It's just a feeling I have, but I think maybe they are rolling a lot of fixes like that into the next version of SL. This may not be an easy change to make with the framework used to create SL2, just guessing on that one.
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
This discussion is closed. You can start a new discussion or contact Articulate Support.