Atomic Systems

Atomic Systems Forums
https://forums.uktrainsim.com/

Oovee WCR Mk1 changes

https://forums.uktrainsim.com/viewtopic.php?f=361&t=149516

Page 1 of 2

Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 12:39 pm
by RobertM
Afternoon all,

I have been playing with the West Highland & BMG 5MT lately, and now I would like to make some changes to the Oovee class 57 Mk1's, first being to change from the old oil tail lamp to a modern electric tail lamp. The lamps like most others come on automatically when you turn the trains headlamps on. I have placed a child object in using a modern lamp successfully, but the old lamp still appears as well, looking very weird, is there a way to trick/disable this lamp?

Secondly, I would like to add a heads-out view as well, but what I want to do is have one carriage have a heads-out view like the Wherry Lines does & only one coach so you do not have to cycle through them all. What my question is how do I clone a coach, edit it and rename it so that it appears as a separate coach in TS?

Robert

Re: Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 3:37 pm
by xguerra
I can't answer the tail lamp query but the second one I can.

Rather than trying to have the one heads-out view coach to stick anywhere in the consist, how about just add it to a brake coach like a BCK/BFK?
You would typically have just the one in the consist, and then wouldn't worry about a special heads-out coach.

As for making it happen, have you edited .bin files and used RW-Tools before?

If you download Matt Wilson's DT Mk1 Upgrade pack from the UKTS library, you'll find in one of the coach folders a special .bin file for the "interior view" camera. which you can use as a template.
It's treated as an interior despite being head out of the carriage, it's just a matter of camera position. And then in the main coach .bin file you reference that as your interior view, and then reference the whole coach .geopcdx shape file as your interior geometry.

Hope that helps somewhat.

Re: Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 5:25 pm
by deltic009
I'd sincerely hope that the OP doesn't follow the advice given and use my work as a template without permission. I don't spend hours of development time on various projects in order to provide templates for people to use as they see fit without permission.

Seems it might be pertinent for my file presence to make as a sharp an exit as my forum presence did!

Re: Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 5:42 pm
by xguerra
deltic009 wrote:I'd sincerely hope that the OP doesn't follow the advice given and use my work as a template without permission. I don't spend hours of development time on various projects in order to provide templates for people to use as they see fit without permission.

Seems it might be pertinent for my file presence to make as a sharp an exit as my forum presence did!
Sorry Matt, I meant to imply in the sense of seeking inspiration and learning how it's done rather than actually using your files.
My poor choice of words.

Re: Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 5:58 pm
by RobertM
Matt, this project is just for me, no one else.

Re: Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 6:05 pm
by gptech
RobertM wrote:I have placed a child object in using a modern lamp successfully, but the old lamp still appears as well, looking very weird, is there a way to trick/disable this lamp?
If the lamp is a named node of the coach's .GeoPcDx file (I'd bet that it is) then that should be 'hide-able' with a small bit of scripting. I'll have a wee dig into it when I'm home.

Re: Oovee WCR Mk1 changes

Posted: Sun Jun 03, 2018 9:04 pm
by gptech
gptech wrote:I'll have a wee dig into it when I'm home.
mmm...no joy I'm afraid; can hide various bits but not the lamps :o ...... and not even all the parts I've been able to hide in other stock items.

I haven't time now until my next set of days off to spend hours investigating further, but I'll pick the ball up (as it were) as soon as I can---that of course doesn't mean that I'm claiming this as my own project, the rest of you can feel free to join in; many hands and light work etc :)

This snippet from an old discussion about adding lights may be relevant though... http://forums.uktrainsim.com/viewtopic. ... 3#p1749223...which is bad news as far as this enquiry is concerned. The whole thread is worth a read actually, even if it does wander about a bit, to give an insight into how these lighting functions work.

Re: Oovee WCR Mk1 changes

Posted: Mon Jun 04, 2018 4:55 pm
by RobertM
xguerra wrote:Rather than trying to have the one heads-out view coach to stick anywhere in the consist, how about just add it to a brake coach like a BCK/BFK?
I'm being fussy but I am basing the consists off of the actual Jacobite sets, and want the heads out view from the first window for maximum THRASH!!!

Re: Oovee WCR Mk1 changes

Posted: Mon Jun 04, 2018 6:05 pm
by rfletcher72
RobertM wrote:
xguerra wrote:Rather than trying to have the one heads-out view coach to stick anywhere in the consist, how about just add it to a brake coach like a BCK/BFK?
I'm being fussy but I am basing the consists off of the actual Jacobite sets, and want the heads out view from the first window for maximum THRASH!!!
Then create a bespoke .bin file so you know which asset to place behind the loco?

Re: Oovee WCR Mk1 changes

