2015: Sump depth

[rkmcswain]

Not sure if this is an "across the board" bug, but here, in C3D 2015, the default sump depth for pipe network structures defaults to 2.0 regardless of rules in place. Sometimes there is an error message involved. The manual fix described here works (replacing the 2015 DLL file with the 2014 version).

However, after applying C3D 2015 SP2, the manual fix is overwritten and the new DLL file suffers from the same problem as before (rules are ignored).

You must go back and manually replace the 2015 DLL file (C3DPipeNetworkRules.dll) with the 2014 version after you apply SP2

[BrianHailey]

Hey R.K.,

I'm not seeing this at all. I created a parts list, added two structures, each with a different rule set applying a different sump. When I created the parts, they appear to honor the rule. Am I missing something?

I'm using Civil 3D 2015 installed from the Ulitmate Suite with Service Pack 2 installed.

VIDEO

[BrianHailey]

And, just to double check, I went into the structure property and you can see the sump is set to 0.

[rkmcswain]

Hence my first sentence... 

All I know is that upon deployment of 2015 here, users started getting the error message [Unable to run macro for "C3DPipeNetworkRules.dll"], which eventually led me to the KB article, but not before my reseller alerted me to the "fix" of replacing the file ("C:\ProgramData\Autodesk\C3D 2015\enu\C3DPipeNetworkRules.dll") from the 2014 install.

Users were getting this error message and the rules regarding sump depth were being ignored (it was being set to 2.0' instead of 0.5')

We applied that "fix" (or replacing the dll file) maybe 3 months ago and everything went back to working fine

Fast forward to this week after deploying 2015 SP2, and now everyone's sump depth is being set to 2.0' instead of 0.5' (but without the above mentioned error message). The 2014 "dll" was eveidently overwritten by SP2. Replacing it again with the 2014 version makes everything work again (sump depth obeys the rule of 0.5')

Thanks for any input!

[rkmcswain]

Couldn't remember his forum name to give credit earlier...but it was @ToddRogers-WPM who got me that fix.