Storyline 2 behavior on QHD screens is TERRIBLE, no scaling! Please Help!
May 22, 2015
I bught a new QHD Notebook - Acer A7 with 2560x1400 display resolution. Notebook has 13.3 display, win 8.1 and Articulate windows look so damn tiny that you can literally brake your eyes trying to look out for objects, buttons and etc. It is a pain in the eye trying to work like that. I have tried to change the scale of windows just to be able to work in Articulate properly, but sadly to no effect! It doesnt change anything in app scale.
In such events, when hi-res displays are becoming a standart and even higher res displays like 4k are coming out, I think it is crucial for Articulate team to give users an update fixing that issues ASAP!
I just cannot work on my notebook, had to roll back to my old one coffin-look monster just for Articulate sake. And I am planning to travel soon, so I cannot drag both around and I dont want. Please solve that!
Maybe Windows 10 may solve that? Does anybody know?
85 Replies
This post was removed by the author
Hi Jay!
We do recommend that you utilize 96 DPI.
As far as the high resolution, we are aware of this need although it sounds as if that is not what you're dealing with at this time.
For reference:
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.
Noup, it doesnt work, in fact 96 dpi makes everything 4 times smaller :) So it's gave me the opposite effect. Reducing screen resolution doesnt work for some reason either, that was the first thing I tried. I mean it doesnt do anything, all other windows elements grow bigger, but Articulate stays the same exact size :(
Hi Jay! You are welcome to share your thoughts on this in the form of a feature request.
This issue seems to be unique to Articulate. All of my other software scales automatically and looks great on the QHD display. I loaded Studio to see if it worked better but as soon as I leave native Powerpoint to test the output, it shrinks like Gulliver to a tiny size.
There has been numerous threads about the scaling issue. It is disappointing that despite the feedback - which started well over a year ago - nothing has been done to address the issue (https://community.articulate.com/discussions/articulate-storyline/storyline-for-high-dpi-monitors-on-windows-8-1).
I looked into the Captivate forum and I did find something that at least helps with a temporary work around. I lowered the resolution from 3200x1600 to 1920x1440 as I had done before and Storyline remained as small as ever. Then following advise with Captivate, I opened the Properties for Storyline and changed the compatibility settings.
Now Storyline is readable. This is a rough work around so I hope we see progress on real support for the higher displays.
Thanks Brent for sharing that here - and our team is aware that users are looking for a better set up for high resolution monitors, so we continue to share thread such as this one with them. Additionally you can also share your thoughts with our team directly by submitting a feature request.
This worked really well on an external screen set to 1920X1080 running off a Surface Pro 3.
I would add that besides the screen resolution issue, I've also had a lot of problems using the Surface touch interface with Articulate.
Hi Kenny,
Can you tell us more about the issues you've run into on the surface? Was it authoring or viewing the published output? You can see the options we support for the Surface here.
Ashley,
I'm using the Surface Pro 3 with Windows 10. This is in reference to authoring files. For starters, because everything is so tiny in the interface on the Surface's HD screen, it's very difficult to use the touch interface. My fingers are a little big for it to recognize what I'm trying to click on. Sometimes it just didn't respond at all to touch and I have to use the trackpad.
Hi Kenny,
I can't do much in regards to the UI and how it displays on a high resolution monitor such as the Surface, but we have shared the feedback with our product development team and QA in regards to the user experience We're working to improve performance on HD monitors. In the meantime, you may need to reduce your screen resolution while working in Storyline.
If there is another issue that you're experiencing while working on the Surface, please feel free to let me know and we can investigate that further.
Brent, you're the only one who has provided information that is even remotely helpful. I had to select Windows 8 and it only scales properly on my second monitor, not on my laptop. Still, it's nice to be able to read it somewhere. Great job.
Bret,
How did you get to that property box? When I open the Properties for Storyline 2, I don't get a compatibility option.
Hi Catherine!
Not within the software. Right click on your Storyline 2 icon on your computer.
Would you be able to share a screenshot of what Storyline looks like after this property change?
Hi Kenny, would you be able to share a screenshot of Storyline on your SP3 with the settings above from Brent? Many thanks~!
Hi Robbie!
Some of the posts you are addressing are a bit dated. You are welcome to reach out to the individuals via the 'Contact Me' option on the user profile.
This issue is driving me crazy! Brent's suggestions are helpful in that you can at least view and somewhat work with the program, but I'm still finding issues between text and image objects not displaying in the right place and size.
This makes me very wary of using SL as I don't feel confident that what I'm creating will render correctly upon output. I'm having the same issue working between HD and UHD displays as Jay had on this thread, and wasting a lot of time as a result.
I just submitted another feature request for this as well. Please articulate, help!
Hi Lalit!
I think we can address your fears perhaps. If you have items that are being out of place and the sizing being off, please be sure that you are utilizing Storyline in 96 DPI and here's how to switch.
In addition, you can control some of the browser and player aspects to prevent scaling. See this tutorial for details.
Leslie:
None of these work arounds are sufficient. I am forced to work in Captivate until Articulate resolves the issue. This should be priority one.
Thanks for your quick response Leslie. I realize you and the rest of the staff are trying your best to find alternative solutions to address this while your development team plays catch up. For that I thank you.
The reality, unfortunately, is that these workarounds are just not sufficient for users experiencing these issues. Adjusting the DPI to 96 for UHD users causes the system and every other application to become unusable, and seeing as I don't work solely in SL alone, but rather have a number of applications open at the same time, this just isn't going to work.
The only real solution is for articulate to make the change at the application level, which unfortunately has severely lagged. Until this is done, sadly I too, will have to look at other options.
I just purchased a new laptop.. and my first installation - Storyline 2. I was so excited. BUT, I am beyond disappointed to see that there are issues with my laptop (w/display 3200 x 1800) and the current Storyline 2 UI. I purchased this laptop specifically FOR Storyline 2. Never imagined I would have this issue! Please find a soon solution.
Well.. this issue is more then 1.5 years old! Look at my initial post date also (10 month ago). So I would not wait for anything soon, the developers dont seem to give much about few user problems with that. I am sorry, but that is true, otherwise they would have hurry a bit to solve that by now, right? We have no dates on when to wait for our fix also. Have a screen more than FHD? Forget about storyline, we dont care. Want to moan about that? Leave a "feature request", maybe in couple of years it will be answered.
This discussion is closed. You can start a new discussion or contact Articulate Support.