Compiler not creating Chapter headings

Hi, I have the latest build of Scrivener on Windows 8.
I’m trying to compile my manuscript to Word 2010. No matter what pre-installed compile setting I use, I can’t get Scrivener to add Chapter 1, Chapter 2, etc

I have my manuscript setup with folders for each Act (Act 1-3), then chapters underneath each act and scenes that make up the text beneath each chapter. If I uncheck “compile as is” for each chapter folder, it seems to create the chapter headings in the word doc.

But then it creates chapter 1, and the page is blank, no text. Then the next page is Chapter 2, with all chapter 1’s text.


Disabling “As-Is” is definitely important. In case you were unaware, the manner in which things are named is done in the Formatting compile option pane, and “As-Is” opts the item out from what happens in this pane entirely, merely printing its text content verbatim—so it’s useful for things like the title page, which would have completely unique formatting, no headings of its own, etc.

As to how this pane works, you may have a level 1 folder row in that pane that is handling the acts, and then a level 2+ (or all folders nested at a level greater than 1) for chapters, if you click on each you’ll see a preview that you can format directly using the provided tools. Then text files probably have their own rules as well. Since all of this is freeform and I don’t know what you have for settings, I can’t give you any specific advice—but the idea is to change that configuration to match your outlining style, or adjust your outline to better suit the system.

For example, if in your Binder you have “chapters” as a folder at the same level as the “scene” text documents (rather than indenting the text documents inside of the folders), and have text documents at level 2 or greater to print themselves like chapters—then that might explain the result you see. That’s just me giving one possible way in which the integration between compile settings and the outline could be out of sync with each other.

Page breaks on the other hand are handled in the Separators compile option pane. It could be however you arrange your scenes and chapters together is causing an extra break, depending on the provided rules. Another thing to check for is that each section can declare a page break for itself. As with “As-Is” it’s meant to be more for exceptions that do not fit into an easy predictable pattern like Separators can address, but if you’ve been experimenting with checkboxes, you may have left a bunch of them on that shouldn’t be. Check for that in the Contents pane.

If the concept of assigning types to levels (and icon types) is all new to you, you might wish to go through the description of how this works in §23.8, Formatting, of the user manual PDF, starting on pg. 239.