Jump to content

UFC programmed to Number Pad

Dispatch

By Dispatch
in Wish List

 Share

Recommended Posts

Rudel_chw

Rudel_chw

Posted
Posted

The NumPad keys are also used for the default View keys, that's why I opted to use LCtrl + Num# instead, and it's equally easy to use the right hand to input the digit, while the left one keeps the Left Control down.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites
Harlikwin

Harlikwin

Posted
Posted
Yup, I've been doing that since my days flying Falcon 4.0

 

The fun question is - do you map them as your numeric keypad is, or in the order they are on the UFC?

 

You can pull the keys off a numpad and repalce/program them as they are on the UFC.

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Link to comment
Share on other sites
Eldur

Eldur

Posted
Posted

I'm using a Autohotkey script to have different mappings dependant on the NumLock state, without overriding the cursor keys or the block above.

 

 

 

; --- Numpad off to type RWin + numbers -------------------

NumpadIns::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad0 Down}
   Sleep, 1
   KeyWait NumpadIns
   Sleep, 1
   SendInput, {Numpad0 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadEnd::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad1 Down}
   Sleep, 1
   KeyWait NumpadEnd
   Sleep, 1
   SendInput, {Numpad1 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadDown::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad2 Down}
   Sleep, 1
   KeyWait NumpadDown
   Sleep, 1
   SendInput, {Numpad2 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadPgDn::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad3 Down}
   Sleep, 1
   KeyWait NumpadPgDn
   Sleep, 1
   SendInput, {Numpad3 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadLeft::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad4 Down}
   Sleep, 1
   KeyWait NumpadLeft
   Sleep, 1
   SendInput, {Numpad4 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
;For some reason NumpadClear is not k-hook and have to use *
*NumpadClear::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad5 Down}
   Sleep, 1
   KeyWait NumpadClear
   Sleep, 1
   SendInput, {Numpad5 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadRight::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad6 Down}
   Sleep, 1
   KeyWait NumpadRight
   Sleep, 1
   SendInput, {Numpad6 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadHome::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad7 Down}
   Sleep, 1
   KeyWait NumpadHome
   Sleep, 1
   SendInput, {Numpad7 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadUp::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad8 Down}
   Sleep, 1
   KeyWait NumpadUp
   Sleep, 1
   SendInput, {Numpad8 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadPgUp::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {Numpad9 Down}
   Sleep, 1
   KeyWait NumpadPgUp
   Sleep, 1
   SendInput, {Numpad9 Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return
NumpadDel::
{
   SendInput, {RWin Down}
   Sleep, 1
   SendInput, {NumpadDot Down}
   Sleep, 1
   KeyWait NumpadDel
   Sleep, 1
   SendInput, {NumpadDot Up}
   Sleep, 1
   SendInput, {RWin Up}
}
return

 

 

 

With that you'll send RWin + Numpad keys when NumLock is off, which I use for the UFC, or the keypad in the Viggen for example. Just tap NumLock and get the view control back, plus the current state is visible by the LED (well, not with an VR HMD mounted...

dcsdashie-hb-ed.jpg

 

Link to comment
Share on other sites
TonyG

TonyG

Posted
Posted
Yup, I've been doing that since my days flying Falcon 4.0

 

The fun question is - do you map them as your numeric keypad is, or in the order they are on the UFC?

 

Order they are on the UFC, which trips me up as a I do a lot of data entry for work. I just remind myself to look at the ufc when I’m doing it ;)

Link to comment
Share on other sites
noisy_lightning

noisy_lightning

Posted
Posted
Yup, I've been doing that since my days flying Falcon 4.0

 

The fun question is - do you map them as your numeric keypad is, or in the order they are on the UFC?

 

For me, I have it in order of the keyboard, as when I am writing down 9line co-ordinates and then typing them in from my kneeboard I default to data entry mode from work.

Link to comment
Share on other sites
Harker

Harker

Posted
Posted
The fun question is - do you map them as your numeric keypad is, or in the order they are on the UFC?

Numeric keypad. Used to do a lot of data entry at work (still do, on occasion) and it'd just glitch me out to swap them. I would use the UFC layout if I had a dedicated UFC panel though.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...