Layouts, margins and screenplay problems on BETA 2.9.017

Hello !

I try to use scrivener instead of Final Draft for a project , and I must say that I have big problems for very basic things.

  • the text is too far on the left in page view, it doesn’t us all my page and I have too many line breaks (especially too little place for dialogs ).
  • the layout is not the same between Scrivener in page view and a compiled or printed project (a lots of margin problems).
  • if I try to edit the screenplay settings and update my document, it crashes.
  • when I compile my document, the top or bottom margins are very small.
  • the short cuts to switch between elements (action, characters, dialogues…) doesn’t works. Refering to the manual, I tried CTRL + number, and variants without success.
  • if I try to edit the paragraphs in the screenplay settings in centimeters, the numbers doesn’t looks like normal at all
  • many other problems…

I have to compile my documents regularly for reading and even if I like the scrivener approach that suits me better than Final draft, the experience is quite horrible.

Are these problems known and do you know if the team plans to correct it soon ?

Hello!

We are aware of some bugs with Scriptwriting at the moment, but I want to make sure that we have all of your concerns as accurately as possible:

This may be an issue with your right margins. Do they look okay when you are not using page view?

This can change drastically based on your compile settings, which you can alter to be whatever you’d like at the time of compile. Which format are you compiling to?

We are aware of this bug and it has been filed.

This can be adjusted in your compile settings, as mentioned in point 1. What margins are you trying to achieve?

The shortcuts for script elements first require the key combination “Ctrl+/” This will bring up the script elements menu, after which pressing the assigned letter will select the chosen Element (A for Action, C for Character, etc)

This is a known bug having to do with our ruler. It has also been filed.

Thanks for your feedback!

Hi and thank you for detailed answers !

1/samlawry wrote:

  • the text is too far on the left in page view, it doesn’t us all my page and I have too many line breaks (especially too little place for dialogs ).

This may be an issue with your right margins. Do they look okay when you are not using page view?

It looks right yes

2/
samlawry wrote:

  • the layout is not the same between Scrivener in page view and a compiled or printed project (a lots of margin problems).

This can change drastically based on your compile settings, which you can alter to be whatever you’d like at the time of compile. Which format are you compiling to?

I use the default settings. I need something really simple.

3/ samlawry wrote:

  • if I try to edit the screenplay settings and update my document, it crashes.

We are aware of this bug and it has been filed.

It would be great if you can correct it.

4/ samlawry wrote:

  • when I compile my document, the top or bottom margins are very small.

This can be adjusted in your compile settings, as mentioned in point 1. What margins are you trying to achieve?

I didn’t check the compile settings. Maybe I don’t use it enough, but I would like a very basic workflow.

5/samlawry wrote:

  • the short cuts to switch between elements (action, characters, dialogues…) doesn’t works. Refering to the manual, I tried CTRL + number, and variants without success.

The shortcuts for script elements first require the key combination “Ctrl+/” This will bring up the script elements menu, after which pressing the assigned letter will select the chosen Element (A for Action, C for Character, etc)

Thank you for the tip !

6/
samlawry wrote:

  • if I try to edit the paragraphs in the screenplay settings in centimeters, the numbers doesn’t looks like normal at all

This is a known bug having to do with our ruler. It has also been filed.

Great !

Good bye and thanks again.

Margins & Layout in Script Mode are still seriously messed up in Version 2.9.0.36 Beta.

Why can’t we just have a professionally and reliably coded update to the former Windows version?

Hasn’t it been 3 years since the new windows “Update” was announced?

I thought that after that amount of active development time I could rely on the current beta version of the “update” to be mostly stable and at least do the must fundamental tasks reliably…

Pretty ridiculous of me right?

I just imported the text for a screenplay I’m working on into the Windows 2.9.0.36 Beta to finish and format it for a Screenplay output. But then I notice that the margins and layout are much too wide on the right, too small on the left and the line height is vertically offset so that the cursor is always significantly too small for the font size selected and located below the text I selected.

The updated windows version has been in “Beta” for a significant amount of time. After that length of development this sort of drastic problem should not still persist. It’s far from hidden. If someone just tries using the software in the Script Writing mode I don’t see how they could miss it.
Also, (according to this thread) most of these problems were reported previously… so, not exactly an unknown bug.

Presumably, these sorts of glaringly bad problems should’ve been fixed already. And still, here it is messing up my day, preventing me from completing the basic, simplest function I needed it to do.

This has set my schedule back probably another day, (maybe another week?) while I look for a solution.
Scrivener is not making my work faster, it i actually delaying me now. It has become a problem, not a solution.

What is happening?

Also, in case people ask, I did not make any changes to margins or formatting. I am using the default Template that Scrivener provides when someone chooses to create a new document.

Try the latest Beta 38. It has major fixes for Scriptwriting when using a non-HighDPI monitor.

Just a reminder that this is Beta testing forum. If using the latest Beta causes you pain and slows you down, you should stay away from it.

When you post a bug/error message, make sure that you use the latest version. A lot of people complain about the short time span of our releases, but this saves us time dealing with cases reported not on the latest version, like this one.