Posted: Mon Jun 04, 2018 7:50 pm
by gptech
Lets start answering questions.....
RobertM wrote:how do I clone a coach, edit it and rename it so that it appears as a separate coach in TS?
Copy the ,bin file of the coach; for example you'd copy ..\Assets\Oovee\BRClass57Pack01_WCRC\RailVehicles\Passenger\Mk1\FO\WCRC\Coach\mk1fo.bin and paste it on your desktop. Then rename that copied .bin to something that makes sense to you, mk1fo-head out.bin is one that springs to mind. Then cut and paste that copied and renamed file into the ..\Assets\Oovee\BRClass57Pack01_WCRC\RailVehicles\Passenger\Mk1\FO\WCRC\Coach folder. You could do the initial copy and paste into there, which would give you a mk1fo - Copy.bin file which you'd then rename accordingly but I prefer to use the desktop to avoid confusing myself.
Open that new, copied and renamed file with RW Tools and change the descriptive name fields---they're right at the top so you don't have to go searching:

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>
		<cWagonBlueprint>
			<Name d:type="cDeltaString">Mk1 FO WCRC</Name>
			<BrowseInformation>
				<iRailVehicleBlueprint-cBrowseRVInformation>
					<DisplayName>
						<Localisation-cUserLocalisedString>
							<English d:type="cDeltaString">Mk1 FO WCRC</English>
							<French d:type="cDeltaString"></French>
							<Italian d:type="cDeltaString"></Italian>
							<German d:type="cDeltaString"></German>
							<Spanish d:type="cDeltaString"></Spanish>
							<Dutch d:type="cDeltaString"></Dutch>
							<Polish d:type="cDeltaString"></Polish>
							<Russian d:type="cDeltaString"></Russian>
							<Other/>
							<Key d:type="cDeltaString"></Key>
						</Localisation-cUserLocalisedString>
					</DisplayName>
				</iRailVehicleBlueprint-cBrowseRVInformation>
			</BrowseInformation>
would become

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>
		<cWagonBlueprint>
			<Name d:type="cDeltaString">Mk1 FO WCRC - Head Out</Name>
			<BrowseInformation>
				<iRailVehicleBlueprint-cBrowseRVInformation>
					<DisplayName>
						<Localisation-cUserLocalisedString>
							<English d:type="cDeltaString">Mk1 FO WCRC - Head Out</English>
							<French d:type="cDeltaString"></French>
							<Italian d:type="cDeltaString"></Italian>
							<German d:type="cDeltaString"></German>
							<Spanish d:type="cDeltaString"></Spanish>
							<Dutch d:type="cDeltaString"></Dutch>
							<Polish d:type="cDeltaString"></Polish>
							<Russian d:type="cDeltaString"></Russian>
							<Other/>
							<Key d:type="cDeltaString"></Key>
						</Localisation-cUserLocalisedString>
					</DisplayName>
				</iRailVehicleBlueprint-cBrowseRVInformation>
			</BrowseInformation>
That little edit gets it showing as a new stock item in the games 'available stock' listing.
Any further edits to change/add the passenger view will only affect that single item.

That's the basic way how reskins start out life, a supplied .bin file is copied and amended, or in other words a supplied .bin file is used as a template.

Get that far, making sure it will appear in game when selected of course, and then you can think about adding the passenger view stuff---once again that'll mostly be using supplied files and amending them.

Re: Oovee WCR Mk1 changes

Posted: Thu Jun 21, 2018 9:33 pm
by RobertM
Took a break from TS for a while but back with it now.

So far I have managed to clone the coach, rename it and have it run up in the simulator.

Passenger view wise, I decided to copy what DTG did with the Dutchess Pack (just because it was the only passenger view I could think of) and used there coaches head out passenger view as my donor.

So far, I have copied the Dutchess passenger view folder from RSC\DuchessPack01\RailVehicles\Passenger\MK1FK\PassengerView & pasted it to Oovee\BRClass57Pack01_WCRC\RailVehicles\Passenger\MK1SK\BR Crimson\Coach\PassengerView. I then edited the Oovee coach from this

Code: Select all

					<InteriorInterface>
						<cControlContainerBlueprint-cInteriorInterface>
							<InteriorGeometryID d:type="cDeltaString"></InteriorGeometryID>
							<NumberOfCabs d:type="cDeltaString">eNoCab</NumberOfCabs>
							<InteriorCamera>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString"></Provider>
											<Product d:type="cDeltaString"></Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString"></BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</InteriorCamera>
							<CabOcclusion>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString">Oovee</Provider>
											<Product d:type="cDeltaString">SettleCarlisle</Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString"></BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</CabOcclusion>
						</cControlContainerBlueprint-cInteriorInterface>
					</InteriorInterface>
					<CarriageInteriorInterface>
						<cControlContainerBlueprint-cInteriorInterface>
							<InteriorGeometryID d:type="cDeltaString"></InteriorGeometryID>
							<NumberOfCabs d:type="cDeltaString">eSingleCab</NumberOfCabs>
							<InteriorCamera>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString"></Provider>
											<Product d:type="cDeltaString"></Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString"></BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</InteriorCamera>
							<CabOcclusion>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString"></Provider>
											<Product d:type="cDeltaString"></Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString"></BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</CabOcclusion>
						</cControlContainerBlueprint-cInteriorInterface>
					</CarriageInteriorInterface>
too this

Code: Select all

					<InteriorInterface>
						<cControlContainerBlueprint-cInteriorInterface>
							<InteriorGeometryID d:type="cDeltaString"></InteriorGeometryID>
							<NumberOfCabs d:type="cDeltaString">eNoCab</NumberOfCabs>
							<InteriorCamera>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString"></Provider>
											<Product d:type="cDeltaString"></Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString"></BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</InteriorCamera>
							<CabOcclusion>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString">RSC</Provider>
											<Product d:type="cDeltaString">DuchessPack01</Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString">Audio\RailVehicles\Wagons\Passenger Carriage Occlusion.xml</BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</CabOcclusion>
						</cControlContainerBlueprint-cInteriorInterface>
					</InteriorInterface>
					<CarriageInteriorInterface>
						<cControlContainerBlueprint-cInteriorInterface>
							<InteriorGeometryID d:type="cDeltaString">Oovee\BRClass57Pack01_WCRC\RailVehicles\Passenger\MK1SK\BR Crimson\Coach\PassengerView\[00]mk1fk_interior</InteriorGeometryID>
							<NumberOfCabs d:type="cDeltaString">eNoCab</NumberOfCabs>
							<InteriorCamera>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString">RSC</Provider>
											<Product d:type="cDeltaString">DuchessPack01</Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString">RailVehicles\Passenger\MK1FK\PassengerView\mk1fk_passview.xml</BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</InteriorCamera>
							<CabOcclusion>
								<iBlueprintLibrary-cAbsoluteBlueprintID>
									<BlueprintSetID>
										<iBlueprintLibrary-cBlueprintSetID>
											<Provider d:type="cDeltaString">RSC</Provider>
											<Product d:type="cDeltaString">DuchessPack01</Product>
										</iBlueprintLibrary-cBlueprintSetID>
									</BlueprintSetID>
									<BlueprintID d:type="cDeltaString">Audio\RailVehicles\Wagons\Passenger Carriage Occlusion.xml</BlueprintID>
								</iBlueprintLibrary-cAbsoluteBlueprintID>
							</CabOcclusion>
						</cControlContainerBlueprint-cInteriorInterface>
					</CarriageInteriorInterface>
Fired up the sim and guess what, no view. The coach loads up fine.

What am I missing?

Robert

Re: Oovee WCR Mk1 changes

Posted: Thu Jun 21, 2018 10:17 pm
by gptech
RobertM wrote:What am I missing?
You're thinking too sensibly, too 'human'.

A camera in the game is just a viewpoint to look at whatever model it's referenced to---a cab camera has you looking at the model of the cab interior, a passenger view at the model of a coach interior.
You need to point the camera at the outside of the coach rather than the inside:
xguerra wrote:.....and then reference the whole coach .geopcdx shape file as your interior geometry.[/quot

Look at how a loco's head out view works, that could throw some more light on it---I'll be able to delve a bit further after the weekend, which is why this is a bit short and not detailed.

Re: Oovee WCR Mk1 changes

Posted: Fri Jun 22, 2018 12:50 pm
by RobertM
Yeah, think I'm struggling to get my head round this one. Back in MSTS (those many many moons ago) this would of been a doddle. Shows how out of touch I am :roll:

Re: Oovee WCR Mk1 changes

Posted: Fri Jun 22, 2018 6:48 pm
by RobertM
Right, success :angel:

I discovered that the Duchess coach I was copying from was infact an interior view, as the Duchess Mk1 set has 2 passenger views, the FK having an internal view & the SK having a heads-out window.

So, I copied the relevant files and edited and success.

All I need do know is the tail lamp.

:drinking:

Re: Oovee WCR Mk1 changes

Posted: Fri Jun 22, 2018 10:19 pm
by gptech
Well done!!...and all without stepping on anybody's IP.

It may be possible to move the oil lamp so it isn't visible; I think that's touched upon in the thread I linked to earlier.
All times are UTC
Page 1 of 2

Powered by phpBB® Forum Software © phpBB Limited