Page 2 of 3
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 2:35 pm
by 749006
Plan B not working
The file Structure of the 365 is ..\Assets\RSC\Class365Pack02\RailVehicles\Electric\Class365\Class365
So I copied that and created a ..Assets\RSC\Class365Pack02\RailVehicles\Electric\Class365\Class323
I amended the Class365_DMOC_A.bin to be Class323_DMSO_A.bin and changed a number of references in the file.
Trying to place the vehicle on the track just ends up with a mess coloured shapes
I'm doing something wrong but I'm not sure what
Peter
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 3:14 pm
by gptech
749006 wrote:I went back to plan A using the 323 bin file and pointing at the 365 but I don't have any Cab Audio
When I switch the AWS on there is no sound
749006 wrote:I'm doing something wrong but I'm not sure what
What you're doing *wrong* is lurching from a problem to another problem--you have/had a working cab but no sound, so why reverse the good bit of that instead of just looking at where the sounds are referenced?
Add
Code: Select all
<cEntityContainerBlueprint-sChild d:id="49913">
<ChildName d:type="cDeltaString">Cab Sound</ChildName>
<BlueprintID>
<iBlueprintLibrary-cAbsoluteBlueprintID>
<BlueprintSetID>
<iBlueprintLibrary-cBlueprintSetID>
<Provider d:type="cDeltaString">RSC</Provider>
<Product d:type="cDeltaString">Class365Pack02</Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">Audio\RailVehicles\Electric\Class 365\Cab\Class 365 Cab Sound.xml</BlueprintID>
</iBlueprintLibrary-cAbsoluteBlueprintID>
</BlueprintID>
<Matrix>
<cHcRMatrix4x4>
<Element>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000402DB10240" d:precision="string">2.33651</e>
<e d:type="sFloat32" d:alt_encoding="000000004E592340" d:precision="string">9.67442</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
</Element>
</cHcRMatrix4x4>
</Matrix>
<ParentNodeName d:type="cDeltaString"></ParentNodeName>
</cEntityContainerBlueprint-sChild>
into the child objects section of the 323's .bin file to get cab sounds.
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 3:55 pm
by 749006
gptech wrote:What you're doing *wrong* is lurching from a problem to another problem--you have/had a working cab but no sound, so why reverse the good bit of that instead of just looking at where the sounds are referenced?
Add
into the child objects section of the 323's .bin file to get cab sounds.
That would only give me the internal sounds but not the external sound
Plan B worked and by doing one step at a time, as you remind me Gary
I tried to be cleaver by copying some of the 323 files in to the 365/323 folder and that went wrong
So I started again by just copying the geos and looked at the result which worked
Then I copied the 323 bogie pivot info to the 365 version and also the coupling info so the Couplings appears and the cars don't mix with each other
Like David's version I have a 323 on the outside and a 365 on the inside.
I wonder if there is a way of placing a driver in the 323 cab - one of the things that looks strange without a person at the front.
Peter
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 4:01 pm
by gptech
749006 wrote:
I wonder if there is a way of placing a driver in the 323 cab - one of the things that looks strange without a person at the front.
Child object--you'll probably have to juggle the positioning in the matrix--13th, 14th and 15th values adjust the positioning along the 3 axes.
Usually 13 = along the width
14 = along the length
15 = height from the rail
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 4:03 pm
by gptech
749006 wrote:So I started again by just copying the geos
You want to check that?...
that's the usual culprit for graphical issues due to the DRM on shape files.
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 4:05 pm
by 749006
gptech wrote:749006 wrote:
I wonder if there is a way of placing a driver in the 323 cab - one of the things that looks strange without a person at the front.
Child object--you'll probably have to juggle the positioning in the matrix--13th, 14th and 15th values adjust the positioning along the 3 axes.
Usually 13 = along the width
14 = along the length
15 = height from the rail
Thanks - I will have a go at that
Might see what the settings of the 166 are as they should be similar
gptech wrote:749006 wrote:So I started again by just copying the geos
You want to check that?...
that's the usual culprit for graphical issues due to the DRM on shape files.
I should have said I just pointed the 365/323 at the SBY_MCV 323 geos - sorry
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 4:09 pm
by gptech
749006 wrote:That would only give me the internal sounds but not the external sound.....
...by doing one step at a time
Yeah, one step at a time. So once you'd got internal sounds the next step would be to look at the external ones...….
It's worth investigating both ways of going about the job, even if it's only an academic exercise.
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 4:15 pm
by gptech
749006 wrote:Might see what the settings of the 166 are as they should be similar
The default 323 DMOS B calls for:
Code: Select all
<Provider d:type="cDeltaString">DTG</Provider>
<Product d:type="cDeltaString">BedPanLine</Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">RailVehicles\Electric\Class319\Default\Characters\319_driver.xml</BlueprintID>
Half the work's already done for you.
EDIT: Make sure you have the DTG\BedPanLine Provider/Product boxes ticked in the scenario editor for the driver to show.
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 4:26 pm
by 749006
gptech wrote:749006 wrote:Might see what the settings of the 166 are as they should be similar
The default 323 DMOS B calls for:
Code: Select all
<Provider d:type="cDeltaString">DTG</Provider>
<Product d:type="cDeltaString">BedPanLine</Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">RailVehicles\Electric\Class319\Default\Characters\319_driver.xml</BlueprintID>
Half the work's already done for you.
I had seen that and copied the info but there was no driver - until I looked in the cab and he is half way thru the bulkhead
I will tweak the numbers and see what happens
EDIT - Nothing seems to happen - I increased some of the values of the 13 & 14th lines but it did not change anything
The driver is there but in the Bulkhead
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 5:36 pm
by gptech
Make sure the DTG/BedPanLine P/P boxes are ticked, and stay ticked following a re-start, in the editor.
Changing the 13th value from -0.814413 to -3.814413 gives:
14th from 1.1 to 4.1 gives:
and 15th from 10.5 to 13.5 gives:
The 13th and 15th values relate to the distance from the centre of the model in metres with the 14th the distance from the rail, so you can fairly easily judge how much he needs shifting in each direction.
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 6:37 pm
by 749006
I'm not using the 319 driver but the default Class 365 as my 323 is a sub folder of that pack
But I'm confused about these numbers - this is what is in the Default 323DMSO
Code: Select all
<DriverPosition>
<cHcRMatrix4x4>
<Element>
<e d:type="sFloat32" d:alt_encoding="000000C0D2FFEFBF" d:precision="string">-0.999978</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="00000000EEE97A3F" d:precision="string">0.00657075</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="00000000EEE97ABF" d:precision="string">-0.00657075</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000C0D2FFEFBF" d:precision="string">-0.999978</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="00000020000FE4BF" d:precision="string">-[b]0.626831</e[/b]>
<e d:type="sFloat32" d:alt_encoding="000000009C42F93F" d:precision="string">[b]1.57876</e>[/b]
<e d:type="sFloat32" d:alt_encoding="0000008082CB2640" d:precision="string">[b]11.3975</e>[/b]
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
</Element>
</cHcRMatrix4x4>
</DriverPosition>
And I have changed the number on lines 13,14 & 15 with no effect
I just changed them all to 15 just as a trial and still no change - unlike your version he is sat in the Bulkhead
I must be doing something wrong but I don't know why it does not change
Re: Pennine Pacer 323
Posted: Mon Aug 17, 2020 9:31 pm
by gptech
I've no idea why you have
amongst those values, but you're looking in the wrong bit!**
You need to be in the <Children> section, at the bottom of the file.
Code: Select all
<ChildName d:type="cDeltaString">Driver</ChildName>
<BlueprintID>
<iBlueprintLibrary-cAbsoluteBlueprintID>
<BlueprintSetID>
<iBlueprintLibrary-cBlueprintSetID>
<Provider d:type="cDeltaString">DTG</Provider>
<Product d:type="cDeltaString">BedPanLine</Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">RailVehicles\Electric\Class319\Default\Characters\319_driver.xml</BlueprintID>
</iBlueprintLibrary-cAbsoluteBlueprintID>
</BlueprintID>
<Matrix>
<cHcRMatrix4x4>
<Element>
<e d:type="sFloat32" d:alt_encoding="000000000000F0BF" d:precision="string">-1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F0BF" d:precision="string">-1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000E0AB0FEABF" d:precision="string">-0.814413</e>
<e d:type="sFloat32" d:alt_encoding="000000A09999F13F" d:precision="string">1.1</e>
<e d:type="sFloat32" d:alt_encoding="0000000000002540" d:precision="string">10.5</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">1</e>
</Element>
</cHcRMatrix4x4>
</Matrix>
<ParentNodeName d:type="cDeltaString"></ParentNodeName>
</cEntityContainerBlueprint-sChild>
**EDIT--Did
you add the
s in an attempt to make the numbers bold? That won't work between [code}-[/code} tags; code makes the forum display just what is typed, ignoring any formatting, which is a very handy way of making sure that what we paste in from RW Tools displays just as it does in RW Tools.
Re: Pennine Pacer 323
Posted: Tue Aug 18, 2020 11:13 am
by 749006
gptech wrote:I've no idea why you have amongst those values, but you're looking in the wrong bit!**
You need to be in the <Children> section, at the bottom of the file.
**EDIT--Did you add the s in an attempt to make the numbers bold? That won't work between [code}-[/code} tags; code makes the forum display just what is typed, ignoring any formatting, which is a very handy way of making sure that what we paste in from RW Tools displays just as it does in RW Tools.
Yes you are right - twice 
I did add the s to make it bold and I did not realise it did not work in the code section
And I did not know there was another entry for the driver in the Child section - what is the purpose of two entries?
I copied the info from the Child section of the 323DMSO.bin in to my version and the chap is no longer in the walls
Passengers are in the train - some in the wrong position because of the different seat config
As I need a DMSO_B I can either copy the DMSO_A and rename or just put an A car at each end
Re: Pennine Pacer 323
Posted: Tue Aug 18, 2020 9:40 pm
by Springer6
This seems to be getting somewhere.
When it finally works out with a drivable 323 with cab ..passengers and driver, would there be any chance of the mod being published ? With the required permissions of course.

Re: Pennine Pacer 323
Posted: Tue Aug 18, 2020 10:48 pm
by gptech
749006 wrote: what is the purpose of two entries?
I've absolutely no idea!
Springer6 wrote:When it finally works out with a drivable 323 with cab ..passengers and driver, would there be any chance of the mod being published ? With the required permissions of course.
I can't see why not, neither of the methods under investigation impinge on DRM or IP rights--we just have to determine which is the best way to do it.