Custom subassembly strings not showing and crossfall is different from the one made in SAC

[KimJG7V9]

Hi, I am new in using Civil 3d. I explored the subassembly composer to make a few decisional on my template. However, when I imported the .pkt file and applied it to a corridor, only the edge of lane and shoulder strings were shown. I made a simpler one as attached. On the section-view editor, it looked correct as it showed the ditch after the shoulder. On plan, I was expecting to see strings along 1. ditch front, 2. ditch base, 3. ditch back, 4. daylight.

Further, I followed an instructional video in creating and assigning parameters. I applied it on the traffic lane and shoulder. I've put in "-Crossfall" as the Slope in SAC, but in Civil 3d properties, the crossfall showed as positive while the slope is falling down.

Would appreciate any help on these please.

Thanks!

[ecfernandez · Accepted solution]

Hi @KimJG7V9, thanks for posting your question to the forums. After checking your file I can say the following:

Problem with "strings": I think you refer to feature lines right? Feature lines that are drawn all the way up the road on the points P7 and P8 trajectory. If so, you are not seeing these feature lines in Civil 3D because those points in SAC have no codes.

You must add the codes if you want to be able to see those feature lines in plan view in Civil 3D. Equally important, you must use a Code Set Style for your corridor in Civil 3D that has the desired appearance for those codes of your corridor feature line.

Problem with cross-fall: Don't assign a negative value to the cross-fall variable in the field slope. If you want to capture the real input from the user and use it in your subassembly you should use a positive variable. in that way, when the user inputs negative values you'll get also the appropriate sign. As you have it right now, if the user inputs a negative value, the negative sign will make it positive creating perhaps undesired results as you were mentioning.

If you need your crossfall to be negative always, use -math.abs(Crossfall). In that way, no matter the sign the user inserts, it will be always negative.

I hope this helps. Best regards!

[KimJG7V9]

@ecfernandez Yes. Sorry, I meant feature lines. The feature lines along those points are now showing. I removed the negative sign and now looks correct! Thank you for your help! 

[ecfernandez]

Hi @KimJG7V9. Thanks for letting us know. Happy to help.

Best regards!