Is there a setting squirreled away somewhere that i can check to force “undefined” elevation objects to display down at 0.00 elevation?
1 Like
You can run project clean up and check the set elevation outside range to undefined bottom of the page
1 Like
Not that I know of. I sent a support ticket about this when the behavior changed, or at least when I first noticed, and it was escalated as an enhancement request.
It’s interesting how many things get changed without making the release notes or help documentation…
1 Like
Advance select for ? or go into the 3D view and select all lowest work areas while zooming out.
For sure, it’s an odd thing. I expect at some point, someone was frustrated with jumping back and forth to elevation zero in 3D view to grab items, but man… when you don’t want them there, it’s a pain when the whole works is smack dab in the middle of your model…
Francisco, I still want all of the geometry to remain on undefined elevation. I just don’t want it to hover up near the project.
A handful of updates back it switched from being at zero elevation to floating at an elevation that i expect is at an “average” project elevation. Seems like an easy setting to manage too.. just give a option in project settings “display undefined objects at elevation: …”. Could be handy..
It appears that undefined elevations are being assigned based on the most recently created surface. When I need to move these objects out of the way, I use the following workaround:
-
Create a box at the desired elevation (typically elevation 0).
-
Generate a surface from that box.
-
Close the 3D view and then reopen it.
After reopening the 3D view, any objects with undefined elevations are repositioned to approximately the average elevation of the newly created surface. In the case of a box at elevation 0, the undefined objects are moved close to that elevation.
5 Likes
Awesome, thanks for the workaround tip!
1 Like