NG wrote:

Of course, one could also allow even more if "track classes" with submenus, etc., were introduced...

This comment was imported from FlySpray: https://bugs.openttd.org/task/5040#comment10858

Rubidium wrote:

Some "investigation" leads me to believe there are currently at least 17 types of rail (the steel part), 6 gauges, 6 different voltages, and 3 electricity delivery systems. This means that we'd need to go to 2048 rail track types to be able to properly model the real world tracks.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5040#comment10859

dandan wrote:

I would like to support this request. Of course, the "combinatorial explosion" is potentially dangerous and submenus and such might be overkill. So 16 slots may seem like a lot, but the idea is not necessarily to have all of them available at the same time. If a track set is supposed to be versatile and provide different track types for different situations, this is hard to do at the moment, except with many GRF parameters and corresponding action 7/9-skips to map different labels to the same ID.

The Japanese track set (and possibly others) already use all 16 slots. When another track set is loaded that defines just one more track type, the player will get an "attempt to use invalid ID" error.

32 seems a reasonable limit to me, possibly combined with a more meaningful error message when that limit is exceeded.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5040#comment10992

Snail_ wrote:

I agree with Daniel. It's true that maths tell us that the number of theoretically available track types would be huge, but in reality there would never be a need of hundreds (let alone thousands) of tracks: most of the voltages would be available for standard gauge tracks only, and, most of the times, only in combination with specific axle weights (or max speeds).

So, whereas tracktype explosion is not something a serious trainset should be concerned about, having 32 tracktypes available would greatly help a set to be more granular and realistic. The set I'm working on would significantly benefit from this.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5040#comment11013

Alberth closed the ticket.

Reason for closing: Won't implement

While there are several hundreds of different track sub-system combinations, it doesn't make a lot of sense to have more than a handful available in any game.
Most players are already bothered by more than 1 track-type.
Use parameters for your newgrf to select which ones you want to play with, from your thousands types.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5040