Community
Civil 3D Forum
Welcome to Autodesk’s Civil 3D Forums. Share your knowledge, ask questions, and explore popular AutoCAD Civil 3D topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

C3D and Pipe Networks very buggy

41 REPLIES 41
SOLVED
Reply
Message 1 of 42
Anonymous
4314 Views, 41 Replies

C3D and Pipe Networks very buggy

As of C3D 2019.  i have issues regarding pipe networks that are from older 2017 files.  i have updated the file and saved over it then did audits and purges.  all to no resolution.  

 

When moving the profile view or adding a projected object to the profile view. it will reset the elevations of my pipe network and messes up all the settings of my network.  this is a big problem as i have to individually fix 20+ objects every time i want to change a projection.

 

ive attached some images to demonstrate.  if anyone can assist, that would be great.

41 REPLIES 41
Message 21 of 42
ralphsanchezATX
in reply to: Anonymous

I've submitted a support case with Autodesk and I would encourage the rest of you to do the same. 

Message 22 of 42
drazen.galic
in reply to: Anonymous

I would guess that maybe the problem is in the same name of the rules. I suppose that in both Civils (2017 and 2019) there is the same name of the rule (i.e. Standard) but which are different. Would be worthy to try to rename  in 2017 rule name. Then it should not be any influence of existing rules in 2019.

Not sure about that, but think that it is possible.

Regards,

Drazen

Message 23 of 42

I don't think that's the case, Drazen.  The rules are embedded in each DWG file.  Also, although Devin's DWG file used a rule set called STANDARD, my own DWG files - which are also exhibiting the same symptoms now - do not.

 

Message 24 of 42
Anonymous
in reply to: ralphsanchezATX

Of all the issues. This seems to be the best fix until cad stops running rules when you project

 

Message 25 of 42
ralphsanchezATX
in reply to: Anonymous

Has anyone else submitted a ticket on this?  I submitted mine on May 9 and it was assigned Case Number 14212977.  As of today (May 15), I haven't had any response whatsoever.  This is extremely disappointing. 

 

Message 26 of 42

My reseller submitted a ticket on my behalf, also on May 8th.  Autodesk's support system and ticket tracking is wonky.  I can't even get in to see the current status of my support requests. 


I've submitted bugs in the past and this silence is normal for bugs that reach the point where a patch needs to be issued. 

Message 27 of 42

Has anyone heard anything at all about this issue?  I've submitted two tickets and heard absolutely nothing; both tickets remain unassigned.

 

Message 28 of 42

I heard from our reseller that it was a known issue that they were working on as well as a few others for a Service Pack Release.  This was two weeks ago and I was told with testing and other variables to expect it around a month.  Knowing that sometimes fixes break other things, I am not holding Autodesk to this date, but just knowing they are working on it, is better than nothing.

Message 29 of 42
Anonymous
in reply to: Anonymous

having the same problem here. 

getting the error: "Unable to run macro: C:\ProgramData\Autodesk\C3D 2019\enu\C3DPipeNetworkRules.dll ..."

 

I've recovered previous versions (after saving 2017 files to 2019, but before Pipe network goes bonkers.) 

It's a project that I must carry forward from 2017 into 2019 to not upgrading is not an option. (also rebuilding from scratch is also not an option. budget reasons) .

Then without warning (as I was updating a point group)  ... C3D had major lag time... then popped up with the above error. No warning. it revised many of my 2017 pipe networks to elevations (inverts approx 300m below were I had them.) 

 

the Solution flagged is NOT an acceptable solution.  it simple details the problem further. 

I was very careful to avoid these "(1) When you're initially laying out the network in plan view, and (2) when you deliberately run the _AeccApplyRules command and then explicitly select the parts to apply them to. " 

 

to be clear. I did NOT "use pipe rules" in previous phase work (2017) as this is a retrofit in an old part of town. I Do NOT want use pipe rules...  (most were assigned the default "Standard" rule set) 

 

So my solutions is simple.  

create new Rule set "None" (self explanatory). one for pipes, and one for structures

