As with other vanilla road-based assets, the connection logic used in MSE is based on vanilla roads and does not require a mod, but the use of mods such as Node Controller, Network Anarchy (formerly Fine Road Tool, etc.), and Network Tiling (now integrated as Network Anarchy) and Network Tiling (now integrated as Network Anarchy) can help you place roads easily. You can also use other different highway assets in combination.
===
Most MSE roads have LW, LC and LE forms, which represent lane west, lane center and lane east respectively, the difference being that the emergency lane/sidewalk offset is on the outside or inside of the direction of traffic. This set of roads is compatible with both left- and right-hand traffic maps, so the left/right nomenclature may cause ambiguity, so a static map coordinate system is used for naming, i.e. +X for east.
LW: The emergency lane offset is located on the outside of the direction of traffic. (Right driving is right hand for the direction of traffic, left driving is left hand)
LC: No emergency lane, offset distance is evenly distributed on both sides of the traffic lane.
LE: Emergency lane/curb setback is located on the inside of the direction of traffic. (Right driving is right-handed in the direction of traffic, left driving is left-handed)
===
Occasions for using different forms.
Usually, the general LW and LC are enough, combining LW and LE can realize the conversion of the driving lane from the inner side of the road to the outer in some occasions, which will appear on some ramps or compact inter-city elevated roads. See [Figure 1] for the method and occasions of use.
(f.1)===
Occasions for using different road modes.
MSE roads contain ground, elevated, bridge and tunnel modes
In case of no other requirements, the connection between the different modes is recommended to use the nodes of the middle mode. Specifically, nodes connected to the bridge mode should use middle mode nodes [Figure 2], and nodes connected to the tunnel mode should have a offset distance of 0 [Figure 3] to avoid unnatural connections.
(f.2)(f.3)===
Conversion of ground mode to elevated mode.
The ground mode of MSE does not flatten the terrain, so you can have this without affecting the terrain elevation: [Figure 4]. Some of the terrain fine-tuning can be done with the terrain brush, in fact, it is more controllable to level the terrain this way.
(f.4)If you need to build a sunken road, you need to manually place retaining walls on both sides of the road [Figure 5.1], and if it is a two-way road you may need some network that specializes in cutting the terrain (e.g. Clipping Network, by TOKACHI269) to remove the uncut ground between the two roads [Figure 5.2]
(f.5.1))(f.5.2)===
If you need to build ramps in bridge mode, it is recommended to have at least one section of elevated mode buffer at each of the nodes where the ramps split off. [Figure 6].
(f.6)===
If evacuation stairs are not required, then setting the nodes to any mode other than middle mode will remove the evacuation stairs. [Figure 7]
(f.7)===
Example 1: Ramp exit (single node split/combined flow)
An example in the left/right hand traffic case, (drawing lines using the IMT ) is shown in [Figure 8].
The node and segment configuration is shown in [Figure 9].
Node Controller configuration is shown in [Figure 10].
(f.8)(f.9)(f.10)===
Example 2: Ramp entrance (dual node split/merge)
An example in the left /right hand traffic case, (drawing lines using the IMT ) see [Figure 11].
The node and segment configuration is shown in [Figure 12]. Note: There is a 4L segment of road in the image but it is squeezed out due to the node setting, you can make a merge section like this. (only one segment is used in the image, but you can extend the merge section with the same method.)
The Node Controller configuration at the node is shown in [Figure 13]. Note: The 4L merge segment in the figure has a separate 'shift' value.
(f.11)(f.12)(f.13)