How many ways are there to make a screenplay? I simply go to file, new project, scriptwriting and choose screenplay. I do nothing else other than start typing in the scene page already there. and this is what I get:
The top is your screenshot, below that is what i get, and have gotten for the past 2 years with rulers included. Clearly Im not the only one.
I have a fresh version of windows 10 and this is the first scriv beta Ive put on it. Given its a fresh windows version the default windows display setings, scale and layout out was set at 125%. I have now put back to 100%. and it changes the wrap slightly (but still incorectly. This is what led me to believe this problem was getting worse as this efects how scrivener wraps text. which it shouldnt in any way.
Indeed your screenshot is about a different bug related to HighDPI/Non-HighDPI monitors. I believe your monitor is a non-high-dpi monitor with a 96 dpi native resolution, while HighDPI monitors use 2x72dpi(144dpi) resolution. Because of this we have an offset of 33% the regular scale.
When you have a combination of HighDPI/Non-HighDPI monitors installed, the situation does not get better. We are working on this too. It is not just a screenplay formatting problem, but a general text formatting problem on non-high-dpi monitors. Sorry for the long delay in fixing this, due to the constantly changing high-dpi Qt functionality and our source code interaction. Once we switch to Qt 5.14 (which introduces major HighDPI improvements) we will need to adjust it again, which is a heavy task.
Thanks for the explanation, Tiho, but…
Is there anything I can do about it? This is a non-trivial problem for screen-writing, a show-stopper. If there is nothing I can do about it, then I can’t use Scrivener 3.
The only solution for Beta 36 is to use a HighDPI monitor, but we hope to provide a working solution for non-HighDPI monitors in the following versions too. Most likely you will have to choose the monitor DPI type, if automatic detection does not work. Most likely moving a project window between High to Non-High DPI monitors will cause problems, but at least the single monitor mode case will be working as expected,
Here is some more info about my system (Windows 10, fully up to date).
Note that the second shot says there is a custom scale factor set of 175%, and the third says it is 125%! I can’t say I know why that is, and I wouldn’t want to touch these settings without knowing a bit more. Apart from the Scrivener beta, everything is working fine for me.
Simeva, you made me curious, so I took the moment and tested my very-well-known 17.3 in laptop on each.
InfoByIp got it right: 96x96 px/inch, or similar if you try their other sizes (bigger potentially better, if any. Their method also looks sound at first glance.
DPI love, on the other hand – at first wildly inaccurate, then I noticed you have to tell it how large your screen is before it can give any kind of answer at all – unless you just happen to be at the default 13.3in.
So I set my 17.3 via the tiny link, and…it said my screen was 103dpi. Not hardly. I would really give that one, DPI love, a miss…
The best way to check the DPI settings used by Qt is to:
open a Command Prompt or PowerShell console window,
Navigate within the Scrivener installation folder.
Type “qtdiag.exe” under Command Prompt or “.\qtdiag.exe” under PowerShell
You will see a list of Qt properties, like palettes, paths, etc.
You will also see a “Screens” group displaying the properties of each of your monitor.
Your monitor DPI is listed as:
“Physical DPI: 93.9653,94.0741 Logical DPI: 96,96 …” for NonHighDPI monitors
“Physical DPI: 137.763,137.504 Logical DPI: 144,144 …” for HigDPI monitors.
The Logical DPI is the important one.
A lot of other useful monitor information is also available.
Brilliant! Thank you.
So it reports Physical DPI = 81.xxxx, 81.xxxx, and Logical DPI = 120, 120.
So, back to the original problem (and sorry for leading this thread off into a discussion of my computer)…
What exactly is the threshold between a High and a Non-High DPI? And is it physical or logical DPI we are talking about?
And am I right to understand this means that the current Beta will not work properly on Non-High DPI monitors ?
Sorry I’m going off-track and just genuinely being curious here, I assume you (&a couple of others on this topic) write screenplays in some professional capacities, surely you’re currently using other screenwriting softwares. Any particular reason why you want to move to Scrivener? Same reason why people went from Word to Scrivener for novel-writing?
Disclaimer: I have both Scrivener 1.9 (patiently waiting for 3.0) and a screenwriting software.
Speaking only for myself here, but Scrivener is the only option for people who write non-linearly. It allows you to outline, do a treatment and write the script all in the same project. You can split your story in acts or any structure you desire and write it in any sequence you want without using several files.
I’ve been using Scrivener for ten years or so, for screenplays, short stories, a novel and other writing projects. I do use another screenwriting software, but only to add Mores & Continueds.
Quite so. It also allows you to organise research material, and to keep multiple episodes of a series together.
I have contributed to previous betas, but because of these display issues I have not even been able to view any screenplay projects yet with this one. I’m intrigued to know what it’s like, but my workflow is unaffected because Scrivener 1.9 is still the same masterful tool it always was.
I’d still like to know what is the threshold between a High and a Non-High DPI. I’ve never heard of this distinction before.
YEEEES - screenplay formating apears to be working in B37. I could cry tears of joy, HUGE thans to the tireless devs getting this one across the line.
I have noticed one quirk. when you are typing some action then hit enter and tab to go into character, scrivener adds an extra line above the characters name which it shouldnt do. Not sure if I should make a seperate post as this is a seperate bug?
