As a good rule of practice (and especially when superelevation is involved) I try to avoid referencing Input Parameters that may be overridden by either superelevation or a target beyond their first reference where it is determined if they are going to be used or not and instead use the appropriate API function. For example, any point that is defined for a link that is parallel to L1 I would use L1.slope to define the slope instead of SLOPE.
I also personally try to avoid using the ApplyAOR checkboxes and the Superelevation dropdown menues because I've found them to not always work right and there is less control. Instead of like to use a superelevation formula for L1 instead of just SLOPE. This formula can end up being long if you want to look at all the potential options but if you know what superelevation variable you are limiting it to then you can also work that in:
if((UseSuperelevation=LeftInsideLane)AND((Side=Left)AND(SE.HasLeftLI)), SE.LeftLI,
if((UseSuperelevation=LeftOutsideLane)AND((Side=Left)AND(SE.HasLeftLO)), SE.LeftLO,
if((UseSuperelevation=LeftInsideShoulder)AND((Side=Left)AND(SE.HasLeftSI)), SE.LeftSI,
if((UseSuperelevation=LeftOutsideShoulder)AND((Side=Left)AND(SE.HasLeftSO)), SE.LeftSO,
if((UseSuperelevation=RightInsideLane)AND((Side=Right)AND(SE.HasRightLI)), SE.RightLI,
if((UseSuperelevation=RightOutsideLane)AND((Side=Right)AND(SE.HasRightLO)), SE.RightLO,
if((UseSuperelevation=RightInsideShoulder)AND((Side=Right)AND(SE.HasRightSI)), SE.RightSI,
if((UseSuperelevation=RightOutsideShoulder)AND((Side=Right)AND(SE.HasRightSO)), SE.RightSO,
CType(SLOPE,Double)))))))))
Now I'm unclear from your original post if you are using only one superelevation and wanting that slope of L1 to be the same in L10 in which case you can use the L1.slope that I referenced above for defining P9 or if you are wanting the superelevation of the lane (L1) to be different than the superelevation of the shoulder (L10) if that is the case check out this post: SAC working with two different superelevation values
Now back to your original question, you are correct that you will want to define P10, P8, and P14 all as intersection points.
P10 will be a TwoPointsSlope intersection point from P6 with a slope of L10.slope and from P9 with a slope of -SLOPESHLDR.
P8 will be a TwoPointsSlope intersection point from P7 with a slope of L1.slope and from P9 with a slope of -SLOPESHLDR. (You will want to make sure you define P9 first.)
P14 will be a TwoPointsSlope intersection point from P13 with a slope of L1.slope and from P8 with a slope of -100% and check the box for "Reverse Slope 2".
For all the intersection points you will have to define the link separately as another element after it.
Kati Mercier, P.E. | LinkedIn | AutoCAD Civil 3D Certified Professional
Pronouns: She/Her
Co-author of "Mastering AutoCAD Civil 3D 2013"
AU2019 Speaker::: CES321590: Analyze and Revise Existing Subassembly Composer PKT Files for AutoCAD Civil 3D
AU2017 Speaker::: CI125544: Analyze and Devise in Subassembly Composer
AU2012 Speaker::: CI3001: Reverse Engineering with Subassembly Composer for AutoCAD Civil 3D
AU2011 Speaker::: CI4252: Create Subassemblies That Think Outside the Box With Subassembly Composer for AutoCAD® Civil 3D®