Class 156 problem

[stevee630]

Yes i've downloaded the patch/fix by sdark2 on this thread, and applied it. I've just re subscribed to the "Getting the workers to Manchester" scenario and run it all the way from Warrington to Oxford Rd stopping at all stations, AND having a gander outside the train from all angles and it all went well! I only have the liveries that came with the stock pack though. But Can't see me wanting anymore to be honest. But anyway, nice one sdark2!
Stephen.

[gptech]

OK...important waffle first....

Every item of rolling stock ever produced for the game depends on a .bin file to make it display, and make it work.
These .bin files reference other files such as the model shape itself (.GeopcDx files) animations for doors/wipers/fans etc (.ban files) simulation files (.lua and/or .out files) so as you can appreciate these are pretty important files.
Luckily we can edit these files; not directly but by converting them to the .xml format, editing, and converting back to .bin---RW Tools deals with this conversion for us automatically...... see, it's getting easier even before we've started!!

So, load up RW Tools and click on the 'Files' menu in the top bar. Then 'Open TS2016 File' to open a navigable window which you'd use to find the .bin file you wish to edit.
For the default (Regional Railways) 156 it's in this folder:

..\Assets\Oovee\BRClass156Pack01\RailVehicles\Diesel\BRClass156\Default\Engine

The .bin file(s) for any reskins will be in a similar folder structure, so if you have a London Midland (for example) reskin it'll be in something along the lines of:

Assets\Oovee\BRClass156Pack01\RailVehicles\Diesel\BRClass156\London Midland\Engine

LondonMidland, London_Midland, LM are all valid folder names dependant on what the reskinner deemed the *right* name, so you see why AP can't possibly cover user created reskins.

Back to the default livery, in that folder you'll see the .bin files for the DMSL and DMS and most likely versions with 'nd' in the name, which simply denotes they don't have a driver in the cab (simple to do, the driver is just a child object called for, or rather not called for in a driverless version, in the .bin)
Choose to open the Class156_DMS_RR.bin file and RW Tools will display something that starts like this:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<cBlueprintLoader xmlns:d="http://www.kuju.com/TnT/2003/Delta" d:version="1.0">
	<Blueprint>
		<cEngineBlueprint>
			<Name d:type="cDeltaString">Class 156 DMS Regional Railways</Name>
			<BrowseInformation>
				<iRailVehicleBlueprint-cBrowseRVInformation>
					<DisplayName>
						<Localisation-cUserLocalisedString>
							<English d:type="cDeltaString">Class 156 DMS Regional Railways</English>
							<Other/>
							<Key d:type="cDeltaString"></Key>
						</Localisation-cUserLocalisedString>
					</DisplayName>
				</iRailVehicleBlueprint-cBrowseRVInformation>
			</BrowseInformation>
			<RailVehicleComponent>
				<cEngineComponentBlueprint>
					<NumberingList>
						<cCSVContainer>
							<CsvFile d:type="cDeltaString">Oovee\BRClass156Pack01\RailVehicles\Diesel\BRClass156\Default\Engine\class156_DMS_numbers</CsvFile>
						</cCSVContainer>
					</NumberingList>
					<NumberingFormat d:type="cDeltaString"></NumberingFormat>
					<Numberings d:type="sUInt32">0</Numberings>
					<FrontCouplingBlueprintID>
						<iBlueprintLibrary-cAbsoluteBlueprintID>
							<BlueprintSetID>
								<iBlueprintLibrary-cBlueprintSetID>
									<Provider d:type="cDeltaString">Oovee</Provider>
									<Product d:type="cDeltaString">BRClass156Pack01</Product>
								</iBlueprintLibrary-cBlueprintSetID>
							</BlueprintSetID>
							<BlueprintID d:type="cDeltaString">RailVehicles\Couplings\Automatic\Default\automatic_default_coupling.xml</BlueprintID>
						</iBlueprintLibrary-cAbsoluteBlueprintID>
					</FrontCouplingBlueprintID>

That looks very complicated, because it looks complicated---it's really a straight forward formatting arrangement and RW Tools has a little feature to make it look easier....

To the right of the address bar there's a button labelled "Highlight XML"...click on this and it 'colour codes' the displayed text:



If it's red, green or blue don't touch it!!...the black bits are what we can safely edit.

RW Tools has another labour saving routine in it's 'Search and Replace' menu. Click on that, with the .bin open of course, then 'Find' in the drop down box. A small window will open, the top pane is all we need to look at now so just type <cPassengerDoorwayDef d:id="77739600"> in it
Oh...that's not so easy to type is it, just copy and paste it in

Now click on the 'Find' button on the right and the view will change to the section starting with that text string, which will look like:

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>

In there are 4 instances of a 9.29 value and all you need to do is make the 2nd and 4th ones -9.29

The edit is just changing 2 values to a negative number--told you it wasn't hard

Once you've done the edit, click on the 'Files' menu again and then on 'Save TS2016 file'. This automatically saves the edit, and also creates a file with the .bak extension. This .bak file is a copy of the un-edited file, so if it all goes boobs up just delete the .bin version and rename this .bak to .bin. Of course the smart way to do it is to copy the ..\Assets\Oovee\BRClass156Pack01 folder to somewhere safe until you've edited all you need to edit.

[stevee630]

That all there is to it?
No, seriously thanks a lot for taking the time to explain that so well Gary. If i do get any reskins i will certainly be revisiting this thread. Nice one mate!
Stephen.

[hle19]

Gary (GPTECH) - thanks awfully for taking the time to explain that, it is very much appreciated.
Can't believe how easy it is. That's my first edit of a RW bin file.

Edited half of my 156 reskins, all appear to be running fine.

Next step will be editing the brakes on the 153 - just a little too weak compared to reality.

[pendolinobasher]

I would like to also add my thanks for help with this.

I have now coded all of the Wherry Lines 156s and they all work correctly now, I can happily do the 156 activities now.

[Trev123]

I have no issues with the 156.

[hle19]

I have no issues with the 156.

Some do, some don't. Already been esablished.