Multicross Intersection (4 lanes, 14-cars)

This blueprint book contains a collection of prints that can be used to build a multicross intersection.

The multicross intersection is one of the most high-throughput junction designs available. (See Aaargha's four-way junction testing thread) To provide this throughput, it takes considerable size and resources.

This implementation is based on the multicross design by Tallinu (see original blueprint collection), with buffers scaled up for 14 cars (locomotives + all rolling stock), and two lanes of travel in each direction. This size makes it particularly amenable for trains built in the 3-8-3 convention. The junction uses the right-hand-drive convention.

Construction

This can be thought of as "one" blueprint, but due to its physical size, it is split into three sections which must each be applied adjacent to one another. The blueprints are numbered "1", "2", and "3"; the #1 blueprint goes in the center of the interchange, and #2 and #3 build outward from there. There are substantial overlaps between the three blueprints to ensure proper alignment of application.

The three blueprints together create one "leg" of the interchange. To construct a complete cross, build one leg, then rotate the blueprints and start from the center again to build another leg; repeat four times total. Collectively this requires several thousand rails, although due to the blueprint overlaps, it is less than the strict sum of the requirements listed for each blueprint segment.

If a T-junction is desired, simply apply the blueprint collection on only three sides; they should all function without the fourth side present.

Linking to standard track

The input rails to this interchange are spaced six tiles apart (3 rail tiles). My standard rails are 2 rail tiles apart each, which provides a more dense rail footprint. A #4 blueprint is also provided with a 3-to-2 width adapter that will mate to the narrower gauge rail system. If your rails are 3 rail tiles apart to begin with, the #4 blueprint is not required.