In Microstation v8i I have an mdl app called SWA that drew a rectangle (in 2d or a cube in 3d) showing the extent of the solid working area. Does anyone know a way of doing this in Connect? It's really useful for explaining to people why they are having problems with geometry that's way outside the SWA.
Thanks
Duncan
David,
The two links you provided refer to rather outdated information with regards to SWA (15+ years old).
The explanations from Brien Bastings are much more up to date and relevant to the current implementation of the SWA.
Regards,Ron
For some more in depth information regarding the SWA you may find the following articles useful:
https://communities.bentley.com/products/microstation/w/microstation__wiki/2972/using-the-solids-working-area-in-microstation-v8-cs
https://communities.bentley.com/products/microstation/w/microstation__wiki/2898/your-solids-working-area-global-origin-working-units-and-you-cs
Brilliant. Now I understand. Thanks Brian. That's what I'm proposing to do.
Duncan Macdonald said:My experience is that lines drawn that far from 0 have problems with snapping and accurate location of snaps.
Yes, there can be double precision floating point issues when you are millions of uors away from 0,0,0 that are unrelated to the swa, the swa only applies to breps (smart solids, etc.).
The recommended approach is to model near 0,0,0 (uors) and specify a global origin to define the geometry's location in the world. But again, this is just good practice for how numbers are represented, it's not because of the solid extent setting.
What you don't want is people changing the swa to 1000 km and thinking, now everything is inside the swa and I'm good to go...because again, the swa is just a scale. It's basically just determining how far apart in uors 2 points need to be to be considered unique, etc.
-B
Answer Verified By: Duncan Macdonald
In our case if we are using Ordnance Survey coordinates and modelling a building in London, then we are more than 500 kilometres from the origin. Clearly .dgn can do this but I know from past experience that doing so causes problems with rendering and accuracy as well as translation to other apps. How does it work with 2d geometry? My experience is that lines drawn that far from 0 have problems with snapping and accurate location of snaps.