Hi There,
I got this message in my model. Wondering if this has happened to anyone else and how does this affect the model and how to eliminate this?.
"the maximum number of open hydraulic models allowed (5) has been reached"
Thanks,
Dawina
I'm running clash detection with ORD version 10.10.1.3. This problem pops up, maximum number of open hydraulic models allowed (10) has been reached. Then I couldn't proceed to performing the clash review. Is there a solution to this now? Thanks.
Hi, I'm using version 10.10.01.03 of ORD and I'm working with composite models to create my long & X - sections (usually I've got about 30 to 60 references attached), they are multidisciplinary. It's been explained why communicate, about maximum number of hydraulic models allowed, pops up. My question is - wouldn't it be enough for it show only once, I need to click on it 20 times when ie. changing views, this is quite time consuming and annoying. Profiles are displayed anyway, so can't see the reason for showing it so many times.
We changed the way that this functionality works in the 10.10.20 version of ORD. Before then, there was a limit of 5, then 10 references. There were performance implications to this, because the software was reading and extracting the databases from the references, and this could take considerable time to do. From 10.10.20, we don't read or extract the drainage and utilities databases in the referenced design files, so you won't get the message any more. This means that the properties in the databases are not available, for inspection or annotation, so what we've done is to store more properties on the graphics - more information on the nodes, conduits and catchments, and some results as well, like flow and capacity on conduits for example. This information is visible in references, and can also be used for annotation.
thank you
it looks that it works in newer version
Hi,
After working for a while now in never version of ORD (10.10.21.04), it looks that communicate about hydraulic nodes disappear, that however was replaced by extreme slowness in 3D cut in profile view. Anything like even panning in the profile, adding annotations, measuring take ages, this is not experienced without 3D cut.
Could you possibly look into issue? I know that the other users - who work in the version mentioned above are experiencing similar slowness.