Page 1 of 2

DTG Class 180 guard call buzzer key?

Posted: Sat Sep 17, 2016 10:10 pm
by sn5775
Hi all,

Does anyone know if the DTG Class 180 has a key assigned to the guard call buzzer?

Many thanks.

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 8:19 am
by dave13
Hi sn5775
I don't think that their is a key assigned to the guard call buzzer :(
But you can press the green button in the cab :)
Dave:)

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 9:15 am
by dingerb
180 manual,green button on the left fig9. signal button.

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 9:58 am
by secludedsfx
dingerb wrote:180 manual,green button on the left fig9. signal button.
They were asking whether it had a keyboard key assigned to it (which it doesn't seem to).

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 11:58 am
by dingerb
duh :cry: and here's me thinking DGT would do a simple bind key to button. must be above there pay grades. :D

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 1:52 pm
by deltic009
dingerb wrote:duh :cry: and here's me thinking DGT would do a simple bind key to button. must be above there pay grades. :D
Well, if it's so simple then I await your files in the UKTS library. Welcome aboard to the content creating community.

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 9:00 pm
by gwrdevon
Hi sn5775

This is quite easy to fix, but you will need to edit a file to do so. If you don't feel comfortable doing this then please don't continue!

Open the folder ...Assets\DTG\Class180Pack01\InputMapper\

Edit the file Class180_InputExpert.bin using RWTools (RWtools is now available at UKtrainsim, file ID 21454 and will make a backup of the original .bin for you when you edit it).

The top of the file looks like this:

<cInputMapperBlueprint>
<RemapperName d:type="cDeltaString">Class180_InputExpert</RemapperName>
<Map>

Insert the following entry:

Code: Select all

				<iInputMapper-cInputMapEntry d:id="1242">
					<State d:type="sInt32">0</State>
					<Device d:type="cDeltaString">Keyboard</Device>
					<ButtonState d:type="cDeltaString">ButtonDown</ButtonState>
					<Button d:type="cDeltaString">Key_U</Button>
					<ShiftButton d:type="cDeltaString">NoShift</ShiftButton>
					<Axis d:type="cDeltaString">NoAxis</Axis>
					<Name d:type="cDeltaString">ToggleControl</Name>
					<Parameter d:type="cDeltaString">SignalBell</Parameter>
					<NewState d:type="sInt32">0</NewState>
				</iInputMapper-cInputMapEntry>
That's all there is to it, now the U key will sound the guard call buzzer.

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 10:07 pm
by AndyUK
Thank you, a much more helpful reply than the previous one!

Andy L

Re: DTG Class 180 guard call buzzer key?

Posted: Sun Sep 18, 2016 10:30 pm
by AndyUK
An alternative, with credit to gwrdevon for the original, which enables 'buzzes' in quicker succession and doesn't leave the desk buttons lit:

Code: Select all

				<iInputMapper-cInputMapEntry d:id="1242">
					<State d:type="sInt32">0</State>
					<Device d:type="cDeltaString">Keyboard</Device>
					<ButtonState d:type="cDeltaString">ButtonDown</ButtonState>
					<Button d:type="cDeltaString">Key_U</Button>
					<ShiftButton d:type="cDeltaString">NoShift</ShiftButton>
					<Axis d:type="cDeltaString">NoAxis</Axis>
					<Name d:type="cDeltaString">IncreaseControlStart</Name>
					<Parameter d:type="cDeltaString">SignalBell</Parameter>
					<NewState d:type="sInt32">0</NewState>
				</iInputMapper-cInputMapEntry>
				<iInputMapper-cInputMapEntry d:id="1242">
					<State d:type="sInt32">0</State>
					<Device d:type="cDeltaString">Keyboard</Device>
					<ButtonState d:type="cDeltaString">ButtonUp</ButtonState>
					<Button d:type="cDeltaString">Key_U</Button>
					<ShiftButton d:type="cDeltaString">NoShift</ShiftButton>
					<Axis d:type="cDeltaString">NoAxis</Axis>
					<Name d:type="cDeltaString">IncreaseControlStop</Name>
					<Parameter d:type="cDeltaString">SignalBell</Parameter>
					<NewState d:type="sInt32">0</NewState>
				</iInputMapper-cInputMapEntry>
Andy L

Re: DTG Class 180 guard call buzzer key?

Posted: Mon Sep 19, 2016 6:46 am
by dave13
Thanks a lot guys :D :D it worked a treat :D
Dave:)

Re: DTG Class 180 guard call buzzer key?

Posted: Tue Sep 20, 2016 4:11 pm
by Springer6
This looks very useful indeed ! Will this work (suitably modified) for any function on a loco where there is a cab button, but no allocated keyboard button? e.g. activate cruise control/speed set on the JT CRH380A ? I can't access my copy of TS at the moment to try it myself.
:)

Re: DTG Class 180 guard call buzzer key?

Posted: Tue Sep 20, 2016 6:51 pm
by gwrdevon
Yes you can assign a key for a cab button in most cases (there are always exceptions)!

I use a raildriver controller so always want to assign a key rather than use the mouse. For example I've assigned the DRA and speed control buttons to a key on most locos where they exist.

You need to find the appropriate entry in the engines bin file, it's the "Control Name" your looking for (SignalBell in the buzzer example I posted earlier). Then add this to the input mapper file (check the syntax, it's not consistent). Also check the key you assign is not already used in the mapper file, many non steam locos still use keys used for firebox, injector steam etc and can be safely deleted. Finally you must use a unique ID in the mapper file.

I don't have the JT CRH380A, but hope this helps.

Re: DTG Class 180 guard call buzzer key?

Posted: Tue Sep 20, 2016 8:51 pm
by Springer6
gwrdevon,

Thanks very much for explaining this. I will give it a try as soon as I can. :)

Springer

Re: DTG Class 180 guard call buzzer key?

Posted: Mon Sep 26, 2016 11:23 am
by gptech
Andy, shouldn't your second section have it's own id, rather than duplicating

<iInputMapper-cInputMapEntry d:id="1242"> ?

Re: DTG Class 180 guard call buzzer key?

Posted: Mon Sep 26, 2016 11:31 am
by deltic009
gptech wrote:Andy, shouldn't your second section have it's own id, rather than duplicating

<iInputMapper-cInputMapEntry d:id="1242"> ?
FWIW I have never change the actual number when duplicating or copying controls or things in blueprints. Lazy, but it hasn't caused me any issues thus far.