Atomic Systems

LionelMarco wrote:But ( as there's always a but...) I'm using a French keyboard (Azerty), and the overlay seems linked to a Qwerty one. So the control are "wrongly" placed (an easy one: Decrease speed-Q- is A on my keyboard and so on). In the end, it's quite dificult to translate the command in my head... Is there's a way to adapt your script to "different" keyboards?

PS: If you still need a few bin file from steam locomotive or class 101 , I can send you a few ones.

davep wrote:My apologies Havner. It seems I missed YOUR post

LionelMarco wrote:Hi!

Same problem with the Xbox360 controller which is completely off too: trying to add break in fact open the throttle. May it be related to the keyboard problem?
Lionel Marco.

CobraOne wrote:

LionelMarco wrote:Hi!

Same problem with the Xbox360 controller which is completely off too: trying to add break in fact open the throttle. May it be related to the keyboard problem?
Lionel Marco.

If you look in the 'trainsim-helper-joystick.lua' file which should be in your plugins folder, at the top there is the section

CobraOne wrote:@Havner Have a look at the program and if you feel it may help others then maybe consider including it in your next update too.

<ControlName d:type="cDeltaString">Regulator</ControlName>
(...)
	<NumberOfNotches d:type="sFloat32" d:alt_encoding="0000000000002240" d:precision="string">9</NumberOfNotches>

Havner wrote: I had a quick look at few locos with notches and nice work. Definitely useful.
You want me to link it somewhere? Or include the complete binary??

Havner wrote:One thing that might be nice to handle is a case where the game is using equal notches. Like throttle in most of the US locos.

Code: Select all

<ControlName d:type="cDeltaString">Regulator</ControlName>
(...)
	<NumberOfNotches d:type="sFloat32" d:alt_encoding="0000000000002240" d:precision="string">9</NumberOfNotches>

Havner wrote: BTW, how's your work on the remapper?

if OnControlValueChange then
	OnControlValueChange(t[1], 0, t[2])
else
	Call( "*:SetControlValue", t[1], 0, t[2]) 
end

if OnControlValueChange then
	OnControlValueChange(t[1], 0, tonumber(t[2]))
else
	Call( "*:SetControlValue", t[1], 0, tonumber(t[2])) 
end

CobraOne wrote:Done and new files uploaded https://www.dropbox.com/sh/svyifuyxtice ... Un8Ia?dl=0

I managed to find the problem with getting the class 365 working. I had used

I am also now working on adding something similar to your overlay as I am sure people who wish to use the Raildriver, will, on seeing your overlay, want one too! but rather than incorporate your helper_script into mine and maybe cause confusion I thought I should keep it separate.

Havner wrote: BTW, how does Raildriver work? Can it be used as is with my helper at all? I mean, does windows see it as a regular joystick or not?
I know they have some SDK, so in theory one could make it work as he wishes. But out of the box, is it of any use in things not specifically written for it?

EDIT: oh, and by the remapper I meant your tool to change keyboard shortcuts, not the RailDriver stuff. You've posted a screenshot of it in the other thread. I thought those were separate.

CobraOne wrote:Havner your a Genius, can't wait to see the code and if it's OK incorporate the idea into my version.

DeltaTime = CurrentSimTime - PreviousSimTime
DeltaDistance = CurrentSpeed * DeltaTime
AccumulatedDistance += DeltaDistance
PreviousSimTime = CurrentSimTime

Natvander wrote:So in essence you've created an odometer? That is cool . If it can be reset at any time, and you know the length of your train you could use it when passing speed limit boards etc. Especially useful for multi-km long US intermodals.

Havner wrote: EDIT: CobraOne, I've used you data extractor in live cases to prepare more locos. Makes things much easier. Nice work, thanks again. I'd just remove the "**" in output file to see the subsections more easily.

Havner wrote: Also I've found a curious case.
FP59PH. It has regulator (0,1) with 17 equal notches and dynamic brake (0,1) with 19 equal notches. But in the game they are combined. And the resulting notches are combined as well. 10 (half) notches for (0, 0.5) and 9 (half) notches for (0.5,1). Making them unequal for the whole range.