Atomic Systems

rededge wrote:I've just run the same above mentioned scenario with no problems. I do have the AP pack installed

That's good news; means that the problem isn't likely to be because of any editing to the default version. Yes, the lighting did throw up some surprises from the outset. initially it was gloomy in Darlington station then somebody turned the searchlights on!

rededge wrote:

gptech wrote:just ran 'Sprinting the ECMl' with no issues---very strange goings on indeed.
How many having bother have the AP sound enhancement installed?---let's see if there's any common element in this.

I've just run the same above mentioned scenario with no problems. I do have the AP pack installed- Gary, did you notice the strange weather transformation on this? Went from nearly dusk to *POW!* quite light again...
Ran OK though.

I've just tried it and got as far as Thirsk about 2 seconds after opening the doors - crash to desktop! I don't have the AP pack installed just the base 156 with no reskins. I have noticed more crashes generally since the update, especially in the editor.

No soundpack, but I've just realised that I had a particle mod installed (and not yet replaced on my clean 49.4 copy).

No immediate crash in 50.5 if I overwrite the Particles folder from a backup without the mod - also no crash if I copy the mod into 49.4, but strangely no smoke either. Mod was untested since installing.

There's definitely something odd going on with either the unit or the Sprinting the ECML scenario. I've got no mods or soundpacks installed for the 156 and I've just tried that scenario a few times. The first two times the sim crashed as soon as the doors started to open. The third time I found that I'd got the option to resume, must have been a save in an earlier version of TS as I'd not played that scenario for ages, and I tried that and the scenario loaded and ran fine with me somewhere approaching York. At that point I quit the scenario and selected Restart from the Pause menu, after that restart I was able to couple the units at Darlington, open the doors and then drive away.

FWIW I tried the same Regional Railways set on the GWML 'Where should they go?' standard scenario that came with the pack and had no problems with door opening crashing the game.

Andy L

Just tried to run 'Sprinting the ECML and got as far as second stop, Thirsk, after opening the doors, a couple of seconds later scenario crashed! No mods or sound packs for this unit

I have Ovees 156 but the only scenarios I have for it are on West Highland Line Extension driving the First Scotrail. I drove a 2 car one for a couple of miles and when stopping at a station only the second car doors opened. Yes I was lined up correctly at the platform.

Trev123 wrote:I have Ovees 156 but the only scenarios I have for it are on West Highland Line Extension driving the First Scotrail. I drove a 2 car one for a couple of miles and when stopping at a station only the second car doors opened. Yes I was lined up correctly at the platform.

That's a problem with the carriage numbers, if you check in the editor you will find they are both numbered the same, changing one of them (might break the scenario but) will make both carriage doors open

Dave

Wow, DTG support are stepping up their game - kudos!

Thank you for bringing this to our attention, I replicated the issue here in the office just to be sure and you're
absolutely right that its causing crashes. I'll pass this information along to the developers and hopefully we can
get a fix out in the not too distant future. In the meantime you can press Ctrl+Tab to get past this crash if you're
desperate to play through any of the 156 scenarios.

Sprinting the ECML I got as far as pushing the T key after coupling up to the other unit.

ttjph wrote:Wow, DTG support are stepping up their game - kudos!

Thank you for bringing this to our attention, I replicated the issue here in the office just to be sure and you're
absolutely right that its causing crashes. I'll pass this information along to the developers and hopefully we can
get a fix out in the not too distant future. In the meantime you can press Ctrl+Tab to get past this crash if you're
desperate to play through any of the 156 scenarios.

Whilst that's definitely a welcome change from the old style 'no response, at best an automated reply suggesting verifying the game' style of support we've known it doesn't give me much to cheer about. Has anybody heard from the developer of the class 156 in the past 12 months?


We've looked at the AP sounds being a factor; disproven.
The exhaust fix from the library has been put under the spotlight; once again disproven, so we have to look further.

Those with a working TS2014 install of the 156:

Cut the copy of the 156 out of the game to somewhere safe and paste in a copy of the one that is known to work....lets see if that makes a difference, for all we know a file or two may have been 'lost' during the upgrade from TS2014 to 2015.

Hi all,
I have already copied over the 2014 class 156 to 2015 and it made no difference. I have also changed over the scenario from 2014 to 2015 that made no difference. I have even sprayed the doors with WD40 that didn't work either. I have one more trick that I want to try, hopefully tomorrow if it works I will post it on the forum, if it doesn't work I will sit in the chair all day and sulk.
Regards,
Pete.

Sorry for the 'bump' of an old post, but I recently ran into this problem myself and was wondering if there was any further progress with this issue. It is ruining the simulator for me at the moment.

chris

Just happened to me as well, when the 156 was being used as AI.

Don't think it started happening immediately after the update to TS2015, the 156 for me has been working fine long after this took place, up until now of course,

Do both vehicles have the same number, ie 156443?

If so, try other numbers and see if that works?

Just had the same using a Scotrail (old style) reskin.