Apply "None" rule set all pipe objects in the 2017 file before migrating files from 2017 to 2019, if possible.  

I did this after the fact... but it took hours of time to wait for it to apply None. 

 

Also, note "None" should be the default if all Civil 3d templates. not "Standard" Rule set. 

 

Instead of lazy work using "rules" apply sound engineering calculations, review, and judgement to all Pipe network objects. 

 

I'll note. I'm a 20yr veteran in ACAD/Civil 3d. I was on forums previously under different ID (change of companies).  so kindly ignore the lack of contributor status. 

 

lcollecutt

 

 

Message 30 of 42
Anonymous
in reply to: Anonymous

***Update***

Autodesk support has contacted me via email.  I will update you all as i get more information.

Message 31 of 42
kylenishioka808
in reply to: Anonymous

Got a helpful clue from a response by Autodesk.  Looks like the issue w/ my DWG has something to do with XREFs.  As a test, I detached all XREFs and promoted all surface DREFs in the problem DWG and then opened it in 2019.  So far so good, but I don't see the benefit to upgrading to 2019 if the problem could re-occur later. 

 

This doesn't exactly solve the problem, but it may be a better temporary workaround for those who are still stuck.  In 2018, detach XREFs and promote DREFs.  Then open in 2019 and reattach and relink. 

Message 32 of 42
Anonymous
in reply to: kylenishioka808

See my post above. the issue is "pipe rules" ... more specifically pipe rules are being applied when they are not prompted. creating empty Pipe rule sets (none as the example) and applying making them current to each pipe network resolves the issue temporarily until AutoDesk fixes this "know issue" with a service patch. then when it's fixed pipe rules can be swapped back into place.  

good luck. 

Message 33 of 42
jefflambert9091
in reply to: Anonymous

Our reseller submitted a ticket not too long ago on the 2018 to 2019 bug on pipe networks.  A patch should be coming with in the next few weeks.  

Jeff
Civil 3D 2024
Message 34 of 42
jasonr
in reply to: jefflambert9091

anything yet? what a pain in the ass.

Message 35 of 42
Anonymous
in reply to: jasonr

There are a couple other threads with the same issues. 

Via an Autodesk support agent I received a "stock" answer when they know they've screwed up and are under fire: 

"Thank you for the feedback. I understand your concern about the relative difficulty of fixing this issue. You are more than welcome to submit product feedback to our developers here: https://www.autodesk.com/company/contact-us/product-feedback "

 

I encourage all of you to provide feedback ASAP; both directly yourself and request your Resellers to do so as well. 

Ensure to flag the issue of "Pipe Rules" "Pipe networks" in "Civil 3D 2019" 

 

Kind regards.

Message 36 of 42
jasonr
in reply to: Anonymous

done.

Message 37 of 42
Anonymous
in reply to: jasonr

i received a response from the rep at Autodesk.  they elevated it and are researching it with the development team.  when we get an update is still up in the air.

Message 38 of 42
CADmgrMike
in reply to: Anonymous

I am using 2019.1 and opened/saved a 2017 pipe network drawing with no issues. I projected a feature line onto the profile view, moved profile view and it is not applying the pipe rules automatically.

Mike Porter
https://provostandpritchard.com/
Message 39 of 42
Charlie.Ogden
in reply to: Anonymous

The Civil 3D 2019.1 update has a couple of fixes related to pipe rules running automatically and changing network elevations unexpectedly.  One fix stops the automatic changes due to pipe rules in a reference template.  The other fix stops automatic changes due to a surface being rebuilt or synchronized.  We believe the latter was the root cause for other cases where pipe elevations were changing.

Could you please confirm that the update resolves the issues that you were seeing as well?

Thank you!



Charlie Ogden, PE
Product Manager
Message 40 of 42
ChadBalser
in reply to: Charlie.Ogden

Charlie,

 

Sorry, we can't test the 2019 service pack anymore.  We moved everyone back to 2018.  We will likely avoid 2019 completely at this point.  

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Rail Community


 

Autodesk Design & Make Report