Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

If neither of those of work for you, you can donate any amount by clicking here.

Recommended Posts

Posted

hi, ive got my cab set up and as a controller im using the ipac, i have a few buttons mapped as left and right control and left and right shift as Future pinball used these but now i need to alter the config in nulldc in game ex to use these buttons i want right ctrl to be cab button C, i have buttons A ( lctrl - key 17 ) and B ( lshift - key 16 ) set but does anybody know the windows 7 keycode values for r ctrl?? i've looked everywhere even used program that give the key value but when pressing left or right ctrl i get the same value of 17??, i need to alter the control in the cfg file as if i try to run nulldc outside of gameex it crashes so i cant get to the options :(, in GameEx it works fine just need to tweek the control slightly.

As allways Any help appreciated.

Posted

I don't think this will work as there may not be a specific assignment for each ctrl key like there is for shift keys, unless you use virtual key codes.

You should be able to use ahk to get around this though.

Posted
  On 10/8/2011 at 12:10 AM, Adultery said:

I don't think this will work as there may not be a specific assignment for each ctrl key like there is for shift keys, unless you use virtual key codes.

You should be able to use ahk to get around this though.

Ive used code A3 which seems to be working but need to test further to make sure, but if not autohotkey will be the next to try, thanks bro.

Posted

If that works, then I misread. I saw it said 0xA3 on MSDN but thought that was for VB, not key codes. :)

Posted
  On 10/8/2011 at 12:31 AM, Adultery said:

If that works, then I misread. I saw it said 0xA3 on MSDN but thought that was for VB, not key codes. :)

Hiya, adding the A3 seems to have done the trick so will mark as resolved :)

Posted

Awesomesauce! :-)

Guest
This topic is now closed to further replies.
×
×
  • Create New...