Driver_Col
Active member
I need some opinions please re the ramifications of merging Routes because I have successfully joined my Badger-Tanglefoot and Tristyn Routes so can have substantial GWR/Western Region operations as well as substantial LMS/Midland Region operations with a rather nice section of shared trackwork. In the future,I see no major problem to now add my Billinton Route to the Tristyn side (giving an SR/Southern Region link) as well as my (adapted) Rosworth Vale Route to the Badger-Tanglefoot side (giving an LNER/Eastern Region link).
Theoretically it sounds like my perfect layout as I can cover everything however, there is the computer to consider .. and this is where your thoughts would be appreciated. To complete just the initial merger of Tristyn and Badger-Tanglefoot and overhaul it for TRS19 was/is a lot of work. That is obviously multiplied by adding the other two Regions. i.e. to do everything will be a huge investment of time. The question is ... can it be handled by a reasonable PC?
My understanding (perhaps rather simplistic), is that a computer (when running Trainz) is working primarily to produce the onscreen imaging, with other resources processing anything else within the preset visual distance. i.e. If my pc is set to process up to 8000m, is it doing anything at all for assets outside that range? Putting that in more direct terms, if my pc can process comfortably my Routes on their current settings, is there any limitation as to how big the Route can grow?
I am pretty sure that I am missing some key knowledge .... which is where you "guys" come in! Thoughts? Regards to all. Colin.
Theoretically it sounds like my perfect layout as I can cover everything however, there is the computer to consider .. and this is where your thoughts would be appreciated. To complete just the initial merger of Tristyn and Badger-Tanglefoot and overhaul it for TRS19 was/is a lot of work. That is obviously multiplied by adding the other two Regions. i.e. to do everything will be a huge investment of time. The question is ... can it be handled by a reasonable PC?
My understanding (perhaps rather simplistic), is that a computer (when running Trainz) is working primarily to produce the onscreen imaging, with other resources processing anything else within the preset visual distance. i.e. If my pc is set to process up to 8000m, is it doing anything at all for assets outside that range? Putting that in more direct terms, if my pc can process comfortably my Routes on their current settings, is there any limitation as to how big the Route can grow?
I am pretty sure that I am missing some key knowledge .... which is where you "guys" come in! Thoughts? Regards to all. Colin.