Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.

jgm

jgm
Siobhan said:
Here're my binds...
Trigger is primary/secondary fire and the nipplemouse is headlook (as is my mouse)

http://www.mcdee.net/elite/binds/xlgfby
Click to expand...

According to the binds file your primary fire is space and secondary fire is backspace. I suspect that you have mapped these in the Saitek manager, which is why it isn't showing up on the graphic.

The nipplemouse is harder because it does just emulate the mouse in this case, but not all cases. I could add the mouse in x/y in all cases but then it would sometimes show a phantom mapping.
 

Siobhan

Siobhan
jgm said:
According to the binds file your primary fire is space and secondary fire is backspace. I suspect that you have mapped these in the Saitek manager, which is why it isn't showing up on the graphic.

The nipplemouse is harder because it does just emulate the mouse in this case, but not all cases. I could add the mouse in x/y in all cases but then it would sometimes show a phantom mapping.
Click to expand...

That's correct. When mapping the trigger directly, when I went to secondary fire, then primary stopped. I wanted both together, so mapped it with keys and the saitek manager. The mouse is default behaviour, but since it's not labelled, I thought I'd mention it.
 

PingHansen

P
jgm said:
Have you been hacking the XML file manually perchance? That binds file is incorrect.
Click to expand...

Guilty as charged. Didn't notice how the modifiers were contained, so I screwed up on that. Plus what looks like an undo or two too many :eek: Looks like my editor doesn't validate what it loads :eek:, and I'm very happy to have caught that. I need to find a validation tool. Sorry for the inconvenience.

Anyway, a quick edit fixed those errors and the modifiers show just fine now for all of the inputs, including the modified keys on the keyboard :D. Thank you for that fine addition.

