current status -> modified status -» superimposed status

[Marcogeo]

I ask you a foolish but necessary question.
I read how to do the superimposed, but I miss something and ask you.
I realize the current state for clarity and categories, okay!. the modified state realize it through the duplication of the glosses?
or, what is the most suitable system to do this?

 

[zetadierre]

I ask you a foolish but necessary question.
I read how to do the superimposed, but I miss something and ask you.
I realize the current state for clarity and categories, okay!. the modified state realize it through the duplication of the glosses?
or, what is the most suitable system to do this?

You mean yellow? Can I ask you where you read?

 

[Marcogeo]

yes for yellow/red there are several answers also on this forum. what is not clear to me is whether I have to build current and modified in a single file or even if to make two and then recover only the parts of interest.
In short, it would be interesting to know the procedure that advanced users use.

 

[Marcogeo]

yes for yellow/red there are several answers also on this forum. what is not clear to me is whether I have to build current and modified in a single file or even if to make two and then recover only the parts of interest.
In short, it would be interesting to know the procedure that advanced users use.

 

[lory.b]

Here, for example, in the comparison tables we have a category cfr-demolitions and another cf-constructions in which we move the factual state elements and those of project, which then take the relative colors.
but you may also have a viewport with the factual state and give the yellow color only to the categories that contain the elements to be demolished. and another viewport (overwhelmed or impounded below) where you keep only project elements on. this could be the viewport of another layer or a file reported. ...
Let's say it depends a lot on the complexity of your project and how you organized the files. sometimes there are those who have been in fact and project everything on one, but on different layers. sometimes you create a file for comparisons (as here where I work). I would avoid both solutions above... ;-)
I do.

 

[Marcogeo]

Here, for example, in the comparison tables we have a category cfr-demolitions and another cf-constructions in which we move the factual state elements and those of project, which then take the relative colors.
but you may also have a viewport with the factual state and give the yellow color only to the categories that contain the elements to be demolished. and another viewport (overwhelmed or impounded below) where you keep only project elements on. this could be the viewport of another layer or a file reported. ...
Let's say it depends a lot on the complexity of your project and how you organized the files. sometimes there are those who have been in fact and project everything on one, but on different layers. sometimes you create a file for comparisons (as here where I work). I would avoid both solutions above... ;-)
I do.

but in essence, if you have the plant of a building that you go to fully revolve how you put them in the project? I mean, you have the current file. changes create them directly in that file by creating duplicate layers or doing them on a new file?
For example, in domuscad with small jobs I did everything in a file placing the two blacksmiths in different position. type the current state at altitude 0m and the modified at altitude 20m. then I subpoenaed the individual plans or views.
more often, to not have too heavy files I created two distinct ones. on one of the two I imported the modified parts of the other and after I made the overlap.
not or well understood which is the correct way in vw.
on the fate that would gladly do without any method I agree with you. :biggrin:

 

[zetadierre]

I noticed that you work very well with the intersections of plumbers. It's important to understand only that who's on it commands! if you have 1 layer with the current state and all well-made and sampled polylines and 1 layer with the project state.. see demolitions and reconstructions soon! if you play with duplicates you will subtract and move to new category according to me you arrange quite soon. . .

marcogeo but by curiosity will you be firenze?!? ! ? !

 

[Marcogeo]

I noticed that you work very well with the intersections of plumbers. It's important to understand only that who's on it commands! if you have 1 layer with the current state and all well-made and sampled polylines and 1 layer with the project state.. see demolitions and reconstructions soon! if you play with duplicates you will subtract and move to new category according to me you arrange quite soon. . .

marcogeo but by curiosity will you be firenze?!? ! ? !

area montecatini terme.:finger:

 

[Marcogeo]

I noticed that you work very well with the intersections of plumbers. It's important to understand only that who's on it commands! if you have 1 layer with the current state and all well-made and sampled polylines and 1 layer with the project state.. see demolitions and reconstructions soon! if you play with duplicates you will subtract and move to new category according to me you arrange quite soon. . .

marcogeo but by curiosity will you be firenze?!? ! ? !

the solution you have identified fits for certain operations but we imagine a house made of walls. how do you manage connections through categories? I mean how can I manage a correct view if I remove or add walls? you imagine what happens when two walls are grafted.

 

[zetadierre]

the solution you have identified fits for certain operations but we imagine a house made of walls. how do you manage connections through categories? I mean how can I manage a correct view if I remove or add walls? you imagine what happens when two walls are grafted.

If you have to handle this in 2d I don't see it so impossible. . .

If you have the status and the design status on different layers (non-category layers) and walls on different categories (e.g. status and project) you create a layer that you call yellow (do not remember. is demolitions true?) and on that throws us both the polylines of project and those of the state of fact. where there is only the factual state without the project will be a part to be removed, then carry over (set dx with selected element>port above) all the project selects all>cut surface. at this point you only have the parts that you demolished and those will be your yellow!

If you have to do reconstructions do the reverse process! on a layer reconstructions where the project advances you put on the state of fact cuts everything and the parts that remain the red dots...

