Announcements
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

graphics & method for modifying Toposolid

graphics & method for modifying Toposolid

The new Toposolid in Revit 2024 may have some new developments that are advantageous, but the work flow and graphics when editing points on a Toposolid are terrible and major hinderance to design and production. 

 

When editing a Toposurface in 2023 and prior, as points are added/modified contour lines between points are shown in real time, based on Site Settings. The background visibility is dulled, but detail lines, images, etc. that may be used as reference are still easily visible. 

 

When modifying a Toposolid in 2024, as points are added/modified, contour lines are NOT shown in real time, but folding lines are shown triangulating between points. When placing points, Revit wants to snap to these folding lines. The background visibility is dulled much more, such that detail lines, images, etc. are dulled to the point where they are barely visible and very difficult to use as reference. 

 

The only way to see contour lines is to exit out of edit mode to see the results. With Toposolid Revit even more aggressively makes contour lines between points in close proximity at curves, creating contour lines that go across curves at multiple points rather than following an intended path. Having to go in and out of edit mode to see contour lines is very time consuming and disruptive to productive work flow. 

 

The Folding Lines are generally meaningless. There's no point in showing them, anywhere. They maybe there for Revit to do whatever it needs to do in creating Topography, but we do not need to see them and have no use for them. That Folding Lines are visible in edit mode, and Revit want to snap to them, is absurd. We need to see the contour lines as points are added/modified, not Folding Lines. 

 

Toposolid editing is also much slower than Toposurface because Revit is constantly triangulating between every point in real time. Adding multiple points along contour lines has now become painfully slow. With Toposurface, multiple points could be added very quickly and contour lines generated instantly. There's even an add-in called Auto Clicker which allows you to move the the cursor along a path and points are added by setting an auto click interval, instead of clicking for every point. This is not possible with Toposolid because the response time is so slow. 

 

It's annoying AF that Revit is constantly making multiple contour lines between points in close proximity at curves rather than following an intended path. But there's a method to force Revit to do what you want by adding points that are +.1 or -.1 adjacent to points that are intended to define contour lines. It's a lot of extra tedious work, but it gets contour lines to behave. Since contour lines are not visible in real time when editing Toposolid, you have to go in and out of edit mode, and it makes the process even more tedious and slow. 

 

When Autodesk bought Site Works from Eagle Point Software, and renamed it Site Designer, it had some very functional and efficient tools for site grading. such as Feature Lines. then Auto desk decided to discontinue it. These tools were adopted from Civil3D and intended for use by Architects. So it is possible that efficient & effective site grading tools can be developed. 

 

Revit needs to be function in a manner that supports the way Architects work. Topography has always been lacking in functionality. One of the most basic functions of topography is site grading, and it's been made even more disfunctional with Toposolid. Autodesk has done a major disservice to it's customers by not provided an easy and efficient manner to grade a site with contour lines, cut/fill, etc. 

68 Comments
mpukas
Collaborator

@PatrickGSR94  revit is creating points at most contour line vertexes, but not all. Toposurface, for me, used to create more points along a contour line, not just vertexes. The lack of sufficient points causes Revit's contour lines to "bleed", or "push", beyond the .dwg contour lines. With toposurface it was possible to add points as needed to get the contour lines to behave. It was a painstakingly slow and arduous process, but it was possible and it worked. With toposoild that process is virtually impossible due to the slow response every time a point is placed, and not being able to see the contour lines while editing complicates it further. 

 

A far bigger problem is revit is creating extraneous points at the perimeter of the toposolid that are not related to the .dwg contour lines. It's excruciating and colossal waste of time to scan the entire perimeter of a 12 acres site and select each point to see which ones are higher or lower than the .dwg contour lines, and delete or edit them. 

mpukas
Collaborator

As if working with points as the primary and only means to generate and modify Topo isn't bad enough, the functionality of working with points is severely lacking: 

While placing points, the elevation input will not keep the value when the command is not used continuously. The Elevation has to be input every time the command is used. 

Points cannot be copied. They can be moved. New points have to be Added using the Add Point tool, and again the elevation has to be entered newly every time the command in initiated. 

When using the Add Point tool, points will not snap to Lines. The Move command can be used to snap to a Line. This is such a waste of time to place Points but not be able to have them Snap, only to then have to use Move to relocate the Points that were just placed. 

 

