Class 156 problem

[shaun123]

Sorry for the bump, I had this problem for the first time today since having the Class 156 since it came out.

My own scenario route Liverpool-Manchester and it was the Northern reskin off DPSimulation site, only happened with AI traffic.

If I took out loading passengers and put 'stop at' instead would this resolve the problem?

[ttjph]

Thought I'd test this again following Gary's nudge in another thread.

First checked the numbers, and 'Sprinting the EMCL' does have duplicate numbers - the player consist is vehicles 156402+156426, but you immediately couple to 156416+156416.

Tried it anyway, in TS2016 v53.9b, running with a windowed configuration as that's what I left it on, and lo and behold the passengers loaded and I drove away.

Then I switched configs back to full screen, and it froze on opening the doors. Ho hum.

Renumbered one of the 156416s to 156406 (via RW Tools), tried again, and no crash! I'll start driving 156 scenarios again over the next while and post some more updates in due course.

Note that I'm on a different graphics card (580 vs 260) and newer Nvidia drivers compared to when I tested way back on the first page.

[156478]

I never had this problem until right just now, and have had the class 156 in Rail Simulator since 2011 and its ran perfectly on two underpowered laptops and my current decent spec desktop.

It wasn't until I installed the Armstrong Powerhouse Class 150/153 and 156 Pack that the problem with the Opening the doors and causing the game to crash came to happen. I tried emptying the Cache and tried different liveries, different routes and removing and creating custom quick drive combinations. Some routes as soon as you started the scenario and pressed T the game would crash, and other times you got to a few stations and then it crashed.
I removed my Class 156 from the Steam Library and readded it- which as far as I know has removed it and re-installed it. Indeed the old sounds were back on the train, thought the issue had maybe gone Tried to open the doors and bang the game crashed!

I have emailed Armstrong Powerhouse of the issue and for any advice. Either that or can we persuade them to do their own version of a Class 156!

[chrisreb]

Interesting - keep us posted - thanks

[J1o2h3n4]

Hi all,
sorry I didn't take up following Gary's nudge in another thread. , Gary's offer. As in all honesty I had gone as far as my limited ability's would take me with this issue.
Having said that, will watch this space with avid interest, in the hope that an eventual resolution can be found. Also my fervent hope is that the problem solution, wont be too complicated for the ones like me with limited skills to use.

Good luck with this.

Regards JohnT

[sdark2]

Just to chime in here. I have a fix for this. When I get a chance to upload it, I'll share it here.

Effectively the problem is related to the door entry zones specified in the Cargo Def section of the Engine BPs. This tells the software where the passengers should head to when you open the doors. On the Class 156, they're overlapping at one end of the vehicles. Overlapping zones will confuse the passenger pathing and cause the software to lock up. Below is what you should look for and how to fix it.

Original Broken Version

Code: Select all

<cPassengerDoorwayDef d:id="77739600">
	<DoorSide d:type="cDeltaString">LHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F5BF" d:precision="string">-1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A942240" d:precision="string">9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>
<cPassengerDoorwayDef d:id="77743312">
	<DoorSide d:type="cDeltaString">LHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F5BF" d:precision="string">-1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A9422C0" d:precision="string">9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>
<cPassengerDoorwayDef d:id="77720400">
	<DoorSide d:type="cDeltaString">RHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F53F" d:precision="string">1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A942240" d:precision="string">9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>
<cPassengerDoorwayDef d:id="77742032">
	<DoorSide d:type="cDeltaString">RHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F53F" d:precision="string">1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A9422C0" d:precision="string">9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>

New Fixed Version

Code: Select all

<cPassengerDoorwayDef d:id="77739600">
	<DoorSide d:type="cDeltaString">LHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F5BF" d:precision="string">-1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A942240" d:precision="string">9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>
<cPassengerDoorwayDef d:id="77743312">
	<DoorSide d:type="cDeltaString">LHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F5BF" d:precision="string">-1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A9422C0" d:precision="string">-9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>
<cPassengerDoorwayDef d:id="77720400">
	<DoorSide d:type="cDeltaString">RHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F53F" d:precision="string">1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A942240" d:precision="string">9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>
