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)
Posts
-
RE: Viewports not lining up from different scenes (same scale)
-
RE: Viewports not lining up from different scenes (same scale)
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? -
RE: Viewports not lining up from different scenes (same scale)
@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 -
RE: Viewports not lining up from different scenes (same scale)
@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
-
RE: Viewports not lining up from different scenes (same scale)
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
-
RE: Viewports not lining up from different scenes (same scale)
@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=jK8lusVdHTQSonder, 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!
-
RE: Viewports not lining up from different scenes (same scale)
@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 -
RE: Viewports not lining up from different scenes (same scale)
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.
-
RE: [Plugin] FredoTools::ReportLabelArea - v3.2a - 05 Feb 20
Hello, guys.
Finally I've a first post.
Fredo, thanks a lot for your tooling! It really helps!
My question is on exReportArea principle, that I'd like to turn to my needs. I used ReportArea (now ReportLabelArea) for the interior design. It works great. And I just checked this new one.
I'm not a Ruby pro, and maybe you should send me to the Ruby forum section. Now I'd like use SU as a mass-modeling tool, and it seems to me there's no simple plugin to do it (if there is one, please, post a link!). Revit or ArchiCAD methods sometimes are a bit clumsy in mass-modeling. And the cost isn't nice for a such simple task.
What I'd like to get a data structure in csv from SU model is as follows:- group
-- name
-- material area (e.g. 3 mats = 3 area values)
-- layer
-- volume
-- etc
The data structure appears to be an hierarchical one, because I'd like to get the parameters of each group/component from my model. Materials and naming are the core of the way of information mgmt I use within SU.
Almost the same for a Component. Actually if I get a long unformatted list of data, I could sort it in Excel.
Now I have no idea which code pattern to use -could you guide here? Any advices, links? I bought last week a brand-new book by Alex Schreyer, but it didn't help me.
Thanks in advance! - group