I don’t work on interiors but I do work on large housing developments (so, models with hundreds of uniques rooms, plus exteriors, 100s of scenes & tags, etc). I use the following methods for doing large numbers of glazing schedules or exterior elevations & plans in LO.
First, I split the model into two basic types (two is ideal, but sometimes 3-4 if it’s a really large project).
SKP file 1 is the “Basic” "structure; it contains only the information about the structure and finishes are needed to produce the technical drawings in LO (the Plans/Elevations and maybe Lighting Plan etc). This SKP model is sent to LO (sometimes more than 1 LO file, eg upper and lower floor) to be (typically) be rendered or hybrid mode, and dimensioned so it needs to be kept fairly simple.
SKP file 2 is a “HQ” (high quality) version. This references in the SKP file for the Basic Structure but adds all the detailed components that are used for rendering (enscape, in your case) such as furniture and soft landscaping. This model will contain a lot of scenes, but they wont be sent to LO (the file would be too big anyway).
Either model can be used as the main design tool.
If you find that this process doesn’t work because your model is organised into a different component heirarchy then I know a few workarounds involvng rendering proxies (if you want me to explain, ask in a reply).
For scene management, Eneroth makes a scene manager/organizer extension that works for transferring scenes (and camera views) between models.
@kengey has a good extension for auto-rendering LO and scene export, which I think will come in handy for you.
So, on to the scene-reduction method:
To cut down the number of scenes sent to LO you can put as many wall elevations as possible into one scene. I don’t use sections unless absolutely necessarey because I find that organsing them (will all the tags and styles they generate) becomes a nightmare! Instead, if you are able to, make each wall a component containing everything that belongs on that wall (including glazing, skirting board, etc). Then arrange all of the wall components in your SKP model off to one side from the main 3d house, in a grid array with all walls facing ‘up’.
Then it’s possible to create one scene (a plan view) that captures ALL of the elevations at once.
In LayOut you can bring in that scene (viewport) and crop it down (and scale it) to just the info shown on one page (eg 4 interior elevations).
For the plan view I would do the same; use one scene for each level in the house, and crop it down to room-by-room plans.
so conceivably you could have just a handful of scenes to represent every room plan and elevation! (realistically if the model is huge you will want to break it up to practical numbers)
Warnings & notes:
- There’s a practical limit to how much you want to send to LO (especially if rendering in vector or hybrid mode), so maybe putting 200x4 elevations into one viewport is too much…try for 50 or 100 to find a balance between No. of scenes and rendering time and admin time.
- Once it has been created, try not to shuffle the grid layout or update the Scene’s camera position, since it will shift all of your LO viewports.
- If your modelling component heirarchy allows it, then you can utilised stacked viewports to create a second scene that contains the complex geometry (3d mouldings, light fittings, etc) which you can render in Raster mode.
Organizing a model based on “wall” components may not be your typical workflow… For example if (like many people) you might have all of the skirting boards in one single component …if tha’ts the case then you will need to ‘explode’ that down to individual skirting board components and use a Tag to organize them (and the Selection Toys extension will be invaluable here). This method of modelling is a bit daunting at first but it actually works quite well if you can get the hang of it.
You dont necessarily need cross-reference organizer. Cross referencing can be done manually just with a windows folder full of all thecomponents you want to load. In the component browser you can rightclick any componet and select “replace”. There’a good extension call Component Replacer that may help if you are bringing in components between models.
Layer Organizer is another extension that could help since you can stack layers meaning a more compact menu…but since 2020 I dont know if it works (tags organizer?)