Model Edit via Adjacent Component Plan
-
Working on a rather complex Sk_up model and would like to edit/revise/refine a Floor Plan & or Section via an extracted (Plan/Section) component immediately adjacent -- in order to simplify the edit process. Able to extract the Plan/Section - but having trouble making changes on the extracted component that simultaneously reflects these changes on the Plan/Section buried inside the model... How about a blow-by-blow run-down by a pro that's accomplished this task. Very much appreciated...
CF-arc -
If you've made a copy of the component, changes that you make inside (editing) that component will be reflected in the other component. That's all. I am not sure what you mean by "Plan/Section" component though. You might try it first on a simple test component.
-
you could try cutting the component and pasting it (in place) in another, 'clean' sketchup file. make your changes, then cut and paste back into the original sketchup file.
what trouble making changes on the extracted component are you having exactly?
-
I'm not quite sure what the trouble is but as Peter says, if you make a copy of the component in the same SKP file any edits you make to the copy will be reflected in the original. If you made a group instead of a component this will not happen, though.
I do this regularly when adding details to a model. When I've completed the editing I discard the copy of the component. I don't bother copying the component to a separate SketchUp file because then I have to go through the gymnastics of replacing the original with the edited copy.
-
@dave r said:
I don't bother copying the component to a separate SketchUp file because then I have to go through the gymnastics of replacing the original with the edited copy.
if you cut and paste (in place), rather than copy and paste, it's actually very easy & fast.
-
Yes. That's true but still more than I need to do. I find it easy enough to simply copy the component out a little bit away from the model to edit it. I can still use the rest of the model for reference. And in cases where I'm working on something small and might generate gaps due to very small faces, I can scale up the copy, edit it and know that the original is getting the same treatment. When finished, I close the scaled up instance and delete it.
The cool thing is you can do it your way and I can do it mine and we end up at the same place.
-
@dave r said:
And in cases where I'm working on something small and might generate gaps due to very small faces, I can scale up the copy, edit it and know that the original is getting the same treatment. When finished, I close the scaled up instance and delete it.
ahh! great tip, never thought of that.
I find that the cutting and pasting into a new file is handy if you have a large file and the clipping thing is a problem.
-
I don't cut and paste, I Save as and reload. I find it is handy for building in a site. I can work on the building in a smaller file if I want.
-
@porch_unplugged said:
you could try cutting the component and pasting it (in place) in another, 'clean' sketchup file. make your changes, then cut and paste back into the original sketchup file.
what trouble making changes on the extracted component are you having exactly?
The goal here is to attempt a set of Constr Docs from the 3-d model. As such, am trying to stack the Plan 'slices' on top of the 'Working model' along with a series of Section 'slices' off to each side. If this works out - the 'extracted' Plans & Sections will be much easier to edit (vs going deep into the model) and each will eventually become a 'Scene/Page' in L/O... Thus far, seem to be having trouble getting the working model to reflect the edits/changes made to the extracted Plan/Section 'slices'...
CF-arc
-
If you are using the section tool to create a group from slice, what I do is:
- Edit the group and make the entire slice a component. I then copy the component vertically forced on the blue axis above the model. This way you can edit the component outside of the model.
- Save the view looking vertically down on the slice - since it is stacked exactly above the slice located in the model, you only see one plan.
What is nice about keeping one of the slices in the model area, is that you can see if there any deviations from changes very easily.
-
[I don't cut and paste, I Save as and reload. I find it is handy for building in a site. I can work on the building in a smaller file if I want.[/quote]
-- thanks for the reply and understood. Would now like to take this idea to the next level in terms of producing a set of Construction Documents from 1 'parent' Sketch Up model while creating several copies or 'children' models in order to accomplish the necessary drawings, details & interiors -- thus limiting the file size of each. As such, here's the problem: -- given the frequent design revisions that are part of every design 'process' -- how does one manage these changes in multiple Sk_up 'children' models which are copies of the one/original 'parent' model without having to go back and update every 'child' model on an individual basis every time there's a change...? -- understand that LO allows for update(s) as necessary using the 'update or relink' command -- but want to make sure all Sk_up models are 'on the same page' in terms of edits/revisions -- before exporting to LO... -- any suggestions/ideas are appreciated as probably not the only one attempting this task.Thanks,
CF-arc
-
@cf-arc said:
-- thanks for the reply and understood. Would now like to take this idea to the next level in terms of producing a set of Construction Documents from 1 'parent' Sketch Up model while creating several copies or 'children' models in order to accomplish the necessary drawings, details & interiors -- thus limiting the file size of each. As such, here's the problem:
Have you looked at the LayOut forum. there's a good discussion on creating construction documents there. You should also take a look at Nick Sonder's videos on his work flow and methods.
@cf-arc said:
-- given the frequent design revisions that are part of every design 'process' -- how does one manage these changes in multiple Sk_up 'children' models which are copies of the one/original 'parent' model without having to go back and update every 'child' model on an individual basis every time there's a change...?
You can't. That's the downside of making "child" files. You have to manually manage them. It would be nice if you could dynamically link multiple SKP files so changes in one would get carried through to the others but at this point anyway, that's not possible.
@cf-arc said:
-- understand that LO allows for update(s) as necessary using the 'update or relink' command -- but want to make sure all Sk_up models are 'on the same page' in terms of edits/revisions -- before exporting to LO...
What you get in LO is only as good as your SU models so you have to take the time to go through all of the SU files and make sure revisions are reflected accurately.
Although I'm not using SketchUp and LayOut for architectural drawings as a rule, my models and construction documents can get to be quite complex and highly detailed. Still, I try to avoid using more than one SketchUp file as much as possible. If I have to create additional SketchUp files I try to make those 'child' files ones that won't be affected by revisions to the main file.
-
Dave is right, but I still find the idea useful. I wouldn't have many child files. So far I have used one per project. The full site. Not that complicated. To me it feels easier sometimes to be able to work on the building, the real focus of my modeling, in its own file. Usually the rest of the model, even the terrain, is for design and visualization for me, not working drawings (we'd resolve final site design with the civil and landscape architect).
I can imagine other ways to use reloaded components, but they don't add up to many child files. LO itself is a "child file", and you get prompts, but you still have to update it.
In fact if I had been doing this on my present project, I might not have "lost" the building--something Dave helped me fix.
-
@dave r said:
@cf-arc said:
-- thanks for the reply and understood. Would now like to take this idea to the next level in terms of producing a set of Construction Documents from 1 'parent' Sketch Up model while creating several copies or 'children' models in order to accomplish the necessary drawings, details & interiors -- thus limiting the file size of each. As such, here's the problem:
Have you looked at the LayOut forum. there's a good discussion on creating construction documents there. You should also take a look at Nick Sonder's videos on his work flow and methods.
@cf-arc said:
-- given the frequent design revisions that are part of every design 'process' -- how does one manage these changes in multiple Sk_up 'children' models which are copies of the one/original 'parent' model [b]without having to go back and update every 'child' model on an individual basis every time there's a change...?[/b]
You can't. That's the downside of making "child" files. You have to manually manage them. It would be nice if you could dynamically link multiple SKP files so changes in one would get carried through to the others but at this point anyway, that's not possible.
@cf-arc said:
-- understand that LO allows for update(s) as necessary using the 'update or relink' command -- but want to make sure all Sk_up models are 'on the same page' in terms of edits/revisions -- before exporting to LO...
What you get in LO is only as good as your SU models so you have to take the time to go through all of the SU files and make sure revisions are reflected accurately.
[size=50]Although I'm not using SketchUp and LayOut for architectural drawings as a rule, my models and construction documents can get to be quite complex and highly detailed. Still, I try to avoid using more than one SketchUp file as much as possible. If I have to create additional SketchUp files I try to make those 'child' files ones that won't be affected by revisions to the main file.
[/size]-- Dave, thanks for the detailed response - believe you've answered my question in that it appears it isn't possible to keep 'child' models constantly updated per revisions to the 'parent' model. (however, plan to continue to think about some sort of 'work-around')... thinking this will lead to 1 very large model (in terms of file size & management) given the number of scenes req'd to produce even a small arc project. haven't yet explored the LO forum on the topic of CD's - but will begin. thanks again,
cf-arc -
Any little image for resume the problem ?
Advertisement