Hi guys. I have had some warning signs pop up. One I believe was a unrendered something ( sorry, daaahhh) . Is rendering in layout about the same as saving?
I read DaveR talking about view ports and the way they update each other.
So when and why do you render?
thanks for any help, didn’t find much on a search…
Correy
Render in Layout is not much different than having an option to Refresh, or Redraw what’s being shown on the display (i.e. computer monitor).
I’d say it’s main use is to get Layout to update any changes that take place whenever a user switches between the various Styles that can be assigned for any given viewport.
There might be an interesting way to use the Render option, but if so, we’ll need to wait for someone else to come in share what that might be.
You’ll suffer no real harm in using Render any time you want,… But I would not confuse it with the standard Save Option. Render is not going to write the file to disk, like the Save function does.
Rendering has nothing to do with saving.
Rendering is how the model gets represented. When you first import a SU drawing into LO it will be raster rendered. The good thing about that is that it is quick and dirty and imposes low demands on the system. So manipulating the LO drawing is easier, especially on low power computers or complex drawings. But you get jagged lines and it isn’t great for final output. You are likely to want to use Hybrid or Vector rendering for that.
Although there is a link between the LO viewport and the SU drawing, it is not dynamic. That is, when you change something in SU, it won’t automatically update the LO viewport. You have to invoke that manually.
A lot of this is because LO is unable to take advantage of advances in computing power achieved in recent years. There is a lot of pressure in this forum to see LO upgraded to something that is as impressive as SU itself in operation.
Except if you open the SketchUp model file from LayOut. Then when you save changes to the .skp file and go back to LO, the viewports will update automatically.
1 Like
Really? As I always use Send to Layout, I guess I never saw that.
It doesn’t really have anything to do with Send to LayOut. It doesn’t matter if you send to LO or insert the model via LO’s File menu. You can open the SU file by right clicking on a viewport and selecting Open with SketchUp. If you do that, LO watches for the Save in SketchUp and updates the reference. It’s the same for text, spreadsheets, and images if you open them in their default applications from LO.
2 Likes
Are we at cross purposes, Dave? Here’s my standard workflow: create model in SU; use Send to Layout to get model into LO; edit drawing in SU (often still open); revert to LO and have to invoke update manually.
I guess it would be different if you had already created and saved the drawing files, then opened the LO drawing, and then invoked Open with SU.
No Simon. We are not at cross purposes at all! Your work flow is fine. I’m just telling you that you don’t have to manually invoke the update after editing the SketchUp file if you open the SketchUp model file from LayOut.
If you go back to edit a LayOut file you were working on last week, for example, and find you need to edit the SU model you used in the project, open it from LayOut, make the changes in the SketchUp model and save. Then go back to LayOut. The updates will be done automatically without you manually invoking them.
You can certainly continue manually doing it as you have been. Just don’t tell others that it won’t automatically update the viewport. It can do that.
1 Like
Hi Guys, thanks for the answers. I did notice that sometimes it was automatically updating when opening from LO. Thanks for clarifying what was taking place!
And as far as saving and updating…
Example, in field of my model I do a doodle , it’s Layer 0, I make a layer for it and then it seems I need to go scene by scene to shut off that layer in the layers I don’t want it to show. Once you have 25 or more scenes it’s laborsome. Is the only way to shut something off across all scenes is to manually go one by one? And then Save?
Thanks for the help.
Correy
1 Like
Hi Correy,
Yes. There’s a plugin available in the Extension Warehouse that when activated creates layers/tags that are hidden in all existing scenes.
Make sure you are leaving Layer 0/Untagged active and ALL edges and faces keep Layer 0/Untagged. Only components and groups get layers/tags.
Thanks Dave. You are a wealth of info. ;^)
And in general for saving, when a change is made on a LO page should you automatically Save it before you move to another Page?
THX
Thank you!
Well, it’s like my old Jewish grandmother would say about chicken soup, it couldn’t hurt. 
Fair enough. I stand corrected.
Is there a reason it has two different ways of operating depending on your approach?
I don’t think I’ve ever used send to Layout Simon.
My Layout templates have a pre-inserted viewport that links to a holding SketchUp model (a cube).
When I start a new Layout project I right-click the viewport and relink the model reference (or go to Document Setup>References).
As Dave says, I always open the SketchUp model from Layout if I need to edit it, so that Layout automatically updates.
One of the beauties of this forum is finding out how other people do things. One gets so set in one’s ways, that you tend not to think outside the tramlines you have set yourself. I guess the Send to Layout feature is what seduced me!
My workflow tends to be:
Create drawing in SU;
When ready Send to Layout;
Notice idiocies;
Go back to SU and correct;
Return to LO and update;
Rinse & repeat.
Which means I tend to use the manual updating method.
But if I update a drawing set after having finished and filed it, I do then to go to the LO file first, if only because it makes sure I am updating the right SU file.
I guess the advantage of having a manual refresh is that yo don’t have to wait for LO each time you make a small tweak. But that’s the theory and very unWYSIWYG. In practice, I tend to refresh at each tweak to see the effect. I guess if LO were faster, there would maybe be no point at all in having a twin method. But until that happens, I’m going to try your way.
My models tend to have minimal colours and are frugal on textures which I guess helps towards my speedy Layout experience
And, perhaps more crucially, a Windows environment?
FWIW the ‘Send to LayOut’ option was purely a marketing thing to get more people to work and explore LayOut, IMO.
Now that a lot more people using it, it kind of backdrops and people complaining that it doesn’t work fast.
Might be related to OpenGL whereas other CAD software uses DirectX. You simply don’t want to have a 3D drawing with all the leaves of the vegetation in a construction document, what do you tell the gardener, ‘I want this leave to grow exactly as drawn!’ Who’s checking ?
I also do not use the Send to LayOut, have LayOut open all the time. In fact, I think I am not gonna bother opening SketchUp at all, I just start a new template in LayOut with a ‘dummy’ SketchUp model inside and open it from inside LayOut, then do a ‘Save As’ 
When you open the reference from LayOut it knows you are potentially editing the reference. and is keyed into watching for the changes.
Like Paul, my templates have a pre-inserted SketchUp model with some standard viewports established and I relink to the SU model for the project. I do the same for the spreadsheet that appears in the documents, too. And then there’s a bunch of title block text setup as Auto Text. While I’m in Document set up relinking the .skp and .xlsx files, I edit the Auto Text. I don’t even need to unlock the layer the title block is on.
even better!