Subassembly Composer 2015 - Intersection points

[Anonymous]

Using subassembly composer 2015.  I want my aggregate base to tie up to the bottom of shoulder.  I'm trying to use intersection points to do this.  The problem is the link I'm trying to intersect with has "ApplyAOR" checked because it is necessary.  I can't get the intersection to work when there is superelevation applied. If you look at the attached example, I want P12 to land directly on L8.  

Thanks

[KMercier_C3D · Accepted solution]

Why do you feel the "ApplyAOR" checkmark is necessary? (Note that if you are using ApplyAOR you should probably have the approximate Superelevations checked on the superelevation tab to be Enabled in Preview.)

P12 isn't showing up on your L8 link because it (for some reason) appears to be calculating the intersection based on the targets instead of the superelevation. I'll admit that I've never used ApplyAOR on any of my subassemblies but instead check for the slope of the toplink manually using a formula. 

[Anonymous]

I've run into similar issues. Because of a new project based on C3D 2015 I am trying to convert or rebuild railway custom subassemblies I created and successfully used in SC/ C3D 2013.

My original SC/ C3D 2013 subassemblies use Define variable to calculate superelevation angle and use Angle and distance for all links and points (from Cant class API functions Cant.LeftRailDeltaElevation and Cant.RightRailDeltaElevation vertical difference).

A corridor opened in C3D2013 shows superelevation and the rest fine, but when I open the same file in C3D 2015 and rebuild corridor using the same SC 2013 or version saved to SC 2015 the corridor is not showing in parts where there are curves (where superelevation should be applied). 

My assumption is after there was added new ApplyAOR functionality and cant preview to SC 2015 for all links Civil3D 2015 corridor doesn't superelavate any link unless it has the AOR previously checked in. So I tried to rebuild subassembly using AOR checks - all works fine if all links are superelevated but I wasn't able to correctly connect non superelevated link with superelevated (with checked AOR), specifically I am using Intersection: TwoPointsSlope 

I found even Rail_Cant_Example.pkt  from Sample Autodesk subassemblies have the same issue - it either superelevate ballast slope links L44 and L45 when AOR is checked (correctly ballast slope should be constant) or changes ballast shoulder width when AOR is unchecked (you can see links L40 and L43 should be constant in this case 0.5m no matter of superelevation is applied or not).

Has anybody figured this out? Is there a way in C3D 2015 to disable AOR functionality and use the C3D 2013 old fashion way to define superelevated points/ links using angle variable (and have all links with AOR unchecked)? I've tried to add predefined Input/Output parametres and turn SupportAOR value to unsupported but it had no effect to my corridor.

Much appreciated,

Lukas

[Anonymous]

Thank you Lukas.  I am very new to subassembly composer but have a corridor modeling (Geopak) background so I have a good idea of how I want things to work.  

The ApplyAOR check box is a bit perplexing.  I'm trying to follow the guidance given by Kati.  The problem is the slope of the bottom of the shoulder won't match the top in a superelevated section unless ApplyAOR is checked, even if I use a formula to define the slope.  So I am still unable get my intersection point to land where it should.

Thanks again 

[Anonymous]

It looks like there should be ApplyAOR check box for intersection points too, but unfortunatelly is not the case at least in C3D 2015

I think Kati tried to point you to set variables using SE class.

http://knowledge.autodesk.com/support/autocad-civil-3d/learn-explore/caas/CloudHelp/cloudhelp/2016/E...

Not sure how the above works for road design but at least for rail the values calculated from Cant class are not respected in corridor and links in C3D 2015 are controlled by the AOR switch setting which works weird in SC. In SC it allows you only to apply AOR to links, not to points and auxiliary points or point intersection (all I could do in 2013 version without an issue).

Anybody experiencing the same?

Lukas   

[Anonymous]

After working with my subassembly more, I was finally able to get it to work.  I ended up turning off ApplyAOR on all links and it's intersecting exactly where I want it.  At some point I went down the path of believing superelevation wouldn't work unless ApplyAOR was checked but that appears to not be the case.

Thanks!

[harold_strang]

It looks like the AOR switch doesn't work properly, which wouldn't be so bad if we could just turn it off and calculate the Y values and slopes ourselves in SC, but it seems that the Cant class properties no longer work in 2015.  Cant.LeftRailDeltaElevation and Cant.RightRailDeltaElevation appear to return zero all the time (as near as I can figure), so it's very difficult to create any usable rail subassemblies at all which require Cant.   😞    Does anyone know if this is fixed in 2016?