I am writing to report a problem I came across with in Revit MEP 2014 ( trial version) and see if you have already found a solution and can help me out.
When working on ducting, if, for example, there is the main duct and you get a flex connection (picture 1), a disconnection occurs when sizing the system (picture 2). This unprecedented error just comes with this version of the application and according to my own experience and a few others, there is no such complication with earlier versions.
I would be grateful if you could guide me and let me know if there is a solution to the problem.
Hello,Saeed! Welcome to the Discussion Groups!
You you be able to attach a small sample Project file? Basically just re-create the issue, use Purge Unused, and manually delete the unnecessary Duct and Pipe Fitting and Accessory families from the Project (Purge Unused may not remove them). This should get the file to a small enough size to post here.
There is no attachment. Try attaching it again and if give you any trouble, send me a Private Message and I'll give you my email address.
I know this post is a little old, but I have just discovered the same issue. Running Revit MEP 2014 using any flex duct branch family, resizing the square ductwork causes the duct branch to disappear and disconnect.
Web Update 2 is installed.
Are there any updates on this issue?
Please help! I am having issue with Revit MEP 2014, when changing the size of my duct, the connection between my main duct and flex duct disappear cause system disconnect. Please give directions on to resolve this issue in REVIT MEP 2014.
Thanks in advance!
Same problem here too. I would create a duct run off the main duct. delete the run leaving the pop (Shoe) from here add flex to air terminal. If i resize the duct width, the pops are erased causing the flexes to disconnect from system.
Can you please install RVT2014-SP2 and let see ?
Someone told me that it has been resloved if we install SP2. I already installed but still it doesn't work
I logged an Autodesk support case on this issue. They have responded by saying that they can reproduce the problem and it has been passed to the development team.
Basically I read that as: Bug recognised, might try to fix it in the next web update.