CSUR direct connect fails when road sizes do not match

[kianzarrin]

possible Solutions:

• use harmony to create exceptions for CSUR roads so that smaller roads get priority. (render the directly connect node of the smaller road)
• use different connect groups for different road sizes. This way roads can have different DC node depending on the target road size.
• Continues Junction median should handle this issue: if DC node is for median (connect group is train and netAI is RoadBaseAI) then stretch the DC texture of the smaller road to match the size of the bigger road.

[kianzarrin]

Even when the difference is 1 there is some problem.

[kianzarrin]

Is CSUR even intended to work in such circumstances?

[victoriacity]

The game will spawn the direct connect node of the road with a larger half width if both roads have node available. The first solution would be the most tractable.
The second solution requires each road having its unique connect group, which greatly outnumbers what the game has provided, so it requires patching the connect group mechanics.
The third solution might result in inconsistency in lane counts, say 3 lanes become 4 lanes abruptly instead of opening the leftmost or rightmost lane.

Direct connect nodes in CSUR are designed to work with junction medians. For transition between different roads although they work in some cases they aren't optimized for such. The best example is connecting 6DR to 6DR4, where the direct connect node doesn't even connect the 3 lanes to each other.