The implementation of Toposolid and Points by Autodesk is a colossal failure. This change was released without proper development. This is a blatantly obvious example of how Autodesk's Revit Development has no understanding of real world use of Revit. 

r.grandmaison
Explorer

I think the problem, both with toposurfaces and Toposolids, is that the developers are thinking about how to create a topographic model in the same way contours are created by way of X,Y,Z points taken during a civil survey by a surveying crew. That’s great for creating by data points from a total earth station, but it’s not the way architects work with topography, mostly.
We work and think with contour lines mostly, and points only at critical locations like building corners or curb cuts/walkways. When it comes to shaping land, I would MUCH rather have an actual contour line I could select/add points to, and live drag those points and line segments around.

I could really care less about the triangulated DTM. Let me work with contour lines directly, the way we are trained to do- and most importantly, the way we think about surfaces when shaping land.

r.grandmaison
Explorer

And, if we ever get the ability to work with actual contour lines instead of elevation points, then implement a way of working with actual contour splines, not approximations based on line segments. Civil Engineers produce contours composed of line segments because they are working from that triangulated/interpolated DTM from their survey points. They like lines segments too for contours because they are more measurable. But, nature/geology/surfaces in real life are not linear abstractions, real contour lines should be curved and spline-like, not jagged approximations. A USGS map is a great example of curved/spline contours and are shown in ways that architects THINK of elevations in. Of course we have the need for straight segments and sharp/angular vertices on contours (drainage ditches/walkways/roads/pavement/etc), but I would really much rather welcome the ability to work with contours in the same way Adobe works with path editing by editing the control points on a spline/path with the ability to add/delete control points along that path/contour and change them from smooth to corner conditions. So, Toposolid devs, please go meet with Adobe devs and see their work!

PatrickGSR94
Advocate

@r.grandmaison i don’t know about you but I think primarily in calculated elevations and slopes. So with a building floor elevation, I’m placing and calculating various points away from the building. For things like ADA access, with 2% slopes at landings at doors, 5% slopes max along sidewalks, 6 inch drops at curbs, 8.3% slopes at ramps, 1% slopes along drainage swales and so on. What the contours do is a by-product of the elevations I need at various locations. 

at the end of the day, what’s important is, will the project get built correctly? Will segmented vs spline curve contour lines affect how the project gets built? The answer is no. It will still get built just the same. 

@r.grandmaison, I agree 100% and posted something similar in this thread a while back. Lines are the key. Of course, we still need the ability to import points to generate a surface in the case where the data is coming directly from a surveyor, but that data should be converted to actual lines. I have actually created topo surfaces in the past by creating model lines and adjusting the height of those lines then snapping nodes to them. In other words, the contours themselves should be model lines. It would be similar to draping fabric over wire to create the surface. And I also agree, the triangulation should go away altogether as it only creates confusion. The key is to be able to create a surface quickly and easily. I did a topo solid a few months ago which took me more than a full day to find out a few days ago that they're thinking about moving the house about 40'. So now that's upwards of 16+ hours for something that should take about 2.

pedruccioli
Advocate

I'm just here to say that Toposolids are a copy/paste from the Floors code, with a little tweaking. It's half a tool, to say the least, and it doesn't fit architectural design, which it was intended for. Engineers use Civil3D. We need something smart, fast, light, simple and good to the eye. Or should I say, we need improved Toposurfaces, not some other tool that makes 1/10 of the job.

nehama87
Contributor

I agree with all the above and would like to mention that when upgrading Environment for Revit to work with Toposolid we addressed all these issues and leveraged the Toposolid to improve flexibility while designing topographies. We also maintained some of the advantages of the Toposurface. You can learn more here: https://archintelligence.com/news/so-what-exactly-is-the-toposolid/#more-4759 

 

@mpukas @PatrickGSR94  I hope this helps.

zeviW4AYU
Explorer

Strongly agree that we need to see contours while modifying sub-elements of toposolids. Constantly needing to escape & restart the command to check contours is asinine. Contour lines are the most well established method worldwide & industry-wide to project a 3D surface into 2D for a reason; it is so much more intuitive and usable to show them while editing. A 2D projection of a mesh, on the other hand, is utterly meaningless--there is no way to understand the Z-axis based on a flattened triangulated mesh.

 

We're not looking for a perfect tool, we're looking for a usable tool, and right now, the way Revit 24 handles topo is ... not great.

Status changed to: Accepted

Accepted:

Congrats! We think this is a great idea, so we've decided to add it to our roadmap. Thanks for the suggestion!

 

To follow the progress of features in development, please see the Revit Public Roadmap and join the Revit Preview Release to participate in feature testing. (Note that Accepted Ideas may not be immediately available.)

 

The Factory

Mark_Engwirda
Collaborator

@mpukas  and @kimberly_fuhrman-jones That is great news.
I have added a further idea/requirement that is missing from modifying toposolids; it would be nice to merge it with this idea and place it on the roadmap as well. 

https://forums.autodesk.com/t5/revit-ideas/ability-to-create-points-outside-of-the-toposolid-boundar...

rhBDHX4
Enthusiast

@kimberly.fuhrman - glad to hear Autodesk is going to work to improve this, thank you!

I'd echo the majority of the comments/ concerns/ frustrations on this thread.  I'd like to add the following input, based on working solely one one 14k sf house in Revit 2024 for nearly a year.  I feel that the toposolid tool ultimately really slows down my interaction with the model.  I have six separate structures, all with foundation walls, 100+ piers, basements, crawl spaces, and a good deal of complexity at the ground plane.  I'm up to over twenty Model-in-Place Void families to do various cutting of the topo.  I suspect I've used the cut tool at least 400 times to cut all the foundation walls, piers, exterior hardscape elements, etc into (or really out of) the toposolid, otherwise my building and wall sections look terrible. 

In other words--the toposolid tool requires a TON of cutting with 3D model geometries (walls, floors, structural foundations, etc), as well as inevitable Model-in-Place void families as a last resort, again, so that any sectional drawings that have topography look good/ correct.  On top of that, per usual, to get sections to look good in general, I have probably close to 1,000 joins of building elements: walls, floor, roofs, ceilings, etc., so that the linework/ heavy cut-line/ assembly layers look good in sections.

Given all this, here is what I am experiencing that is unique in 15+ years of using Revit w/ Toposurface tool (and doing all my building element joins per above per usual):  the model is getting extremely heavy and laggy.  Even with a gigabit connection, using BIM Collaborate Pro to host the model, and great laptop, merely cutting one pier or one wall into/ out-of the toposolid takes at least  25-seconds.  Joining a floor to a wall on the second level, with zero direct interaction with the topo is taking 15+ seconds.  I worked on a more complex and similarly large/ multi-structured house in Revit 2023 with toposurface tool, and had ZERO of these laggy issues.  My hunch is that ultimately, given that the toposolid is cut hundreds of times by all sorts of building geometry, even as I go to join a second-floor floor assembly to a wall assembly, Revit is having to think about/ calculate the implications (if any) to the Toposolid. 

Ultimately, by treating the toposolid as a solid that gets booleaned like crazy to get drawings (particularly sections, but also plans) to read, it seems to me that now the toposolid is intrinsically joined (or rather cut)/ linked to the 3D building geometry elements, so that even just joining building-only elements is taking magnitudes of order longer than any per-2024 project using toposurfaces; Revit seems to be considering the toposolid for every join, regardless of whether or not it has a direct connection to the toposolid.  This seems like a huge problem to me.  It certainly has taken literally days of productivity away from me over the course of a year.

Some suggestions:  previously, the toposurface + building pad tool seemed "smart" in the way it allowed piers, foundation walls, and other building elements to be hierarchically "above"/ in-front-of the sectional representation of the toposurface.  If the toposolid feature could be altered to not have to cut concrete foundation walls and structural foundations (piers/ footings/ etc) into the toposolid, and rather they just get drawn on top of/ hide the toposolid, that would have saved me days of work.  Maybe there is a way to provide end-users options in terms of the layering / hierarchy of toposolid vs building assemblies?  I realize I can do (and have done plenty) of MIP void families, but those are squirrely to edit after making them, and with my foundation walls reaching down below my subgrade slabs, it doesn't make sense to make 100+ MIP void families, when I can just cut the wall into the toposolid.

Something has to give.  I'm definitely reverting to 2023 if something doesn't change.  Sitting around for half a minute to cut a wall into the toposolid, or just joining building assembly elements is not how anyone wants to spend their time, and is not like what I experienced with toposurfaces in the past.  I do like that the toposolid approach would've been awesome on my winery projects with caves, and allows for really carving the topography to suit the project, but not at the expense of my time.

Here's a screenshot of just my toposolid, and then the whole project, fwiw.  Would be willing to discretely share the file directly with Autodesk if that helps for R&D and solving the issues my team/ office is having...

 

 

Toposolid-Only.pngFull-Model.png

brucegund
Advocate

I hope that ability to "draw" walls, foundations, floors over the Toposolid will also be added to the "accepted" implementation of the idea! So that we do not need to cut them manually....

 

Thanks!

Bruce

@rhBDHX4 ,

Thank you for that fantastic reply! The best way to interact directly with our product teams on the development of features like Toposolids is to join our Revit Preview Release. You can also follow development and give feedback on our Revit Public Roadmap. Our teams are actively working on this and would certainly appreciate the feedback and example projects. Please let me know if you need any additional assistance!

ellison
Enthusiast

Here's another toposolid editing glitch that should be easy to fix: when modifying subelements of a toposolid, if you try to move a combination of points and fold lines, they will not all move the amount you specify.  They will often move exactly twice as far as you specify - as if the move operation is being repeated.  if you are careful to include only points or lines in your selection set, then the objects move as expected.   The filter selection tool would be of help in avoiding the issue, but it is unfortunately not available when selecting subelements of a toposolid - another point I'd love to see addressed.

PatrickGSR94
Advocate

@ellison 

This is yet another problem caused by this whole "subelement editing" workflow.  It's all extremely finicky, and always has been, ever since the subelement editing was introduced for floors and roofs.  It needs to be a separate Editing Mode, similar to the Sketch Edit mode used for many Revit system families, with discreet Finish and Cancel buttons, so that hitting Escape or trying to use other tools doesn't automatically cancel out of the subelement edit mode.

Status changed to: Implemented

Implemented

We are pleased to say that this has been implemented in Revit 2025! Thank you for your contribution to improving Revit!

Help | Toposolid Enhancements | Autodesk

 

 -The Factory

mpukas
Collaborator

I've installed Revit 2025 and have been using it for about a week. I've done some very minor work with Toposolids. So far, everything that Autodesk has done in this version is what should have been done in 2024. That first version should have never been released in the form that it was in. It was poorly thought out and underdeveloped. It caused many of us massive headaches and frustration for a year. 

 

The UI and workflow for Toposolids in Revit 2025 are STILL problematic: when selecting multiple points to move them (such as when a building footprint changes), multiple points do not move accurately - if I type in distance to move them, they all move twice the distance entered; if I select a start and end point, they all move twice as far as the end point. as @PatrickGSR94 stated, there should be an Edit Mode for editing points. When adding points, the Elevation that is entered does not stay when the command is stopped and started again. When in Modify Sub Elements, triangulation lines are still show, in addition to topo lines - this still only serves to add confusion and unnecessary complexity. 

 

And above all, grading a Toposolid by individual points is STILL absurd. Autodesk needs to bring back basic site modification tools that were developed by Eagle Point Software (which Autodesk bought, rebranded as Site Designer, and then abandoned) such as Feature Line and Soft Terrain. Feature Line can have start and end point elevations adjusted, or the slope between points adjusted, and the spacing of points along the line adjusted. Soft Terrain can be a shape of any geometry, any vertex point can be adjusted, the slope between vertexes can be adjusted, and the spacing of points between vertexes can be adjusted. 

mpukas
Collaborator

I echo and want to draw attention to @rhBDHX4's and other's posts re: cutting a topo solid. SOMETHING has to be done to improve the workflow and functionality of a Toposolid vs building foundations. It is common practice to have separate files for Site and Buildings, whether there is one building or multiple. The downfall is the Toposolid, and getting drawings to read graphically correct. It is such a waste of time given Revit's limitations to have to MIP numerous voids and void families to cut the Toposolid. 

mpukas
Collaborator

In Modify Sub Elements, points cannot be copied. Points can only be added using the Add Point tool. Which gets back to the drawback that the elevation is not kept from the previous input. 

 

PLEASE - keep the elevation input, and allow points to be copied. 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea