Path of Travel lines is a good start to a great addition but it needs some work......Unless I'm missing something.
1. There needs to be an option to not consider overhead doors.
2. There needs to be an option where the path follows walls (a specific distance from the wall) to the nearest exit door.
Solved! Go to Solution.
Path of Travel lines is a good start to a great addition but it needs some work......Unless I'm missing something.
1. There needs to be an option to not consider overhead doors.
2. There needs to be an option where the path follows walls (a specific distance from the wall) to the nearest exit door.
Solved! Go to Solution.
Solved by ToanDN. Go to Solution.
hello, are you referring to this see LINK. thanks
hello, are you referring to this see LINK. thanks
.
That video does show the new "Path of Travel" option. I've attached a screenshot of what I would like to see changed.
That video does show the new "Path of Travel" option. I've attached a screenshot of what I would like to see changed.
Try this: In the OH Door Family, make the Geometry not Visible in Plan/RCP, and use a Detail for door representation in Plan/RCP.
...is the OH Door actually a Door Family. Is their a nested Family in it?
Try this: In the OH Door Family, make the Geometry not Visible in Plan/RCP, and use a Detail for door representation in Plan/RCP.
...is the OH Door actually a Door Family. Is their a nested Family in it?
Changing the door to another category would make the door schedules incorrect. That is not an option.
Changing the door to another category would make the door schedules incorrect. That is not an option.
the overhead door is an actual door family. There are no families nested in it.
the overhead door is an actual door family. There are no families nested in it.
@JGuliker wrote:
Changing the door to another category would make the door schedules incorrect. That is not an option.
We just had a similar thread earlier today. Changing the Visibility of the Geometry resolved in that case.
@JGuliker wrote:
Changing the door to another category would make the door schedules incorrect. That is not an option.
We just had a similar thread earlier today. Changing the Visibility of the Geometry resolved in that case.
See attached.
See attached.
What did you do?
@barthbradley wrote:
What did you do?
I nested a shared generic family in the door family.
@barthbradley wrote:
What did you do?
I nested a shared generic family in the door family.
I see that you nested a non door family into that overhead door family which does work. Thanks for the suggestion.
Now the only thing left is to have the travel path follow walls. Maybe that is something autodesk can add in future updates.
I see that you nested a non door family into that overhead door family which does work. Thanks for the suggestion.
Now the only thing left is to have the travel path follow walls. Maybe that is something autodesk can add in future updates.
Seems I can ignore Overhead Doors by simply unchecking one box in Route Analysis Settings.
All doors shown here are OOTB:
Seems I can ignore Overhead Doors by simply unchecking one box in Route Analysis Settings.
All doors shown here are OOTB:
@barthbradley That does seem to work but then it ignores all there other categories as well. Then Columns would also be ignored.
@barthbradley That does seem to work but then it ignores all there other categories as well. Then Columns would also be ignored.
Yep, I discovered the same thing as I played around a little more with this new tool. I trying to figure out the intelligence behind it, but every new discovery I make about it, seems to confound me even more.
Yep, I discovered the same thing as I played around a little more with this new tool. I trying to figure out the intelligence behind it, but every new discovery I make about it, seems to confound me even more.
What is your desire to have the path of travel follow walls in parallel? I think I know the answer in that it is the way we are used to identifying these travel distances - but I checked code. In both the IBC and NFPA 101 (2 primary codes I deal with) there is no mention of requiring the travel distances to be orthognal (or parallel) to the partitions. Granted, this gets into the realm of "as a crow flies" distance calculation but this is not prohibited by code.
Granted, there my be some code officials out there who would tell me to go fly a kite and to show the path of travel "the way it's always been done" 😕
What is your desire to have the path of travel follow walls in parallel? I think I know the answer in that it is the way we are used to identifying these travel distances - but I checked code. In both the IBC and NFPA 101 (2 primary codes I deal with) there is no mention of requiring the travel distances to be orthognal (or parallel) to the partitions. Granted, this gets into the realm of "as a crow flies" distance calculation but this is not prohibited by code.
Granted, there my be some code officials out there who would tell me to go fly a kite and to show the path of travel "the way it's always been done" 😕
I'm having troubles with the path of travel. I'm getting an error when I want do let it pass through a curtain wall door.
Any suggestions?
I've checked the family. and it is a door family.
I'm having troubles with the path of travel. I'm getting an error when I want do let it pass through a curtain wall door.
Any suggestions?
I've checked the family. and it is a door family.
Check Curtain Panels in the Route Analysis Settings dialog box - but then it just might go through other panels in the curtain wall.
Check Curtain Panels in the Route Analysis Settings dialog box - but then it just might go through other panels in the curtain wall.
Can't find what you're looking for? Ask the community or share your knowledge.