Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Would be useful when particularly curtain walls have been modelled without the disallow join box ticked first and you want to disallow join to them all. You could select all instances in entire project and click a button (or un-tick a box) to disallow join to the selected elements.
The default wall join functionality in Revit is appalling.
For example, material handling gives no precedence to elements/layers that are marked as 'structural' for example, resulting in structure that is cut into or changes length due to touching non-structural element/layers -- this is not the reality of how buildings are built at all, and makes documentation much more difficult.
The current options for users are to either accept Revit's flawed and most often incorrect wall joins, to cycle through a few different alternatives which more often than not don't include a correct/logical one, or right-click the walls end and choose Disallow Join (where there are multiple overlapping walls this can be difficult to do without first isolating the wall(s) to be worked on) -- The suggestion to make this a separate tool to work on multiple walls at once would be a huge step forward, it would save me thousands of clicks for most projects.
Also the current Wall Join tool should highlight walls like AutoCAD, not simply show a box around the intersection, so users can be clear on which walls they are working with, as there are often many intersections and numerous walls close to each other.
@kimberly_fuhrman-jones, I will let @vitorbortoncello answer to his thought process, but the way I read his idea is, "I want to be able to select a wall or multiple walls and click a button and say "disallow from join" for all ends of all the walls I've selected all at once." The current methods of the tools makes you select each end individually which is good, but often we need both ends of one or more walls."
I'd like to also state that although I think it almost should be a related separate idea, Anonymous' thought of "Also the current Wall Join tool should highlight walls like AutoCAD, not simply show a box around the intersection, so users can be clear on which walls they are working with, as there are often many intersections and numerous walls close to each other." is an excellent suggestion as well.
"I want to be able to select a wall or multiple walls and click a button and say "disallow from join" for all ends of all the walls I've selected all at once. The current methods of the tools makes you select each end individually which is good, but often we need both ends of one or more walls."
May I kindly confirm with you the primary concern of the issue here?
Efficiency: Are there challenges with the existing tool, even though Revit allows multi-selection (using the Ctrl key) and mouse selection by framing the targets? https://streamable.com/glwqzq
Usability: Is the main issue that the walls are not highlighted like in AutoCAD, making it difficult to determine which walls are being worked on?
Something else...
Additionally, could you please share specific scenarios that justify the need to disallow joins for all ends of one or more walls simultaneously?
It would be much easier if the Disallow Joins option were available immediately after selecting walls, rather than having to use the dedicated tool. While I can right-click individual walls to apply it, I’d like the ability to do this on multiple walls at once.
@starry.cui, I don't think I knew you could do that. I have added that to my training package. I've also added WW as a shortcut for Wall Join so I don't have to go up and find the button. I rarely used that tool because it was always a bit of a pain in the butt I felt. Still is a little bit, but this helps.
But I do still agree that having the walls highlight would definitely be helpful as well so that we could then unselect certain walls or we could individually select/unselect walls.
In a perfect world... those walls would have gradient coloring, darkest at the ends where the join is, but then fading as it moves away from the joint spot. So if we've selected an entire wall, both ends would be dark and light in the middle. (opposite of course in dark mode).
Thanks a lot for the explanation. I totally understand the mindset of wanting to directly select walls to edit wall joins.
I understand the workflow like "select a wall or multiple walls and click a button to say 'disallow from join' for all ends of all the walls I've selected all at once" is convenient, but it can be challenging to determine user intentions, such as whether they want to disallow all ends or just specific ones in Revit, like https://postimg.cc/ZCkmfL7c
We will discuss internally and see whether there will be a way to improve your experience.
Dynamo, along with a Python node (or even some custom packages), is frequently used to solve exactly this type of repetitive workflow problem in Revit.
Here's how Dynamo would solve it:
Selection: A Dynamo node (like Select Model Elements or All Elements of Category) would select the walls (or curtain walls, where this is very common).
API Access: A Python script within Dynamo would access the Revit API (Application Programming Interface) and use the function WallUtils.DisallowWallJoinAtEnd(wall, end_index).
Batch Execution: The script would loop through the list of selected walls and apply the "Disallow Join" command to both ends of each wall (end_index 0 and end_index 1), accomplishing the work of hundreds of clicks in just one run.
Given that Anonymous' original post is from 2017, when can we expext this to be implemented? Can you make it into a dot update, please? I would not mind having this in older versions as well. How about tomorrow afternoon?