However, some of the actions have both a primary and a secondary keybind (I'm leaving in some of the original keys for compatibility), but only one is shown
Code: 
    <SetSpeedZero>
        <Primary Device="Keyboard" Key="Key_X" />
        <Secondary Device="Keyboard" Key="Key_Numpad_Decimal" />
    </SetSpeedZero>
You may also want to put a plus sign between the (Left alt) and the (key), as (Left alt) is a valid keybind by itself.

A potentially confusing issue, is that joystick actions for the SRV will show up on the stick, without mentioning that they only relate to the SRV (I had forgotten to change Joy_9 for the SRV, when I changed it for the spacecraft).

New file is binds/xzfjir

I noticed you changed the color of the joystick binds modified with LeftAlt modifier from reddish to green. Is there a reason? (just curious)
 

PingHansen

P
There is a small inconsistency in the way the keyboard references are generated, if there are secondary keys defined on the keyboard. I've only noticed it because I'm transitioning from one set of binds to another, having left the original keybinds for compatibility with some panels for Roccat's PowerGrid.

This:
Code: 
    <TargetWingman0>
        <Primary Device="Keyboard" Key="Key_7" />
        <Secondary Device="Keyboard" Key="Key_Numpad_9">
            <Modifier Device="Keyboard" Key="Key_LeftShift" />
        </Secondary>
    </TargetWingman0>
    <TargetWingman1>
        <Primary Device="Keyboard" Key="Key_8" />
        <Secondary Device="Keyboard" Key="Key_Numpad_0">
            <Modifier Device="Keyboard" Key="Key_LeftShift" />
        </Secondary>
    </TargetWingman1>
    <TargetWingman2>
        <Primary Device="Keyboard" Key="Key_9" />
        <Secondary Device="Keyboard" Key="Key_Numpad_Decimal">
            <Modifier Device="Keyboard" Key="Key_LeftShift" />
        </Secondary>
    </TargetWingman2>
    <SelectTargetsTarget>
        <Primary Device="Keyboard" Key="Key_0" />
        <Secondary Device="Keyboard" Key="Key_Numpad_Decimal">
            <Modifier Device="Keyboard" Key="Key_LeftAlt" />
        </Secondary>
    </SelectTargetsTarget>
    <WingNavLock>
        <Primary Device="Keyboard" Key="Key_Minus" />
        <Secondary Device="Keyboard" Key="Key_Numpad_6">
            <Modifier Device="Keyboard" Key="Key_LeftShift" />
        </Secondary>
    </WingNavLock>

Results in this:
mcdee_error.png
 

wolverine2710

Tutorial & Guide Writer
wolverine2710
I haven't played ED for quite a while. The tool was very usefull for finding back my setup in an easy way. After I've spread some rep I will rep+1 you.

I've taken the liberty of adding it to EDCodex, entry: "Keyboard and HOTAS Reference Sheet Generator". It would be great if you would take over and enhance my humble attempt. I know you have already registered, just send me a PM with the email address your registered with - for identification. You used the "claim owership" button for another entry but I missed that one, so a PM is the fastest way ;-)

On the 18th of January Bret C. created the brand new "Elite Dangerous->Gameplay and Features->Player Tools & API Development" subforum. You have already posted there. This thread seems to be a ideally suited for that subforum Perhaps something to consider.
 

Brieus

Brieus
I just found this, very nice so far. But do you think you could add a 2nd page that lists controls that are not bound to any keys?
 

jgm

jgm
Brieus said:
I just found this, very nice so far. But do you think you could add a 2nd page that lists controls that are not bound to any keys?
Click to expand...

That would be somewhat troublesome. A simple list wouldn't be very useful as there are a number of features that have alternative controls, for example main thrusters has both absolute (100/75/50/0/-25/-50/-75/-100) and relative (fasters/slower) controls. To further muddy the mix it also has both analogue and digital controls. You can pretty much guarantee that most people don't have all of these controls bound, but that doesn't mean that they are missing functionality. The page has a rudimentary grouping but it doesn't have enough to be able to work out if enough relevant controls are bound to provide this functionality. I'll have a think to see if there is some way of adding this information in a useful fashion.
 

Dia Vernon

Dia Vernon
Thank you JGM. I'm relatively new to Elite: Dangerous but I'm a veteran of the original Elite for the Commodore (way back when). This is a great tool and indeed find it very useful. Thanks again
 

MrNo

M
Great Tool and have used it a lot in the past 3 months or so....Anyhow I recently added an old Madcatz joy-pad to the system to use for the SRV worked a treat.
Now i get.

Unknown Controller

You have a device that is not supported at this time. Please report details of your device by following the link at the bottom of this page supplying the reference "shadej" and we will attempt to add support for it.

http://www.mcdee.net/elite/configs/shadej.binds

Thanks
 

jgm

jgm
MrNo said:
Great Tool and have used it a lot in the past 3 months or so....Anyhow I recently added an old Madcatz joy-pad to the system to use for the SRV worked a treat.
Now i get.

Unknown Controller

You have a device that is not supported at this time. Please report details of your device by following the link at the bottom of this page supplying the reference "shadej" and we will attempt to add support for it.

http://www.mcdee.net/elite/configs/shadej.binds

Thanks
Click to expand...

Please could you provide a link to this product on the web?
 

Wrongway

Wrongway
jgm said:
Yep sorry forgot to reply. I switched the buttons but am unsure about the hats because others have reported them as being correct the way they are currently. Are you using the CH mapper software, and if so can you check to see if anything has been rebound in there?

UPDATE: actually I think I've found the issue. Looks like you aren't using the CH software and the other configuration was, so I've remapped it. Please try it again and see how it looks.
Click to expand...

Sorry about the very late reply. I have been a bit out of touch with ED for the last month. I have just seen the update and glad you found the issue. Now I need to catch up with everything else thats been happening with this thread. It's certainly a fantastic utility that you have made and like many others I am very grateful.

It looks like each time we submit a file for generation it produces a file with a 6 character ID that is saved somewhere on your system. I can see myself making frequent changes as will probably others. I hope this doesn't cause a problem with all these files adding up. I am quite willing to overwrite older versions if it helps.
 

Wrongway

Wrongway
JGM I might have hit a problem. I have another ED control setup which uses a Warthog joystick with a CH Pro Throttle instead of the Warthog throttle, which I could never get used to. Thats coupled with Saitek rudder pedals. Have a look at the result. http://www.mcdee.net/elite/configs/jemtwo.binds
I am not using any mapping software.
 
Last edited:

jgm

jgm
Wrongway said:
JGM I might have hit a problem. I have another ED control setup which uses a Warthog joystick with a CH Pro Throttle instead of the Warthog throttle, which I could never get used to. Thats coupled with Saitek rudder pedals. Have a look at the result. http://www.mcdee.net/elite/configs/jemtwo.binds
I am not using any mapping software.
Click to expand...

Could you explain what the problem is? It looks like it is showing sheets for all three of these items...
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom