Just getting started with TS2014 -problem with two cab views
Moderator: Moderators
Just getting started with TS2014 -problem with two cab views
Hi all,
I've recently bought Train Simulator 2014 Steam Edition and have installed a few routes and rolling stock.
I've been struggling to create my own routes, scenarios and consists but managed to create a very basic scenario and consist.
I have a Class 166 DMU which I think is from the Great Western Paddington to Oxford route and have installed a London Midland reskin. The 166 appears fine when in FGW livery but when in LM livery I have a problem with the cab view whereby the windscreen blind appears to be pulled halfway down obscuring most of the view forward.
I also have the Portsmouth route with the Class 450 which again works fine by itself but I have also installed the London Midland Class 350 reskin and the windscreen is also obscured, but is worse than the 166. Hope this makes sense.
Not sure what further information to provide - please let me know.
Any help gratefully appreciated.
I've recently bought Train Simulator 2014 Steam Edition and have installed a few routes and rolling stock.
I've been struggling to create my own routes, scenarios and consists but managed to create a very basic scenario and consist.
I have a Class 166 DMU which I think is from the Great Western Paddington to Oxford route and have installed a London Midland reskin. The 166 appears fine when in FGW livery but when in LM livery I have a problem with the cab view whereby the windscreen blind appears to be pulled halfway down obscuring most of the view forward.
I also have the Portsmouth route with the Class 450 which again works fine by itself but I have also installed the London Midland Class 350 reskin and the windscreen is also obscured, but is worse than the 166. Hope this makes sense.
Not sure what further information to provide - please let me know.
Any help gratefully appreciated.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
Those cab view problems are because the .bin files don't have a reference for the wipe pairs---the bit that was introduced when we got rain on windows.
The class 350 has a newer version in the library, the 166 may have a fix already produced but you'd probably need to edit the file yourself. When I get home tonight, unless somebody else pops in of course with a fix, I'll have a proper look and sort somethin for you.
The class 350 has a newer version in the library, the 166 may have a fix already produced but you'd probably need to edit the file yourself. When I get home tonight, unless somebody else pops in of course with a fix, I'll have a proper look and sort somethin for you.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
Much to my shame and embarrassment, I forgot that the updated 350 uses the GEML class 360 PTSO so if you don't have GEML that'd be of no use to you.
Are you happy editing .bin files?
If so, you need to open the Class350 DMOS.bin
and add:
immediately after the </ControlValues> tag. This is about 3/4 of the way down the document.
For the 166 the section to add to the class166_dmos.bin file is:
once agin after the </ControlValues> tag.
If that's all double dutch to you, just shout and we'll work round that.
Are you happy editing .bin files?
If so, you need to open the Class350 DMOS.bin
and add:
Code: Select all
<WiperPairs>
<cControlContainerBlueprint-cWiperPair d:id="65301088">
<SlaveToAnimationA d:type="cDeltaString">wipers</SlaveToAnimationA>
<SlaveToAnimationB d:type="cDeltaString">wipers</SlaveToAnimationB>
<TextureID d:type="cDeltaString">RSC\GuildfordDistrict\RailVehicles\Electric\Class450\Default\CabView\Textures\[00]wiperanim_nm</TextureID>
<NormalsTextureID d:type="cDeltaString">RSC\GuildfordDistrict\RailVehicles\Electric\Class450\Default\CabView\Textures\[00]weatherglassnorm_nm</NormalsTextureID>
</cControlContainerBlueprint-cWiperPair>
</WiperPairs>
For the 166 the section to add to the class166_dmos.bin file is:
Code: Select all
<WiperPairs>
<cControlContainerBlueprint-cWiperPair d:id="78360832">
<SlaveToAnimationA d:type="cDeltaString">wipers</SlaveToAnimationA>
<SlaveToAnimationB d:type="cDeltaString">wipers</SlaveToAnimationB>
<TextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_wiperexp_nm</TextureID>
<NormalsTextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_norms_nm</NormalsTextureID>
</cControlContainerBlueprint-cWiperPair>
<cControlContainerBlueprint-cWiperPair d:id="78361472">
<SlaveToAnimationA d:type="cDeltaString">wipers</SlaveToAnimationA>
<SlaveToAnimationB d:type="cDeltaString">wipers</SlaveToAnimationB>
<TextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_wiperexp_nm</TextureID>
<NormalsTextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_norms_nm</NormalsTextureID>
</cControlContainerBlueprint-cWiperPair>
</WiperPairs>
If that's all double dutch to you, just shout and we'll work round that.
-
msmith4000
- Established Forum Member
- Posts: 383
- Joined: Mon May 24, 2010 1:24 pm
- Location: Fife
Re: Just getting started with TS2014 -problem with two cab views
Lots of older reskins dont work properly in later versions of TS2014 for reasons already explained earlier. Look for updated versions in the library - if they are not available they could probably still be used for AI trains. There are some fixes in the library - the HST buffer pack being one that springs to mind.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
and if there aren't any, ask and somebody will either guide you through *fixing* things or do it for you. I doubt there's a single older skin that can't be tweaked to work with the newer model shapes.msmith4000 wrote:Lots of older reskins dont work properly in later versions of TS2014 for reasons already explained earlier. Look for updated versions in the library
-
msmith4000
- Established Forum Member
- Posts: 383
- Joined: Mon May 24, 2010 1:24 pm
- Location: Fife
Re: Just getting started with TS2014 -problem with two cab views
Indeed gptech - which reminds me I have a lot of Class 60 reskins I have to get round to fixing after upgrading to the Advanced version! I did have a lot of Class 47's to fix as well but I ended up having a wee clear out to get my kuju folder size down a bit
Re: Just getting started with TS2014 -problem with two cab views
gptech wrote:Much to my shame and embarrassment, I forgot that the updated 350 uses the GEML class 360 PTSO so if you don't have GEML that'd be of no use to you.
Are you happy editing .bin files?
If that's all double dutch to you, just shout and we'll work round that.
Many thanks for your help. I have some coding experience so I thought I'd be able to modify the .bin files myself but I'm still experiencing the same issues. I suspect I have gone wrong somewhere. Before trying to modify the .bin files I made backup copies, which I have since restored.
I wish I'd made a note of everything I'd bought/downloaded/installed, but I've managed to discover the following, if it helps:-
The class 166 appears to be from the Steam Great Western Mainline add-on and the class 350 appears to be Class 350 Pack V1 UKTS File ID 26498 by sippycarlito (Simon Carlier) which requires the Portsmouth route add-on from Steam, which I do have.
The file paths that I tried to modify were as follows:-
class166_dmos.bin
C:\Program Files (x86)\Steam\SteamApps\common\RailWorks\Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\LondonMidland\DMOS
Class 350/1 London Midland
C:\Program Files (x86)\Steam\SteamApps\common\RailWorks\Assets\RSC\GuildfordDistrict\RailVehicles\Electric\Class450\LM1\Engine
Class 350/2 London Midland
C:\Program Files (x86)\Steam\SteamApps\common\RailWorks\Assets\RSC\GuildfordDistrict\RailVehicles\Electric\Class450\LM2\Engine
Would it be possible, please, to request some guidance with updating the .bin files?
Thanks again and kindest regards.
Re: Just getting started with TS2014 -problem with two cab views
Hi all,
I thought I would provide some screenshots as these might explain the problem better than I can:-
Class 166 DMU from GWML route with London Midland reskin:-
- cab
- view from cab with zoom forward
Class 450 EMU from Portsmouth route with London Midland reskin:-
- cab
- view from cab with zoom forward
Thanks again.
I thought I would provide some screenshots as these might explain the problem better than I can:-
Class 166 DMU from GWML route with London Midland reskin:-
- cab
- view from cab with zoom forwardClass 450 EMU from Portsmouth route with London Midland reskin:-
- cab
- view from cab with zoom forwardThanks again.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
Hi again,
sorry for seeming to leave you in the lurch, but I've been on holiday
The 166 is likely to be the more 'involved' one to fix, as if you have:
it uses the older shape files which means the textures don't map properly to the newer model.
A slightly different problem to yours was resolved with http://forums.uktrainsim.com/viewtopic. ... 8#p1694356
so give that a whirl.
Get the 166 sorted and then we'll see to the 350
sorry for seeming to leave you in the lurch, but I've been on holiday
The 166 is likely to be the more 'involved' one to fix, as if you have:
|
it uses the older shape files which means the textures don't map properly to the newer model.
A slightly different problem to yours was resolved with http://forums.uktrainsim.com/viewtopic. ... 8#p1694356
so give that a whirl.
Get the 166 sorted and then we'll see to the 350
Re: Just getting started with TS2014 -problem with two cab views
Hi gptech,
Many thanks for your reply. I followed the instructions in the other thread for the Class 166 but unfortunately this has not resolved the problem. Not to worry.
Hopefully we can get the Class 350 working?
Many thanks again for your continued help.
Many thanks for your reply. I followed the instructions in the other thread for the Class 166 but unfortunately this has not resolved the problem. Not to worry.
Hopefully we can get the Class 350 working?
Many thanks again for your continued help.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
I've just downloaded the LM 166 and had a play about and the "wiper pairs" bit gets rid of the odd cab view:
Fire up RW Tools or whatever you use for editing ,bin files and open
..\RailWorks\Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\LondonMidland\DMOCL\class166_dmocl.bin
Just above the <Children> section, about 3/4 of the way down the file, you'll find:
Click on the document after the </ControlValues> and press 'Enter' to create a new blank line.
In here paste the following:
Repeat the process for the
..\RailWorks\Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\LondonMidland\DMOS\class166_dmos.bin file
That should get you a *proper* cab view in both driving cars
Test the doors, if they shoot up in the air when opening you'll need to work through the other fix to use the older animations.
EDIT: It's probably worth deleting the cache file (Blueprints.pak) from the ..\RailWorks\Assets\Kuju\RailSimulator folder before testing the edited stock.
Fire up RW Tools or whatever you use for editing ,bin files and open
..\RailWorks\Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\LondonMidland\DMOCL\class166_dmocl.bin
Just above the <Children> section, about 3/4 of the way down the file, you'll find:
Code: Select all
</ControlValues>
</cControlContainerBlueprint>
</ControlContainerComponent>
<ContainerComponent>
<cEntityContainerBlueprint>In here paste the following:
Code: Select all
<WiperPairs>
<cControlContainerBlueprint-cWiperPair d:id="74210016">
<SlaveToAnimationA d:type="cDeltaString">wipers</SlaveToAnimationA>
<SlaveToAnimationB d:type="cDeltaString">wipers</SlaveToAnimationB>
<TextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_wiperexp_nm</TextureID>
<NormalsTextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_norms_nm</NormalsTextureID>
</cControlContainerBlueprint-cWiperPair>
<cControlContainerBlueprint-cWiperPair d:id="74210656">
<SlaveToAnimationA d:type="cDeltaString">wipers</SlaveToAnimationA>
<SlaveToAnimationB d:type="cDeltaString">wipers</SlaveToAnimationB>
<TextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_wiperexp_nm</TextureID>
<NormalsTextureID d:type="cDeltaString">Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\CabView\Textures\[00]166_cab_norms_nm</NormalsTextureID>
</cControlContainerBlueprint-cWiperPair>
</WiperPairs>..\RailWorks\Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\LondonMidland\DMOS\class166_dmos.bin file
That should get you a *proper* cab view in both driving cars
Test the doors, if they shoot up in the air when opening you'll need to work through the other fix to use the older animations.
EDIT: It's probably worth deleting the cache file (Blueprints.pak) from the ..\RailWorks\Assets\Kuju\RailSimulator folder before testing the edited stock.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
For the 350 you could grab Richard's reskin from http://www.dpsimulation.org.uk/rf72reskins.html.
Although this is for the Brighton Mainline version of the 450 it'd be easy to edit the .bin files to point to the PDL stock.
This reskin includes a custom built panto so the PTSOL won't look 'odd' and would be the way I'd fo in your position.
Although this is for the Brighton Mainline version of the 450 it'd be easy to edit the .bin files to point to the PDL stock.
This reskin includes a custom built panto so the PTSOL won't look 'odd' and would be the way I'd fo in your position.
Re: Just getting started with TS2014 -problem with two cab views
I am pleased to say that I've been able to get the 166 and 350 running - there is a minor glitch with the 350 where some of the "London Midland" logos appear mirrored (I think). Also had one strange incident where the passenger doors opened on the wrong side?
I have found another Class 350 UKTS File ID: 32433 which I have tested and works absolutely fine.
I've since had the same cab view problem with a Cross Country HST which I was able to fix and I've also been able to apply the cab light fix to the Class 390 Pendolino using a similar method, so many thanks once again for your help.
Kindest regards.
I have found another Class 350 UKTS File ID: 32433 which I have tested and works absolutely fine.
I've since had the same cab view problem with a Cross Country HST which I was able to fix and I've also been able to apply the cab light fix to the Class 390 Pendolino using a similar method, so many thanks once again for your help.
Kindest regards.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Just getting started with TS2014 -problem with two cab views
Yeah, that's a known issue with how the textures for the DMOS are mapped to the model. Using decals as child objects is the way round that so if you want/need to know how to *fix* that just shout and loads of folk will advise how it's done.sn5775 wrote:there is a minor glitch with the 350 where some of the "London Midland" logos appear mirrored