<cPassengerDoorwayDef d:id="77742032">
	<DoorSide d:type="cDeltaString">RHS</DoorSide>
	<OffsetX d:type="sFloat32" d:alt_encoding="000000E0A370F53F" d:precision="string">1.34</OffsetX>
	<OffsetZ d:type="sFloat32" d:alt_encoding="000000E07A9422C0" d:precision="string">-9.29</OffsetZ>
	<RatePerSecond d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</RatePerSecond>
</cPassengerDoorwayDef>

[gptech]

Lovely Steve..... that should see one issue 'put to bed', it would be interesting to see if all the .bin files for the various liveries have this *error* (for want of a better word) if only to find out if that explains why some versions have worked OK.

[J1o2h3n4]

Hi all,
I have 26 variations of this model_ collected over the years for numerous scenarios.
So before I start to try this out, will somebody confirm this is what I must do for every variation:-
Open up the Asset folder Oovee and then seek out every file in the variations present, starting Class156_............bin.
Then using RWTools compare the contents with the text as above - and then change as required, gonna be a long day.

But if this is the long awaited solution, then take a bow SDark2.

Regards Johnt

[sdark2]

Lovely Steve..... that should see one issue 'put to bed', it would be interesting to see if all the .bin files for the various liveries have this *error* (for want of a better word) if only to find out if that explains why some versions have worked OK.

Seems they are, none of the versions I have here worked, they all crashed the sim.

I've passed the fix over to be implemented officially and I would imagine it would be shunted to everyone soon enough but if you can't wait for the official version, this will get you up and running.

In my fixed version, I've also added in non-driver versions of each livery, appropriate Quick Drive consists and meta data so they show up in the loco collection properly. Note that this only affects the default included liveries and no other third-party liveries are fixed.

All you need to do to install this is to make a backup copy of your existing BRClass156Pack01 folder and then copy the contents of the zip to your assets folder, overwriting the appropriate files. Make sure you remove the Blueprints.pak file before you attempt to run TS. Note that if you have AP's soundpack installed, the Class 156 will be broken again and you'll need to do a manual patch as above to correct the issue or wait for AP to push out a fix (they've been made aware and are working on patching themselves).

You can download it by clicking the link below:

https://dl.dropboxusercontent.com/u/878 ... 56_Fix.zip

[sdark2]

Hi all,
I have 26 variations of this model_ collected over the years for numerous scenarios.
So before I start to try this out, will somebody confirm this is what I must do for every variation:-
Open up the Asset folder Oovee and then seek out every file in the variations present, starting Class156_............bin.
Then using RWTools compare the contents with the text as above - and then change as required, gonna be a long day.

But if this is the long awaited solution, then take a bow SDark2.

Regards Johnt

Easy way to validate > Backup your current folder, then use my patch, check to see if it works by using one of the default paints (they should show up in Quick Drive). If it works, restore your backup and patch manually.

[J1o2h3n4]

Hi,
possibly (probably) my old eyes, but I cannot see which lines differ between new and old in your example above.

Whereas in my Railworks Tools display I see this line "<RatePerSecond d:type="sFloat32" d:alt_encoding="000000000000E03F" d:precision="string">0.5</RatePerSecond>" as being different to your versions above.

Regards Johnt

[tluamiani1]

That's great news. I'll try it out as soon as I get home tonight!

Cheers
Iain

[sdark2]

Hi,
possibly (probably) my old eyes, but I cannot see which lines differ between new and old in your example above.

Whereas in my Railworks Tools display I see this line "<RatePerSecond d:type="sFloat32" d:alt_encoding="000000000000E03F" d:precision="string">0.5</RatePerSecond>" as being different to your versions above.

Regards Johnt

The values that are different are the Z Offset values, if you look at the polarity of the values, you'll see what's different - like I said in my initial post, there were overlapping doorway definitions. The only way to remove those is to affect the Offsets.

The RatePerSecond value is the rate at which passengers are loaded and are effectively irrelevant to the fix.

[J1o2h3n4]

Thanks, note need new glasses.

Regards JohnT

[amtrake8a]

Armstrong Powerhouse updated their Class 150 sound pack to fix this issue with the Class 156. Apparently DTG will release a patch that will also fix this problem.