Am I right?

 

[Marcogeo]

If you have to handle this in 2d I don't see it so impossible. . .

If you have the status and the design status on different layers (non-category layers) and walls on different categories (e.g. status and project) you create a layer that you call yellow (do not remember. is demolitions true?) and on that throws us both the polylines of project and those of the state of fact. where there is only the factual state without the project will be a part to be removed, then carry over (set dx with selected element>port above) all the project selects all>cut surface. at this point you only have the parts that you demolished and those will be your yellow!

If you have to do reconstructions do the reverse process! on a layer reconstructions where the project advances you put on the state of fact cuts everything and the parts that remain the red dots...

Am I right?

Okay. so, basically, I suggest to create a new layer on which I will bring back my plant that I will go to change. then in the viewports I will make the overlap.
this is a methodology I had imagined but does not run the risk of thickening the file? I clearly pose the problem because working in vw I would always do 3d.

 

[zetadierre]

Okay. so, basically, I suggest to create a new layer on which I will bring back my plant that I will go to change. then in the viewports I will make the overlap.
this is a methodology I had imagined but does not run the risk of thickening the file? I clearly pose the problem because working in vw I would always do 3d.

I can't answer that. I tried to start making a project in 3d but I didn't leave

As soon as I'm clearer with 3d casemai

 

[Marcogeo]

Can someone send me a simple file to make me understand how to set it up?
I don't understand if I'm the one who's explaining bad or I don't understand what's wrong with me. Maybe a file can help me understand.

Thank you.

 

[lory.b]

we architecture make them only in two-dimensional; I don't know if an example of ours can serve you, since I think I understand that you set the job in 3d.
I do.

 

[Marcogeo]

we architecture make them only in two-dimensional; I don't know if an example of ours can serve you, since I think I understand that you set the job in 3d.
I do.

This answer will spy on me completely! I thought, buying vw, jumping forward and instead I see myself working with powercaad!
How can I handle 2d and 3d separately?

Are you telling me that the method you use is to make the 2d architectonic and the 3d you only use it to make presentations? Yes, yes, they are also capitulated etc but is not a double job? Shouldn't the method of work be streamlined rather than sum up?

I have to make some reflections and better understand what the right method of work is or may be for me! :frown:

 

[Marcogeo]

by chance alternating layers with 2d to that with 3d? that is stacked, for example, the plant 2d and the upper layer the same but 3d? then you play everything between lighters?

 

[lory.b]

we say so: the old habits are hard to die.
when I came to work here, things were a little different from today. the concept of bim perhaps still to come. and when a working method is consolidated in 40 people it is very difficult to make changes.
Architectural are exclusively two-dimensional.
personally, having some familiarity with the software and following developments, I am not happy with it. I would prefer that it worked directly in 3d while instead I have to develop them separately from drawings 2d, in later stages.

But that has nothing to do with what you do.
You're using it properly, like bim.
to set comparisons, there is no specific method. You have to decide how you do best. from us follow on specific files.
so we have the factual state tables, design and comparisons where the elements take the yellow and red colors. you can simply refer it to the factual and project status files as viewport inside a new file. edit viewports by assigning the colors yellow and red to the categories.
I do.

 

[Marcogeo]

we say so: the old habits are hard to die.
when I came to work here, things were a little different from today. the concept of bim perhaps still to come. and when a working method is consolidated in 40 people it is very difficult to make changes.
Architectural are exclusively two-dimensional.
personally, having some familiarity with the software and following developments, I am not happy with it. I would prefer that it worked directly in 3d while instead I have to develop them separately from drawings 2d, in later stages.

But that has nothing to do with what you do.
You're using it properly, like bim.
to set comparisons, there is no specific method. You have to decide how you do best. from us follow on specific files.
so we have the factual state tables, design and comparisons where the elements take the yellow and red colors. you can simply refer it to the factual and project status files as viewport inside a new file. edit viewports by assigning the colors yellow and red to the categories.
I do.

Okay. I have no idea what you wrote to me but I can imagine something, here I will have to deepen the chapters "references".
then confirm that you make a file for each state.

 

[lory.b]

then confirm that you make a file for each state.

That's what we do here. but it is not mandatory.
instead you could create on a single file - maybe set with prefixed categories "sdf-" (actual status) and "pgt-" (project) - a new level of layout and create viewports set for comparisons.
for that I advised you to do tests, so that I can understand what the most congenial method is to you.
There is no method, there are several.
for how we name the files (we follow regulations as certificates) we must by force divide the processed.
for you will certainly be different. proof with references, try with viewports.. .
You have a new tool for your hands, you owe it in a way "trap". therefore it will never be time lost what you will dedicate to some extra evidence.
I do.

 

[Marcogeo]

for you will certainly be different. proof with references, try with viewports.. .
You have a new tool for your hands, you owe it in a way "trap". therefore it will never be time lost what you will dedicate to some extra evidence.
I do.

and I thought I would present three projects (and related notules) by the end of the month:biggrin: