I'm posting this question in the general section rather than the TS12010-specific forum because I suspect the problem and answers apply across most of the Trainz versions.
I took the laptop along to the model railway club night to give them a demo of the line I have been modelling. At home I work on the laptop with it hooked up to a TV giving me a 1920 x 1200 display. At the club, their giant TV turned out to only be 1300x768, so I tweaked the display width and height in the options file and ran the route. In driver I was getting a lot of freeze moments, up to 30 seconds duration, during which I had no keyboard control, no visual updates, just the sounds continuing. I am used to these freezes whilst building in Surveyor at home, but don't usually notice them in Driver. I assume they're autosaves by Surveyor.
Was the reduced display size somehow responsible for the freezing? They seemed to occur when I swung the cab or follow camera around, which made me suspect this was a draw-distance issue?
Are there any things I can do to reduce freezing to an absolute minimum? I was hoping to have a large screen display up at their next exhibition and run the route, but I don't think it would meet expectations if it had as many freezes as I got that evening.
I had run the sessions at home before setting out, so I was hoping the cache files would have already had the route in. I am now wondering if changing the display settings had somehow caused those cache files to become invalid and if I had persevered at the club I would eventually have got smooth running.
Spec-wise, by the way, it's a Medion Erazor X6811 laptop which works very well at home, so I don't see this as a machine-not-up-to-it issue, although it could also have been a graphics problem caused by running at a non-native resolution.
I took the laptop along to the model railway club night to give them a demo of the line I have been modelling. At home I work on the laptop with it hooked up to a TV giving me a 1920 x 1200 display. At the club, their giant TV turned out to only be 1300x768, so I tweaked the display width and height in the options file and ran the route. In driver I was getting a lot of freeze moments, up to 30 seconds duration, during which I had no keyboard control, no visual updates, just the sounds continuing. I am used to these freezes whilst building in Surveyor at home, but don't usually notice them in Driver. I assume they're autosaves by Surveyor.
Was the reduced display size somehow responsible for the freezing? They seemed to occur when I swung the cab or follow camera around, which made me suspect this was a draw-distance issue?
Are there any things I can do to reduce freezing to an absolute minimum? I was hoping to have a large screen display up at their next exhibition and run the route, but I don't think it would meet expectations if it had as many freezes as I got that evening.
I had run the sessions at home before setting out, so I was hoping the cache files would have already had the route in. I am now wondering if changing the display settings had somehow caused those cache files to become invalid and if I had persevered at the club I would eventually have got smooth running.
Spec-wise, by the way, it's a Medion Erazor X6811 laptop which works very well at home, so I don't see this as a machine-not-up-to-it issue, although it could also have been a graphics problem caused by running at a non-native resolution.