I dont understand how this works. Whenever we override styles in Layout, they show in the menu as if its been changed but they switch back to the original style…
In a temporary model I created my “override” styles in SketchUp and then saved them to a Style folder somewhere in my work folder.
In SketchUp I entered the path to the Style folder in preferences…
They then appear in Layout in the Model Tray…
1 Like
Could you share the fast modeling style?
Kinda agree, but that’s just because i avoid LO, for the simple reason collegues need to be able to add info to the documents.
So i model everything in SUP and export images which get (semi) automatic updated in a word template document. You could say Word functions as LO for me/us.
If you hate it, just skip it. Nobody forces you to use it 
This is very easy to make on your own but also requires a dedicated scene
You can set it up via creating a new scene, which will prompt you to save as a new style. The key elements are:
Profile edges off
Hidden geometry off
Shadows off
These three tax the graphic card the most.
The dedicated scene you create is the one where you do all your modeling. It is my first scene named “working model”. You can call it whatever you prefer.
If you use high res material imagery, then also textures off. Personally I don’t do this, and prefer managing texture size.
Gotcha. I think my entire SKP model uses that style 24/7
1 Like
You should use different styles for floor plans, elevations, vector work etc. to really take advantage of SU/LO. But when you do actual modeling, use the fast style.
I only make drawings for canopies, no floor plans. Can you screenshot an example?
Here’s our scenario.
-
In the office we have a folder on the server that has the styles that we point to.
-
We change the style of a scene IN LAYOUT
-
The end of the day come, we shut down our computers and come back and reopen the file in the morning.
-
The layout shows that there was a change to the style because the menu box is grey BUT the viewport now shows no change.
We have not been able to make this workflow work for us.
Also, do many style in the sketchup scenes slow down layout?
This is likely due to you modifying the scene from inside layout. You should always modify the scene in SU, then update the reference in Layout. Editing the SU model and scenes from inside LO is a recipe for disaster.
We haven’t edited scenes in layout. We have only tried to update the style (and more recently tags) When the style is changed inside of layout, it causes this behavior.
I will add that we work off of a server, I don’t know if that’s important info.
Changing the SU style in LO is editing the SU scene in LO, since styles are associated with the SU scene.
Your better option is to setup SU templates that already have specific styles associated with specific scenes.
But what im understand from users like @DaveR and @PaulMcAlenan is that this is how they work. They have one simple style inside of sketchup and then in layout point to their more complex styles and change it within layout… unless I’m understanding it wrong.
I am currently doing the way you are describing, I have all of my styles inside of sketchup and my scenes are managed with each style. It’s when I try this other way suggested (that we’ve abandoned because it doesn’t work) that layout breaks for us.
I respect both of those guys and their work. However, since styles are a significant part of scenes, then modifying the style from within LO is modifying the scene. I find leaving that work inside SU is much faster since you simply resolve that aspect of the scene by simply updating the reference file which you still have to do regardless…so one step instead of two.
1 Like
In one of the earlier 2023 releases I was experiencing a bug that would not save override styles.
The bug appeared to only affect copied viewports and not viewports that had been inserted via File > Insert.
I’m not experiencing the bug with the latest release.
I agree that LayOut has more issues, and less polish, than SketchUp, and it does bother me, given the market(ing) for architectural work w/ SU. LO feels a bit back burner. Needs some quality of life improvements, and performance improvement. But at this point I’ve honed my workflow to it and it’s fine for me. My only big performance gripe with it is lag with text input. It was crashing constantly for me in 2022, but that seems fixed now. One alternative to LayOut is to export PDF or image from SU and then edit with Bluebeam PDF editor. Bluebeam has lots of markup tools, including scale tools which would allow quick dimensioning similar to LayOut (without the snapping). But I’ll continue to use LO for its integration with SU (dynamic viewports, snapping, etc).
Bluebeam does have snaps if your views are in Hybrid / Vector!
The biggest issue with Layout is the Hybrid / Vector rendering. If you have even a slightly complicated model, forget about it… You cannot export a PDF to Bluebeam and use snaps unless it’s in hybrid or vector… so good luck using Bluebeam without it. This exact issue is one of the great fallbacks of Layout. Then, if you don’t want your sheets to look like something from the 80’s you have to set your image resolution to high making a HUGE file size…
Layout is so bad… so so bad.
How many edges and faces constitute a “slightly complicated model” in your opinion? My largest has less than 300 000 entities - it is a competition entry for a largish art museum.
That’s why you separate scenes that can be hybrid or vector rendered that are simple and not the entire model. I hybrid render just the section cut. Everything beyond the cut is raster.
Isolating the section cut keeps the LO file light and fast. When printed raster does not look like it does zoomed in on a screen. So many people forget that.
My pdf sheets print in seconds.