I recently discovered another trick to prevent layout from crashing.
It is hard to gather all the knowledge about how to navigate Layout’s speed bumps. I wanted to share the things that I do, maybe if everyone shares their tips, then everyone can access this information more quickly and easily than sorting through hours of videos (not to diminish the value of educational videos).
Initially layout large files with models in Raster, because that is the fastest for Layout to handle.
In the main Default Tray, under “Sketchup Model” make sure the “Auto” box next to Raster/Vector/Hybrid is UNCHECKED. Then Layout will not try to continually render your model. Then you have to manually click the “Render” button for each viewport after you make changes to your model.
When Layout crashes while trying to render a model, first render it in Raster, then it is less likely to crash when switching it to Vector.
File > Document Setup > Paper > Rendering Resolution: keep Display Resolution to LOW and you can keep Output Resolution at HIGH.
If you have a secondary monitor, it might be causing Layout to run slower. When I unplug my secondary monitor, Layout runs faster.
I click inside the plan and section viewports so as to involve “panning”, and click out without any changes. That breaks the live link to camera settings for the scene. So now I know updating a scene in SU carelessly will not shift my viewport geometry around. This became very much easier in LO 23 where “pan” is the default tool inside the viewport.
I also keep a small vignette of my project on a separate “on every page” layer. That’s nice aesthetically, but I use it as a “button”: I right click that small viewport and update my model easily even if all other content is on locked layers. That’s easier than going to “document setup” to update SU model.
I give “real map coordinates” using prefix numbers before automatic coordinates in labels, like this pair of UTM coordinates:
7 354 <Coordinates(y)>
This adds distance from map zero to the coordinates. You have to set model origin to fit so that the last digits given by sketchup adds up to the correct coordinates, obviously.
I reuse scenes to many viewports. All elevations are derived from one SU scene, and I choose “front-back-left-right” in standard views for the viewport to set that up. That works as long as not every elevation has its own section cut to cut terrain shown in the elevation.
I keep SU tags logically organised in folders for main themes, like: surroundings, the actual site, help geometry, stories folder, all stories (where all building component tags go), so that I can more easily override tags for a viewport on tag folder level.
I use “always face camera” on grid notation components, and different tags for each grid of different orientation, so that I can reuse an elevation scene and have numbers not being mirrored. Parallel grids on both sides of the building are then instances of the same component.
I am using 3D Connexion CAD Mouse and for some reason I can arrange this in Sketchup but I can’t do it in Layout It dosen’t recognize Layout app in Windows 10, only the app I used before the Layout app
Do you have any ideas how to do this on Windows 10?
Some interesting methods there. Some I do not yet understand.
The vignette, are they on the sheet or off to the side? If you have multiple SU files linked, do you have multiple vignettes? The whole idea is a time saver?
Why the real map coordinates in labels?
The grid system is interesting. But having the grid in the SU versus in Layout creates some complexity, I assume. Do you put the grid on a separate layer to control the visibility of the grid? In other words, so the grid be on top of the drawing?
yes. without it I would have to unlock the layer so as to get something to righht-click on to update the model, and then lock it again afterwards, or keeping “document setup” open, which is not ideal.with multible models I would need multiple “vignettes”, and they could just as well be off to the side of the page.
The label auto text for <Coordinates(y)> and <Coordinates(x)> reads out the distance from origo in the scene ( with the axis used in the scene) so if the x-coordinate on my map is 7242333 meters from map zero for a certain spot on the building I would place my building x = 333 meters away from model origo. The layout label would then report x=333. I would then just manually add 7254 in front of <Coordinates(x)>, so that it add up to 7242333 m.
This label I can copy around and get coordinates all around the building automatically.
On a section I would need to have a stacked viewport on top to show the grid properly with all the other tag for that viewport turned off, or just accept as I do, that the grid is partially invisible on section cuts.
I have my building grid inside the sketchup model because I actively use it for reference all the time while modeling. Some say they make the grid in Layout, but that makes no sense to me. I would give measurements in Layout that refer to that grid, and if the grid is Layout geometry I would get paperspace measurements and not the real distance.
I also place the grids in SU and then in Layout, place them in a layer titled “References”. That layer also holds other references, such as the center points of circles, etc. Then I draw grid lines in Layout snapped to the SU grid lines. Draw one, copy the others, two seconds. That way the grid lines are drawn for the viewport. I hide the reference layer for PDF exports.
I had not considered adding labels with “always facing camera” on. I have tried making the grid lines translucent planes as I do with building setback lines, property lines, etc. The jury is out on that method for me; it gets a little busy. I think your way is better, simpler and cleaner. I will try this next time.
Thanks, Paul. I am aware of those practices. You see, all the tags on because I was compiling multiple models into one. That house layout is driven by a post and beam structure (that you mentioned) that had to be communicated to the engineer and then approved. You can also see floor trusses that don’t fit the floor sections floating around that the engineer changed. Now that I have the final structure from the engineer, I am adjusting the plan, and I will delete the structure.
I choose this point to convert to version 2023. With version 2022, I found I had too many models that were just imports of the base model. Such as imported models for section planes, elevations, interior elevations, etc. It took too long to update the imported model and then update Layout. The reduction in linked models and the multi-core faster update of SU remaining imported models was beginning to work for me. Until vector line issue.