Viewports not lining up from different scenes (same scale)

NIck735

Dave- No I am using sketchup 2015. I have been a long time lurker, but this is my first time posting. When I created my screen name I was using sketchup 8... I think I figured it out. I changed the view from top to top(relative) and this did the trick. Im not really sure what the difference between the two is though.

Dave R

You shouldn't need to do that.

You should be able to create your first top view scene and make a second one from the exact same camera position. They should overlap perfectly in LayOut. Use layers in SU to make invisible those things you don't want see in the scene. You should be able to make as many scenes as you need from the same camera position and stack their viewports with perfect alignment in LayOut. This is a common procedure for me. I'm never setting the standard views in LO. There's no need for that when the views are created in SketchUp.

Another thing to make sure of is that you aren't changing the camera by editing the viewport in LayOut. If the Scene is shown as modified in the SketchUp Model inspector window, you will have problems.

vapross

Hello everyone!
I have the same issue as described above.
I use SketchUp Pro 2015 and here what happens.

I produce a set of photomatches of mass-model in urban context. Now I started to use composing method for crisp linework in LayOut (instead of Illustrator).
So I prepared the context model with different photomatches. Each resulting photomatch consists of two SU scenes - photo only and new building only with corresponding styles and layer visibilty.

In LO I place a viewport with photo only, ctrl + c, paste and change the copy to the scene with building only and vector mode.
Suddenly something went wrong. I added a few photomatches to the model, and in LO when I set a viewport with linework scene to vector mode, it gets a bit bigger. If I set it to raster mode, everything is ok (however the background can't be done transparent due to a style)

I tried almost everything, but it didn't work. And I tried other generic perspectives to turn into vector linework - the same stuff happens. A vector viewport gets a bit bigger than raster one.

sonder

The key is saving your scenes in Sketchup so they are identical in orientation, otherwise they will not align in LO.

vapross

@unknownuser said:

The key is saving your scenes in Sketchup so they are identical in orientation, otherwise they will not align in LO.

Sonder, that's is the main question - why the vector viewport is jumping when everything is saved (scenes with all checkboxes, file, model reference updated etc)
I think the best illustration will be a short video

sonder

@vapross said:

@unknownuser said:

The key is saving your scenes in Sketchup so they are identical in orientation, otherwise they will not align in LO.

Sonder, that's is the main question - why the vector viewport is jumping when everything is saved (scenes with all checkboxes, file, model reference updated etc)
I think the best illustration will be a short video

So your issue is alignment in Sketchup scenes. You need to make sure the scenes are "stacked" exactly in order for them to work in LO without having to manually move things around in LO.

I use templates now where the scenes are already created making the setup really easy on every project. If I were starting from scratch, using a floor plan as an example, I would first create the base scene that I want to raster image which is most of the floor plan layers on, except the line work. Once you have everything visible you want to see, update the scene. To create the next scene that is going to show linework only, start with the floor plan scene, toggle off all your layers except those you want to vector render. Then create a new scene. Doing this process ensures the two scenes have the exact same alignment.

You can test the alignment issue by simply clicking through the scenes in SU. If the model jumps around, it will do the same thing in LO.

I talk about it here at the 4:00 mark:
https://www.youtube.com/watch?v=jK8lusVdHTQ

vapross

@unknownuser said:

You can test the alignment issue by simply clicking through the scenes in SU. If the model jumps around, it will do the same thing in LO.

I talk about it here at the 4:00 mark:
https://www.youtube.com/watch?v=jK8lusVdHTQ

Sonder, thank you for the answer

Here is the video where I perform the entire process - https://www.dropbox.com/s/h05n6f0bzv53dlb/SU-LO%20jumping%20issue%202015-07-14%2008-04-09-240.avi?dl=0

I do think this is the bug, maybe caused by photomatched scenes. Although I tried a stacking (actually it was yours) method for the first time - before it I have being considering it as mauvais ton.

By the way, thank you for your techniques, they are inspiring!

vapross

I tested other models without photomatch scenes - the same issue. Switching from raster to vector leads to kinda "zoomed" view. So "jumping" is not a correct word - it's certainly "zoomed"

It's like something went "broken" - never noticed this bug

pbacot

I know in SU the photomatch scene is special and you can't really replicate it. The perspective you set up has it's own special camera settings. No clue why vector views in LO would be the cause of this. I bet this is a rare operation. The testers probably never even tried this use of Photomatch.

That said, this discussion started with problems using scaled scenes in LO with parallel projection, which is not a setting photomatch uses.

JQL

Use thomthom camera tools to update cameras. Match photo introduces a frame ratio that reads differently in some scenarios.

Yu can replicate a camera from a photomatch scene in another scene by using advanced scene settings in window>scenes:

1-untick "camera position" in the incorrect scene;
2-double click the ,atch photo scene;
3-click once in the incorrect scene name;
4-tick "camera position" back on and te incorrect scene inherits the match photo "scene position"

hope this helps

vapross

@pbacot said:

The testers probably never even tried this use of Photomatch.

This kind of wireframe mass-models is typical for visual analysis - I use SU for this purpose

vapross

@jql said:

Use thomthom camera tools to update cameras. Match photo introduces a frame ratio that reads differently in some scenarios.

Thank you for this tip. However there are no issues with raster view with Photomatch scenes and only vector one becomes zoomed.
Actually, I tested other models without Photomatch scenes at all - the same issue, vector becomes zoomed
Maybe I should report a bug

vapross

When I switch to ortho scenes, vector viewports perform normally, and here we have the composing approach.
Guys, can you try the same operation with generic perspective scenes?

pbacot

I just mean the photomatch and LO overlay use. I think the usual use is to create a model from the photo. What it has to do with wireframe and needing to overlay scenes IDK, but I still think this would be a scenario they didn't think of testing, all the way into the overlay in LO. So they wouldn't find this deficiency (can't say if it's a bug-- probably just something the program doesn't do).

I wanted to try it out, but I can't follow what the steps you use are.

JQL

I get no zoom factor when changing a perspective viewport from Raster to Vector or Hybrid.

Why don't you share a model here?

vapross

Oops, missed your answers here.
I tested once again with generic perspectives and vector view, and now it's ok. However, the photomatch scenes keep on zooming with vectorview in LO - i think it depends on the distortion of axis when photomatching (some scenes have wide FOV). Well, got to test it further, because it would be a really time saving method (even now).
Here is the model (SU - https://www.dropbox.com/s/joxh1d9y97qqb92/3047-site_2015-07-11-v3.skp?dl=0 (soon will be removed)