Normal 0 21 false false false SV X-NONE X-NONE
First datapoint glued to base plane
In B Architecture you can set the config var ATENV_3DSETUP = 0 if you do not want the 3D “help” around (sticky Z, ACS plane lock, ACS snap lock…etc). However, there seems to be an unpredictable behavior of these settings although the corresponding locks look OK (unchecked).
Somtimes it works, mostly not. The solution has been to draw a first line from this forced on datapoint, set an end point where wanted and from there on snap. Primitve work flow; one would to know what is happening.
Other suspects investigated: Active Floor None, Icon locks off, off, off (these do not seem to change anything when toggled anyway…)
There must be some very basic setting somewhere that I have missed. Any idea?
Ingemar Saevfors
Win 7, Mstn 08.11.07.443, BA 08.11.07.69
Ingemar
you are not alone in this having problem with getting Accudraw's drawing plane as you want. In Z, and in front when working in front views.
I have difficulties understanding excatly what is happening and why.
Part of the problem seems to be platform people don't bother to understand what is happening in BA.
Another thing is there is an admitted bug in snapping in front views with acs-snaps on. Been there since J-version I think.
ATENV_3DSETUP = 0 -- is it working in v8?
Sometimes I think I get "2d-datapoints" by accident and have problems releasing it.
regards / Thomas Voghera
we have the same problem and it is extremely unproductive!
The problem is that there is always an acs at play. So if you just click a data point in elevation MS/BA puts it at the z value of the active acs (even if all your locks are off!!) So while the user might expect the datapoint to start a line where they can see it on the screen (which is after all where they wanted it!!) it actually starts placing off screen at the acs z value. Rubbish behaviour!!!!
Helo
I couldn't agree more ...... this 'new feature' is extremely annoying/unproductive ...
It appeared either with the initial V8i or SS1 (can't remember which)
I logged a report with Tech Support and after several exchanges it was concluded that this is a WAD feature.
Apparently, in BA, there is always an Active ACS which you are 'stuck' to. Even when ACS Lock and ACS Snap Lock are very clearly OFF. Pointed out how this was obviously misleading. Also, even a 'tentative point' won't work (you can't move Accudraw's Origin to the tentative point) unless you rotate the ACS to be parralel to the direction you want to 'move' in. So you have to rotate Accudraw to Side/Front, then you can tentative point to a point higher than the fixed ACS, then you rotate again to Top so that you can snap to a point away from the 'fixed' ACS.
The tech support guy at the time agreed this wasn't productive/logical ....... but apparently this had been introduced to ....... 'make things easier for new users' !!!!!!!!!!!!!! I kid you not!!!!!!
This was certainly there before SS2
How did they conclude that this is an 'improvement'? It has messed up what was one of the main advantages of 3D in Microstation: fluidity of moving around the 'working environment'/model. You could just snap/tentative point to things and the ACS/Accudraw would move around with you.
Bentley Systems ..... please sort this out ..... and NO .... I will not be putting in a change request ....
Things like this underline a really quite shocking lack of 'testing and checking for suitability for intended purposes'.
Are they really saying .......'this or that feature/tool won't be fixed or amended unless some large enterprise style engineering group says ...... we want this fixing/amending'
Could Bentley please exercise a bit more 'pre-emptive' checking and testing ....... some of the things that have slipped through are things that if somebody had sat down and played around with it for only a couple of minutes .... they should have really concluded that 'this isn't right'
CAD aside .... one would have thought it pretty obvious that if you turn a feature OFF (the icon clearly says OFF) ... then indeed, it is OFF. When you want it back on again, you turn it on
C'mon folks, we need these sorts of things dealing with BEFORE we move on to interactively linking building geometry with specs, quantities, schedules, fire ratings, insulation values, daylighting, construction sequencing, clash detection, ..... + whatever else sounds good in the publicity blurb ..... across several continents all in glorious 64 bit real time colour.
This should have been dealt with .... it has already been formally raised with Bentley Systems and wasn't fixed when SS2 was released .... now we have to wait another 6 months or for SS3
(Footnote to this .... I'm not renewing my Select Subscription due to this kind on nonsense)
Regards
Danny Cooley
Freelance AEC CAD/BIM Technician Architecture, MEP & Structural ..... (& ex Low Carbon Consultant, ..... because they weren't that bothered!)
OBD Update 10, Windows 10 Pro, HP Z4-G4, 64Gb, Xeon 3.6GHz, Quadro M4000
I'm glad not to be alone with this nerve wrecking phenomenon. Yes, it resembles much 2D drafting as there seems to be no problem when in the top view. It’s when in Front or Side views you get stuck to the base plane. And this is not only in B Architecture! I just checked it in straight Mstn V8i, which does not carry the ATENV_3DSETUP config var. For a long time I have been thinking there is some basic setting I have missed out; but with all of you screaming as well, this looks more like a bug??
My sympathies ..... must admit though I'm only having this problem with BA. Standard V8i is OK.
Not sure what settings we have different. By default I have ACS Snap and ACS Snap Lock OFF (and very rarely use them) ..... tentative point and rotating Accudraw work fine.
Are the files in Microstation, ones that were created or worked on in BA? Maybe this is 'carrying over' some features/locked ACS or something related in to 'standard' V8i? Couldn't really say how that would be. Who knows.
But I'm certainly only having this problem in BA.
My understanding is that it is not a bug. It's some approach/strategy that was implemented for 'new users' so that they would find working in BA easier. As you have noticed, it could help in 'Plan View'. But the implementation of it clearly hasn't been thought through and tested properly, and has backfired somewhat.