Turntables - Converting Static Ones into Working Ones?
#11
Posted 04 June 2016 - 05:24 AM
Returning to Peter's original problem:
I think that providing the ability to add route specific TrackShapes and TrackSections may be useful. The management of a unique tsection.dat has been effective, but the structure in itself is quite rigid.
So I made some tests, and I found that, unlike I thought, it is possible to use "include" files with tsection.dat after some small code changes.
So the feature allows to insert in the Routes's Openrails.dat a tsection.dat file that first includes the tsection.dat contained in the Train Simulator Global folder, and then includes some route specific TrackShapes and TrackSections. It can be also used to modify some TrackShapes and TrackSections included in the Global tsection.dat.
I attach here an example file that I tested with the USA1 route (but it could be any other route).
tsection.zip (548bytes)
Number of downloads: 1318
The first TrackSection and TrackShape is present also in the Global tsection.dat, so the effect is that the original TrackSection and TrackShape are modified; the second ones are not present, and so they are added to the lists.
I think this can solve problems like the one of Peter.
Suggestion: to be able to use these modified items with the actual MSTS RE it is necessary that these modified items are present also in the original tsection.dat file. However, when the work with the RE is terminated and route is distributed, it is sufficient to distribute the above route's specific tsection.dat.
I attach here also the modified .exe and .dll files, that must replace the ones within x.3551. They include also the last changes for the car spawner lists.
tsectionint.zip (1.11MB)
Number of downloads: 2144
I'm open for discussion about the opportunity or not to have this feature included in OR.
I think that providing the ability to add route specific TrackShapes and TrackSections may be useful. The management of a unique tsection.dat has been effective, but the structure in itself is quite rigid.
So I made some tests, and I found that, unlike I thought, it is possible to use "include" files with tsection.dat after some small code changes.
So the feature allows to insert in the Routes's Openrails.dat a tsection.dat file that first includes the tsection.dat contained in the Train Simulator Global folder, and then includes some route specific TrackShapes and TrackSections. It can be also used to modify some TrackShapes and TrackSections included in the Global tsection.dat.
I attach here an example file that I tested with the USA1 route (but it could be any other route).
tsection.zip (548bytes)
Number of downloads: 1318
The first TrackSection and TrackShape is present also in the Global tsection.dat, so the effect is that the original TrackSection and TrackShape are modified; the second ones are not present, and so they are added to the lists.
I think this can solve problems like the one of Peter.
Suggestion: to be able to use these modified items with the actual MSTS RE it is necessary that these modified items are present also in the original tsection.dat file. However, when the work with the RE is terminated and route is distributed, it is sufficient to distribute the above route's specific tsection.dat.
I attach here also the modified .exe and .dll files, that must replace the ones within x.3551. They include also the last changes for the car spawner lists.
tsectionint.zip (1.11MB)
Number of downloads: 2144
I'm open for discussion about the opportunity or not to have this feature included in OR.
#12
Posted 06 June 2016 - 12:03 PM
Csantucci, on 04 June 2016 - 05:24 AM, said:
So I made some tests, and I found that, unlike I thought, it is possible to use "include" files with tsection.dat after some small code changes.
I'd like to know what kinds of changes these are, as it is a complex area of code already and don't want to make things any worse or limit what we can do in the future.
#13
Posted 06 June 2016 - 12:38 PM
#14
Posted 21 June 2016 - 01:27 PM
Csantucci, on 06 June 2016 - 12:38 PM, said:
Thanks, that's pretty simple - good work! :)
Please feel free to commit the code if you think the normal rules are met (particularly, no objections from the community).
And sorry about the time to reply, I've had very little free time recently but promise to get to everything eventually.
#15
Posted 23 June 2016 - 04:17 AM
A blueprint has been created here https://blueprints.l...or-tsection-dat .
#16
Posted 30 June 2016 - 05:30 AM
James, could you pls. approve the blueprint so that I can commit?
#17
Posted 07 July 2016 - 12:36 PM
#19
Posted 12 July 2016 - 03:07 AM
Hello, has anyone yet made replacement models for the UKFS turntables? I`m thinking of making a new model that will "drop in" to substitute the original UKFS shape. It looks as if the existing UKFS TT hierarchy is unsuitable for modification, and so new models might be the best bet.
Is this the way forward for UKFS?
Rick
Is this the way forward for UKFS?
Rick
#20
Posted 12 July 2016 - 03:18 AM
Far as I know, none have been made yet. I think Tim Booth has been approached with a view to him remaking them, but not heard anything definite on that so far. There is definitely a need for working turntables to match UKFS though.