Train Simulator Classic

Train Simulator Classic

(p) Presflos for Long Meg
7 Comments
moonraker65 Feb 20 @ 7:04am 
Made a change to the Class 37 parcels service. Don't think Standard vans were used for parcels that late. Maybe you were thinking of the former fish vans coded SPV. Anyway I swapped them for GUVs from the BRB 2 pack and IHH CCT's which seemed more appropriate. Very nice scenario
greendragon32  [author] Feb 8, 2019 @ 3:14am 
Thanks for the feedback Brian. The spurious speed restrictions only seem to appear on freight services; passenger ones show the higher speed limits throughout.
brian62 Feb 7, 2019 @ 4:10pm 
a very good trip, Ai and signals all ok. in 32bit no probs [except the 35 mph as previously noted,
[19 all before ribblehead tunnel, in the tunnel a 45 mph line speed ] in garsdale tunnel line
speed is 60 mph. on approach to long meg siding no 15 mph signs, either on 2D map or trackside. however this is still a very good trip on a good route. many thanks.............
greendragon32  [author] Feb 3, 2019 @ 3:27pm 
Many thanks for the info deargdoom. I think this may be partly down to my setup which includes an older PC for developing scenarios - also I have removed a lot of reskins from my S & C folder which has helped. Good to know that it is not the route that is the cause.
deargdoom Feb 3, 2019 @ 1:15pm 
Just a quick note as I haven't had the time to run the whole scenario yet, but no apparent problems in 64 bit, and none with the few other (non-Workshop) scenarios I have for the route, one of which uses the AP Class 40 and always used to crash in 32 bit. I also tried a short QD starting from Carlisle, and again no problems.
greendragon32  [author] Feb 3, 2019 @ 2:36am 
Thanks for that Chris. I can get the route to run in 64-bit but can't go anywhere near Carlisle in either mode without an Access Violation crash. Also the 35 mph sections to Ribblehead only seem to affect freight services.
chris5012 Feb 3, 2019 @ 1:03am 
Very good scenario, everything worked perfectly. I was unable to play it in 64bit (Access Violation error message) but it played perfectly in 32bit mode. I don't think that it is a problem specifically with the scenario as the route itself won't play in 64bit.