Xtracks, dbtracks, ustracks, etc. I'm so confused!!

[spengr]

Hey everybody. I'm new to TRSE and trying to get started. What are the differences and advantages of the different track profiles?

Thanks
Mike

[eric]

Here's an overview of the systems you mentioned plus two you didn't.

---

DBTracks and USTracks are upgraded track shapes you can retrofit into an existing route built using XTracks. They have highly detailed shapes including frogs, guards and some turnouts have working switchstands. Using these shapes requires some advanced understanding of route building to execute the replacement, usually done after a route is completed. It is closed source and no longer supported. It is partially supported in TSRE.

Xtracks is the original track systems developed in 2002-2007 to support new route development. It's the most complete in terms of track sections offered, but also the least visually accurate. Most turnout pieces lack guards or frogs, the track spacing (5m) is too wide for most railroads, and the rail profile is a square box and ballast is flat. It is closed source with limited support. It is supported in TSRE.

MTracks is an extension of XTracks, but with more realistic track spacing (4m) and curve geometry. Most turnouts have guards and frogs. The rail profile is a square box and ballast is flat. It is closed source and no longer supported. It is supported in TSRE.

ATracks is a 1:1 replacement for XTracks and MTracks, with is a more visually accurate rail profile and sloped ballast profile, with guards and frogs at turnouts. It uses open source scripts and Blender for generating new pieces. It is supported in TSRE.

Scalerail is a standalone system also developed in 2005-2007. It has a more visually accurate rail profile and sloped ballast, with guards and frogs at turnouts, and many have working switchstands. It is closed source with limited support. It is supported in TSRE.

[eric]

I wanted the overview separate from my opinions.

As a route builder, I cannot stand the square flat track from XTracks and prefer 4m track spacing as my modeling is older routes.

Scalerail is what I've used the most, and still use.

As a developer, I produced and support ATracks.

Visually, there is a version of ATracks compatible with USTracks, but without the hassle of executing a shape substitution later in route development.

If I were starting on a new project I would probably use ATracks simply because its open source.