Class 156 problem

[gptech]

Though it looks like i may be better off skipping the Class 156 if even DTG don't seem to interested in providing a fix.

I wouldn't let it put you off, there are far more happy 156 drivers than disgruntled ones with problems. Yes, there are issues with it under certain combinations of settings/routes/scenarios/phase of the moon but nothing that can't be worked through/round.
You're unlikely to see a fix from DTG though; once again they may not be able to work on it as it isn't their model.

[ttjph]

You're unlikely to see a fix from DTG though; once again they may not be able to work on it as it isn't their model.

... although it worked fine until their core update broke it, so you could make an argument for a core fix...

[gptech]

although it worked fine until their core update broke it, so you could make an argument for a core fix...

True, and if implemented then we could discuss at even greater depth how a core fix to fix the 156 broke (again) oodles of other stuff fixed in previous core fixes......eventually coming full circle.

Is anybody getting the same problem (any of the problems) in every route they try the 156 on...or am I the only one running the odd test now and again?

[titfieldthundrbolt]

I have the exact same problem also when I go to couple to another unit the game crashes too.

[gptech]

also when I go to couple to another unit the game crashes too.

Could you expand on that a bit please?
What route, which scenario, which livery of 156 etc so we can see if we can replicate the problem---might not bring forth an instant fix but anything that could point to where things start to go base over apex has to be tried.

[Trev123]

God this thread still going.

[gptech]

Yeah Trev, it's a keeper is this one.....

[Timex]

yes, keep the thread going!
from my previous posting another fix is to uncouple the units before opening the doors- this works all the time.
.. ah, don't forget to recouple before setting off!

I've been looking at the 150, it has very similar scripting and guts.

Which came first the 150 or the 156? (TS wise!)

[Juanillo99]

I've been looking at the 150, it has very similar scripting and guts.

Which came first the 150 or the 156? (TS wise!)

First, Class 156 → April 15, 2011
After, Class 150 → February 14, 2013

[gptech]

from my previous posting another fix is to uncouple the units before opening the doors- this works all the time...................don't forget to recouple before setting off!

It wouldn't help titfieldthundrbolt though......

also when I go to couple to another unit the game crashes too.

and....is doing something so un-prototypical and *wrong* really a 'fix'?

I've been looking at the 150, it has very similar scripting and guts.

Yes. you're right---the door interlock section would seem to be exactly the same. I copied and renamed the Class150EngineScript.lua to Class156EngineScript.lua with the same results as using the original. This was on the Port Road scenario that I found to be problematical when porting it from the free route to the full DLC version so can't be taken as conclusive proof that the idea doesn't work. Could somebody else have a wee play with this and see if they get different results?

[atlasduff47]

Yes. you're right---the door interlock section would seem to be exactly the same. I copied and renamed the Class150EngineScript.lua to Class156EngineScript.lua with the same results as using the original. This was on the Port Road scenario that I found to be problematical when porting it from the free route to the full DLC version so can't be taken as conclusive proof that the idea doesn't work. Could somebody else have a wee play with this and see if they get different results?

I had a bash at this and found that on the first attempt, (Bristol-Exeter) as soon as I opened the doors to allow passengers to board crash to dump The second attempt (WHL North) I couldn't get the bloody thing to move at all, though it didn't crash when the doors were opened. I will have another look later.........

[atlasduff47]

Well, I definitely get different results.......copied and renamed the Class150EngineScript to Class156EngineScript and found that I got the aws warning before moving the reverser and wasn't able to get the thing to move at all....swapped back to original Class156EngineScript and move into Penistone and opened the doors succesfully, passengers loaded and off I went...arrived at Wortley pressed 'T' and got the message 'There is no Disk inserted - Please insert Railworks disk into Drive X' at which point I pressed cancel and got a crash to dump.

It is a shame, as I prefer it to the 158, oh well back to the one and only original sprinter (150) then

[K2rover]

Had the crash to desktop on the WHL South (reworked the route with RETB signalling). This was with the Saltire and First Scot Rail liveries coupled together into a four car! In the end I just had to make a mental note not to open the doors at any station along the route and then I got the whole length of it without a crash.....cue some very annoyed passengers at Corrour and Rannoch Stations

"Sorry Sir, if I open the doors the world we currently are standing in will end and we'll get a crash to desktop. I've asked the controller to diagram a 158 on the next service in 4 hours so that might be better! The alternative is to climb through the driver's window which I've opened!"

[gptech]

Is that a publicly available scenario or a creation of your own? It'd be useful if somebody/somebodies could see if their copy of the units causes the issue too.
In all honesty my gut feeling is that there's too much going on which all can't be attributed to the 156 itself---sure, it may be part of the problem but not necessarily all of the problem. As we're most unlikely to see an *official* fix the more we can do for ourselves, the better.

[K2rover]

Hi gptech.

It was just a free roam scenario. I also got a crash to desktop when I tried to put a Mk3 sleeper train in the platform at Fort William. That seemed to be an 'out of memory' problem.