Helm
-
Posts
834 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Helm
-
-
3 minutes ago, _c_ said:
No. Given that we don't know Unit Plan yet, presently the only really efficient way is using Design Layer Viewports.
Both Symbols and Design Layer Viewports fail on variable wall height, obviously, but Symbols fail more, since their definition doesn't reside on design layer and walls are entities whose parent is required to be design layer.
Edit: if you don't use walls, symbols are better.
If you want to use the viewports in another file or project what do you do. Also I still find the whole wall height business confusing and cumbersome. Why can't we just put a wall on a layer give it a height without any other settings. Variable wall heights in symbols - I am not sure can't a symbol have walls of differing heights.
-
On 4/30/2020 at 10:58 PM, Boh said:
Not to mention walls within symbols sometimes getting confused with elevation level. 😉
That seems to be the reason some don't want to use symbols for units.
-
I keep thinking about this bit about unit plans. At present the only really efficient way is to develop symbols of the units. They can be used in various projects and if updated every instance of the symbol changes. Or one can also update a copy of a symbol and replace it in the overall floor plan easily.
-
55 minutes ago, _c_ said:
We use design layer viewports. It is pretty complex if you need to display them on multiple files but it works perfect, including IFC export.
This gets rather tricky if you need various wall heights. If Unit Plan resolves this, well done.
So you make a unit/apartment plan with only interior walls? And make it a view port. In our case we are making factory built modules that have double common walls, that is a factory built common wall on each side of the unit. We would sit that VP/module on top of the slab and then draw the exterior building walls and then interior hallway walls for example. Actually we would probably fit all the modules around the overall floor plan then draw exterior walls then fit the slab to the overall floor plan. Just trying to get the system straight in my head. Right now I am getting basic layouts done by others and we have to do the exterior look and finalize the model and no one seems to do the basic layout the same way. Having written all this I am wondering if this is going to be problematic since VPs can't be copied to other files.
Interestingly the architect we started working with does all his work with others online, no one is in his office and because of my long experience I seem to be getting the bigger projects, works out perfectly during this lockdown.
Yes some sort of unit plan approach would be a great help. In the housing market factory built modules are going to be the future. Our architect has all the work he can handle and we are happy to be sitting at home in Italy working on his projects. Keeping up with VW and years of experience has made me at retirement age an even more valuable asset in the work force.
-
On 4/30/2020 at 4:54 PM, lorenza said:
Ok, UNIT PLAN is extremely important for our workflow!
Here too, we still have not found the best way. You can make a symbol of an apartment plan but what does it include. I am not talking about much more that walls, fixtures, and furniture. But how does the symbol connect to the building structure, the exterior and interior common walls. And what about layers, they cannot be included in a symbol everything is on one layer, but we can use classes for electrical etc.
-
1
-
-
Dumb question, what do you mean by voids?
-
What I am reading is that the normal run of the mill flu kills about 0.1% of those affected and the Corona 1% more or maybe a bit less depending on the age and overall health of the population. Up to 45 million people get the flu every year in the US and there is a vaccine for it. None for Corona and it is 3 times more contagious.
-
I challenge all the disbelievers to do some arithmetic if drastic measures are not taken 40 to 70% of the US population might get the corona virus and 1% of those will likely die.
-
1
-
-
Even if this virus were nothing worse than the flu the fact that it is at least 3 times more contagious than any flu we have seen means that if not taken seriously many many more people will die from it. We make jokes in Italy about what it is like having to stay home, but the virus is no joke a bomb is about to go off in the US and this attitude that it is nothing more than the common flu will only make things many times worse.
-
1 minute ago, zoomer said:
The Wall Tool isn't capable of doing slanted Walls or Walls with varying Thickness.
So you would model these by standard 3D Modeling Tools like Extrudes.
You can create Auto Hybrids from standard Geometries later to get a similar
2D Plan representation like PlugIn Objects have.
Yes that is the only way I imagine to do them, but what about doors and windows. I suppose you make a polygon for the wall then extrude it, then make cut outs for doors and then put in a door symbol. The same for windows. Really a lot of work.
-
How do you deal with odd shaped walls such as one finds in old buildings in Italy and other countries. How do you make a model of a building with walls that are not parallel.
-
Having more than one detail in a viewport goes back to the comment that you can´t use auto callout referencing. I don´t know how important that is since it is only useful when looking at the plans and details in VW it has no use for hard copies on the job site.
On my current project I made empty viewports with the settings of scale, etc I wanted for each. Then pasted the details in as annotations. That works pretty well, and the modifications done to the details as annotations can then be copied and pasted into a design layer for future use. If you make annotations in the normal way to a viewport you can´t save the whole thing for use in another file. Of course this only works if the detail consists of only one layer.
There is a management issue that is persistent in VW; you can´t easily copy viewports to another file. So you have to be careful how you approach using annotations.
-
This would be a handy and time saving option, but there is still the ago old question of when is it better to use annotations or put notes, dimensions, etc on the original design layer. If we are talking about 2D details and plans it might be easier and better to do them on the design layer or layers, there you don´t need to open anything and the viewports just need to be updated. Also as we know viewports cannot be copied to other files. But in the case of elevations derived from a model each elevation would generally be in its own viewport and notes, dimensions, etc need to be done as annotations.
-
4 hours ago, Jonathan Pickup said:
If you create detail viewports that way, you can’t link the detail callouts and references to the individual details.
Good point, but then we don´t do links, probably we should.
-
How do you do them, do you make a viewport for every detail. So I have lots of details connections, windows, doors, etc. done in past versions of VW. So I copied them onto a design layer. Then thought it a pain to make vp for each of them so I made large viewports for each scale on a sheet layer then copied and pasted the details in as annotations. Then the original details are left alone and the ones in the viewport can be revised in annotations and grouped and moved into place in the sheet. Am I making a mistake here, is there and easier way.
-
On 10/14/2019 at 11:07 AM, drelARCH said:
Hi,
I have small tiny residential house project migrated form VW2019 that cause me memory issues.
Every time I update any of HL viewports in file new amount of memory is added to demand (looking at activity monitor app).
While OpenGL is really fast and cause no memory issues, HL render for me is quite slow (looking at size of project model) and very much memory demanding.
When I open this file memory is from hundreds of MB up to few GB. But when I rerender HL viewports it is going up quickly to 50GB and still up even 100GB!!!
File size was around 360MB(was 430 in VW 2019), but after I rerendered all my viewports (OpenGL + HL viewports) it jumped to almost 1GB.
I have set up 7 sheet layers with A3 size pages with 80 viewports (26 in Hidden Line rest OpenGL )
Is there a way to release ever growing memory demand? Is there a way to stay in 'safe zone' with memory without restating file?
When I restart the file everything is ok until i start to render again...memory demand builds up.
In fact I am missing button to globally (after high quality rendering is performed and drawings are published) decrease viewports quality...Changing dpi back to 72 on sheet layers will not take effect...
Thanks for help.
I am not sure which memory you are referring to. VW will increase its use of RAM as you update complex viewports and not release all of it until you restart the program. Sometimes saving the file and then reverting to save will reset the RAM but I noticed that it does not in 2020.
-
1
-
-
Yes a good idea, it is a pain to go back and forth when especially when you need to put the same annotations in several viewports.
-
Just a complement on your work. It is impressive. From a practical standpoint if this is for a client even the worst of the ones you have done is enough to give them a really good idea of how your design will look, so I would suggest you not lose too much time/money trying to make the renderings perfect.
By the way is that all of the kitchen? I see you have an American size refrigerator and just one small sink. Is there more kitchen to the right side? I love the overall look.
-
If I make a section viewport then render it with OpenGL the background is black. Also there is no crop to edit. Is this normal or am I missing something.
2020 Design Summit Thoughts
in General Discussion
Posted
OK so continuing on the subject of unit plans, I am starting to agree about design layer viewports. I have not been a big fan of using referenced files. But on my current project we do have one big one and that is referencing the apartment building to the office building on the same site in order to accomplish the overall site plan and project model. The beauty of it is that the referenced viewport can have all the advantages of a normal viewport. So:
Let me summarize how I think it works, we make a file for the units, then we create the main project file. On that file we make design layer viewports for each unit type referencing the unit file, then those viewports are copied and pasted as needed to create the overall floor plan. Any changes we make to the units would be done in the original unit plan file and updated in the project file. Do I have it right so far. What will be the issues regarding floor elevations and wall heights.