This could happen if you did worked on two monitors;
that menu window could be displaying on the second monitor.

Oh, then erase the angular dimension... obviously.

You could try exporting to PDF and printing from Adobe Reader with scaling options.

Instead of always digging into the styles dialog, activate the "Warn of style changes when adding (updating) scenes" option under Preferences > General. It will then pop a small dialog up asking if you want to update your style or save it as a new one (or do nothing).

It can be a (little) annoying but when toggling section planes on/off and updating your scene for instance, it can be very useful, too. Always use fully updated scenes and styles in SU when you want to work with the file in LO.

As it still seems to cause much confusion, maybe some better style control of the inserted SU file in LO would be good...

Thanks for the great tip, Richard; it is much appreciated!

Hopefully, that makes things a bit easier, though a ton of hatching patterns installed with LO would be great, too.

I make a sketchup file layer in layout and lock it. That way the view port cant move.

http://www.youtube.com/watch?v=3YAiDatANQo&feature=related

I have a couple problems.

Camera Jumping—

Often when I go from view edit mode the camera view jumps significantly, so I can no longer see the relevant part of the model if I see any at all.

Scale Selects Improperly—

Often when I set a scale in an orthogonal view the scale does not select the number I click on. It's not possible to set scale if the view is not orthogonal. I don't know if matters if it's in view edit mode or not when this happens, but I remember times when it was not.

Best,

Jim

@jhauswirth said:

@biff said:

But everyone has to tweak their images and orientations in LO for the final presentation.

What settings are you tweaking in LO that you can't in SU?
Note that if you tweak things in LO and you see (Modified) listed in the SU dialog for the Scene name, its not going to render what SU is rendering- that's what (Modified) means, you modified the Scene in some way, so LO takes a snapshot of the Scene because it thinks since you modified the Scene you want your changes to stick. LO will only match what you see in SU if you have a Scene selected in LO and it isn't marked (Modified). Also, if you change the shadow light/dark settings, you need to update the Scene afterwards to capture the new settings and LO will only render those new settings if the Scene isn't
marked (Modified).

Thanks for the reply.
Actually by the mention of tweaking in this instance, read reorientation of maybe a perspective view, to suit the final presentation on an A3 paper. This process is not fast and easy, as often a rerender is needed to see an incremental window crop or positioning.
What you have explained makes perfectly clear sense, and I can see why it has been thought out like that. But in my way of thinking, perhaps the application of this thinking is a little flawed in practice.
I will explain why. It takes a fair while for me to orient, and position a perspective architectural shot in LO. I'm sure many people get pedantic at LO stage too, there is a certain graphic composition that needs to be obtained. No way could I have preplanned that exact position in SU without seeing the final against my presentation sheet and other components. I finally get positioned and realise a test print shows the shadows a bit dark. So, you would naturally assume a quick tweak of shadows in SU and rerender in LO. But actually it means I have to choose that scene again and go through the fairly cumbersome orienting and positioning of the object.

@unknownuser said:

so LO takes a snapshot of the Scene because it thinks since you modified the Scene you want your changes to stick
---my approach to this would be that if you updated a scene for shadows you would want to see that result in LO.
ALso I see in LO there are shadow settings for time and date, could not light and dark be brought across too?
Thanks again for the reply.Layout is getting better and better.

THANKS! (for the disappointing news...)

Is the a place to add my voice for this request somewhere?

EDIT: oh look a Wish list thread - 😕

Mate my system is CRAP and to get a workflow happening in LO with large images imported it helps if you firstly open the image in PS and use the "save for the web function" to reduce image quality, you can re-reference this later to the original if needed!

In some cases I also have to section the image up if it is a very large trace, make a few yariations of your base image, section it to say 6 parts with white space for the rest, import the first image trace that space then re-refernce the image with the next section and so on. The massive white space drops the image size considerably!

Mate as Gaieus suggests it isn't possible.

However there is a simple workaround - LO has a great feature of retaining information set outside the page bounds (which has some very handy reference aspects). So you can simply flick between landscape and portrait under document setup and export your pages individually to suit which are set L or P.

That's it actually. They mean that the inserted 2D view of the SU model is not updated to the latest changes of the model.

If it is a very complex model (and you are in hybrid or vector mode), you can leave them like that as updating may take long. Only update (manually) once in a while.

If it is a simple model however, you can turn auto update on in the Tray > SketchUp model tab and they will instantly update once you make some changes.

b- I did find it. I had the edit resolution on high. I set it at low and it's
made a huge difference. Saving and changing pages on the order of 10x faster!.
The dimensions command doesn't seem to work quite as accurately, but it gets me
close enough. I think there's a slight loss of accuracy in layout anyway. I just
adjust the text, since I know what the dimensions should be. Please thank j, as well. Dave

like cornerbar, er, clubhouse?

b

ps - for newbies, there's a forum called CornerBar, and a model that goes with it.
CornerClubhouse.png

sketchupjockey - send me the file in a PM, or I can try to talk you through trying to recover the file. LayOut files are zipped so unzip the file and look inside the pages/ directory. How many pagexxx.xml files are there? That's how many pages actually got zipped up in the file? Are you saving to a file server or was all work local?

b

Thank you good to know..
c

hi Edson,
did you set the model text in Model Info dialog box?

john

@redinhawaii said:

I decided to redo specifically the framing plan, with a new, less detailed SU model, i.e no plumbing fixtures etc. So I went in to the document setup and clicked "relink",
referenced the new model, and wow, the new framing plan fit in seamlessly. But all hell broke loose when I looked at the elevations, sections,etc....
dang, everything changed...

OK, why bother to do a new SU model for this rather than simply adding a new scene in the original model and setting it up to show less detail?

How about simply deleting the specific view and making a new one and linking in the new model? If it's just the one or two places it won't take more than a couple of minutes.

We've found two instances of extra slow rendering with vector, and I'll point out one and we're working on fixing the other.

If your view in LayOut only has a tiny bit of geometry, but yet there's a large (geographic area of model not shown), you do render all of the model and it can be slow. Dave R helped us find this, and we're looking at how this happens but no workaround other than to have you move items that aren't geolocated closer to each other, or possibly do them in separate models and include all of them in LayOut separately.

An edge issue in vector, which we're testing fixes for, that can cause some models. A user in our Google support forums provided us a test file which we were able to analyze. We'll keep you posted on how this goes and if it helps.

Unlike raster images, the vectors aren't cached and are re-rendered, so even without these issues, you still may get slow rendering. We are currently working on making updates to models be less painful when updated in LayOut.

b