Hi all
We are migrating from V82004+Triforma to V8I+architecture.
To be short, i have already post some question there is two month and i'was ( and i'm) waiting for bentley's answer. In 2D we don't have many pb. We actually work with V8I in 2D but not yet in 3D because of 2 pb. First, it's printing dynamic view, second it's converting a sheet with DV in a 2d dwg to send to our customers.
i know the workflow in 3D with Architecture. i have read many many articles but nothing on printing. i can make my sheet with DV, annotations.... i see my sheet on my screen but how printing with pen table and exporting.
I wanted to know how people using BA are working, printing, converting. If they synchronise or not DV, or the DV are in "calculate hidden line"??
Thanks for any answer.
PS : In the past i send a message concerning exportation with the "merge visible edge in 3d" option. I have some hidden that dosn't appear when i make a circle hole in a wall (ok in the DV but not in the export). Bentley say that it's a mirostation's bug that has been fix. certainly in the future update...
Hi guys and happy new year
a new year with some solutions?? we will see.
i haven't news from bentley for the moment. If we havent issues, maybe we will be oblige to re-draw our cells libraries to use DEM (because most of them aren't calculate) and say good bye to DV or more simple stay in 2D...i don't hope.lol.
I'm agree with you about (dont strech, simple element...) but the pb i have is with simple element. Like say damon, a simple circle hole in a wall and i have pb when i am in "visble edge" mode like the .jpg i post before. The pb is the addition of parts/family activate, unification activate, hole (circle) in a form, and hidden line activate. If one of those thing is not activate, it's ok. but i need all of them like evreybody i think.
So nothing new for the moment. Maybe last month when i'll have finish my actual project on... V8 2004 + Triforma...
Regards
PJ
Sounds like smartsolids are a bit more complex... and need more processing.
Maybe its a Parasolid problem as Bentley can't really modify their code directly to optimise DV/DEM?
Size: This is worrying.
I think the one problem comes from the fact that BA doesn't like normal 3D smart solids created with normal microstation tools. In the days of when Triforma first arrived I can understand this. But 10 years on I woulda thought a lot more integration would have happened. Especially now that DV's are part of base microstation.
I find that a single 'smart solid' can slow down DEM by 10%. And DV's seem to have similar issues.
The key to drawing in 3d in BA is to use forms for everything. Do not merge forms 2gether to make smart solids.
The more complex the 3d elements are then your DV is going to slow dramatically. Luckily BA has a cool function that will merge elements that are the same part and will delete the join lne which dramatically overcomes this. But every new user I see always does the same mistakes in making smart solids rather than placing 2 elements next to each other to make one building feature.
eg. A precast panel that has 200mm thicknes from groud to a first floor and gets reduced to 150mm thk at the 1st floor for the floor seating. Some users will a hole to create the 150 thk part, or draw 2 solids and merge them 2gether. But you should just draw 2 separate forms and the DEM/BV processing will delete the join line betweeen them. Ity will process much quicker even than if you create a "feature" in the form.
Now that DV's are part of microstation you'd think this should have been oversome? [in AECOsimBD] Somehow I doubt this to be the case. It seems Buildings in 3d are just too big for Microstation to handle effectively. My current 18 story Hotel model is now 87Mb. BV's (and DEM) just don't like processing that much data. My elevations just don't come out sometimes, and if I make the accuracy low the output is just terrible.
Sounds like a glitch development should clean up..... Too much intelligence stored with individual tool code and not somewhere more central and discoverable...?
Apparently, UI and processing code should not be mixed. Maybe, the vertical's specialised code (rewritten as object enablers or element handlers?) that are linked with the stuff that is exposed to other tools need to separated out as well?
In the mean time, shouldn't whoever is in charge of the Wall tool check that all the other platform tools like the Stretch tool are compatible before they release them ... or vice versa? I guess the platform guys release first... which is problematic for the verticals which have to follow on?
Unknown said: .....The issues you see can be bad cells, bad parts, etc. sometimes very hard to trace down We spent a year with great dv's and elevations not plotting to find out that all our windows had to be recreated as a single element was made by cutting something in a negative direction. When cut in a positive direction they plotted ok. .....
.....The issues you see can be bad cells, bad parts, etc. sometimes very hard to trace down
We spent a year with great dv's and elevations not plotting to find out that all our windows had to be recreated as a single element was made by cutting something in a negative direction. When cut in a positive direction they plotted ok.
.....
This may be the case time and again. I have found that sometimes doing a simple hole on a wall form can have errors in it that will cause disruption to DEMs and DV's. Mostly it comes from someone using the 'stretch' command to extend the wall after the hole has been formed. This quite often will make the form behave badly afterwards. Must be something to do with creating a negative value somewhere in its geometry.
No matter how many times I say "Do not use stretch on 3d forms" to the people but here they will always do it. You must always use the "Extend form" tool.
Stretching just does not work on forms especially when they have "features" in it. In fact if you try to stretch say a couple of rooms to make a room bigger/smaller, if you have a door within the fence area I find Microstation will crash every time.
Its very hard to break draughtspeople from doing it in 3d, when in 2d (probably for the last 10-15 years) it is probably the most used tool in thier arsenal.
regards
Damon