Pressure Pipes Resetting to 0

[ToddRogers-WPM]

I submitted a case to Autodesk, case #14309006. This was submitted 2 weeks ago and I have still not heard from anyone. I did however, email it to @SethHall at Autodesk and he passed it along.

I was wondering if anyone has seen this issue.

When a pressure pipe is placed in profile, it works just fine. When that same pressure pipe is opened in a VDI environment, it resets to elevation 0. However, if you look at the Pressure Pipe Properties, the elevation is there. So, a workaround is to Swap Part, swap the part with itself, then the pipe goes to correct elevation. See video attached...

[Anonymous]

That’s some crazy ****.  Have to admit I don’t use pressure pipes much.  Have seen flattening with pipe networks when using reference templates.  I remember Tommie was battle with the pipe networks issue when we were at ITF

https://forums.autodesk.com/t5/civil-3d-forum/c3d-2018-pipe-network-change-elevation-automatically/m...

[BlackBox_]

What specs are you providing VDI client sessions of Civil 3D?

What specs does your VDI host (RDSH; Remote Desktop Services Host) have?

May I ask why you're using VDI in lieu of RDP? 

I also do not use Pressure Pipe Networks - no real point, as the Civil 3D team completely missed the mark.

Gravity/Pressure should be a Property of a given Pipe Network (most Sanitary networks contain both at the same time via Gravity Sewer, Wet Well/Lift Station & Force Main). Both (in Civil 3D) allow for pipes to be drawn along an arc, but each has different 'parts' & 'catalogs', and only one actually kinda sorta is able to be interchanged with Infrastructure Parts Editor or InfraWorks properly.

To boot, the Civil 3D team still hasn't provided for Directional Drills; instead, one must fake & bake it using Profiles with Curve Settings that represent that pipe material's minimum bend radius. Grrr

[ToddRogers-WPM]

@BlackBox_Unfortunately, I'm just the middle man at this point. I do know that they are using Advance 2000 as a VDI.

[BlackBox_]

No worries, @ToddRogers-WPM - I provide my employer CAD/IT Admin, so I sometimes hop down the rabbit hole quickly. Haha

Everything has trade-offs.

A couple of long-time issues with VDI (on-premise or cloud-based) is that the RDSH (aka the physical server that hosts VDI) doesn't have enough physical GPU installed to allocate enough vGPU to VDI Clients and that even the newest generation of multi-core Xeon (read server-grade) physical CPUs has a significantly slower single-core clock speed than a basic i7-7700K physical CPU, which results in a VDI Client with 4+ vCPUs that are simply too slow to adequately handle typically heavy Civil 3D loads.

Say network latency isn't a factor, those issues combined can be costly production killers. 

Good luck ~ Cheers

[ToddRogers-WPM]

And now I know why you go by BlackBox! Thanks!!

[BlackBox_]

FWIW as a comparison to your VDI specs (if/when you get them internally; don't have to post), here are the physical workstation specs** we just implemented as a daily plans production shop using Civil 3D for less than $2,500 per user:

https://forums.autodesk.com/t5/civil-3d-forum/civil-3d-2016-slow-computer-issues/m-p/7472150/highlig...

**I just upgraded my Samsung 960 Pro to a new Samsung 970 Pro last week.

You always get what you pay for, but never have to pay retail! Haha