Currently, the way the trains folder is set up is rather cumbersome, and in some cases, can take up a lot of disk space, for example if you have multiple setups of the same train
A better way of reading these files is having its own config folder and its resources moved to its proper locations:
- Train (using R-16 as an example)
- Configs (Train Folder > Config > R-16)
- ats.cfg
- extensions.cfg
- panel2.cfg (or panel.cfg)
- sound.cfg
- train.dat
- train.txt
- Plugins (Train Folder>Plugins)
- OS_ATS1.dll and other supported train/route enhancement plugins
- Textures (Train Folder > Textures > R-16)
- All supported image file types
- Models (Train Folder > Models > R-16)
- .b3d, .csv, .x, .animated files
- Sound (Train Folder > Sounds > R-16)
- All supported sound file types
This setup would allow a modular design, and easier management of train setups without consuming too much disk space, simular to how the route folders are managed.
Currently, the way the trains folder is set up is rather cumbersome, and in some cases, can take up a lot of disk space, for example if you have multiple setups of the same train
A better way of reading these files is having its own config folder and its resources moved to its proper locations:
This setup would allow a modular design, and easier management of train setups without consuming too much disk space, simular to how the route folders are managed.