Baldawg

this is a bug im sure. i have created a new default lua that has new "special MFD and PMFD bindings". This will allow you to bind to buttons 19 and 20 for the PMFD

Ok couldnt help myself. I added special bindings for the MFDs/PMFD so that the button moves when being pressed by your simpit mfd (if you have them)i prefixed the new edits with Special so they are easy to find. here is the new lua below. I may do more editing later to other bindings. default.lua

here is the new default.lua. as promised.... Im in the process of troubleshooting the MFD/PMFD buttons not moving in game when pressing simpit button...may have to write new code for those too!!!

i actually dont have control sync turned on due to it causing issues when respawning and shutting the jet down potentially. as for your issue with the idle/off position being opposite....i do intend to try to resolve this as ive seen this occur with the landing/taxi light switches well. on the ground it works fine but it seems once in the air it changes states and acts as a toggle which i cant re-sync by a mouse click. your lines of code separate the values for the binding so that wont help since you only have one button associated with the throttle idle. give me a few minutes to look at it and ill write up something to try out.

The default.lua file resides here: C:\Users\Yourname\Saved Games\DCS\Mods\Aircraft\F-22A\Input\F-22A\Joystick

Here are the final edits to the default.lua for anyone interested. The Nav light 5 position switch and Emergency Jettison work as you would expect. The other potentiometer type lighting control knobs are only on or off. im sure that there is more coding in the module that is required to make them work with encoders or pots. Ill post the code below as well as make my default.lua available. {down = 3003, cockpit_device_id = 2, value_down = 0.0, name = _('NAV Lights OFF'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.1, name = _('NAV Lights ANTICOL'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.2, name = _('NAV Lights POS/ANTICOL'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.3, name = _('NAV Lights POS FLASH'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.4, name = _('NAV Lights POS STEADY'), category = _('F-22A Systems')}, {down = 3002, cockpit_device_id = 2, value_down = 1.0, name = _('AAR Lights ON'), category = _('F-22A Systems')}, {down = 3002, cockpit_device_id = 2, value_down = -1.0, name = _('AAR Lights OFF'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 1, value_down = 1.0, name = _('MFD Lights ON'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 1, value_down = -1.0, name = _('MFD Lights OFF'), category = _('F-22A Systems')}, {down = 3004, cockpit_device_id = 1, value_down = 1.0, name = _('INST Lights ON'), category = _('F-22A Systems')}, {down = 3004, cockpit_device_id = 1, value_down = -1.0, name = _('INST Lights OFF'), category = _('F-22A Systems')}, {down = 3005, cockpit_device_id = 1, value_down = 1.0, name = _('CONSOLE Lights ON'), category = _('F-22A Systems')}, {down = 3005, cockpit_device_id = 1, value_down = -1.0, name = _('CONSOLE Lights OFF'), category = _('F-22A Systems')}, {down = 3006, cockpit_device_id = 1, value_down = 1.0, name = _('FLOOD Lights ON'), category = _('F-22A Systems')}, {down = 3006, cockpit_device_id = 1, value_down = -1.0, name = _('FLOOD Lights OFF'), category = _('F-22A Systems')}, {down = 3075, cockpit_device_id = 1, value_down = 1.0, name = _('FORM Lights ON'), category = _('F-22A Systems')}, {down = 3007, cockpit_device_id = 1, value_down = -1.0, name = _('FORM Lights OFF'), category = _('F-22A Systems')}, {down = 3002, up = 3002, cockpit_device_id = 4, value_down = 1.0, value_up = 0.0, name = _('Emergency Jettison'), category = _('F-22A Systems')}, EDIT: added updated file below default.lua

Success!!!! here are the first working additions for those that would like to use their simpits to control more of the Raptors systems..... {down = 3003, cockpit_device_id = 2, value_down = 0.0, name = _('Navigation Lights OFF'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.1, name = _('Navigation Lights ANTICOL'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.2, name = _('Navigation Lights POS/ANTICOL'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.3, name = _('Navigation Lights POS FLASH'), category = _('F-22A Systems')}, {down = 3003, cockpit_device_id = 2, value_down = 0.4, name = _('Navigation Lights POS STEADY'), category = _('F-22A Systems')},

some success upon further digging, i was able to implement this code without it breaking the lua, im sure that the keypad on the ICP is for looks at this point since it wasn't implemented to work in the first place. I will be investigating further with known working elements ie the exterior and interior lighting panels. More to follow..... {down = 3017, up = 3017, cockpit_device_id = 7, name = _('ICP 1 PNT'), category = _('F-22A ICP')}, I was able to bind a button however, i see no response in game of the 1 button on the ICP when pressing said simpit butt i did notice that even when im pressing the MFD buttons ive bound to my cougar mfds the in game buttons don't show them being pressed. they are working however, not sure if this is a limitation due to it being a mod.

Love this mod....very impressed with the level of interaction and complexity that has been created. Im a home simpit builder and i always try to dig into the default.lua when i get my hands on a new module to make my simpit as usable as i can. With that said, i have tried to implement more keybinds for the Raptor to make it more user friendly for me however, the usual editing im able to do with other lua's is breaking this default.lua. Here is an example below where i added the 1 btn from the ICP to see if it would work. {down = device_commands.Button_17, up = device_commands.Button_17, cockpit_device_id = devices.ICP_SYSTEM, value_down = 1, value_up = 0, name = _('ICP_1_PNT'), category = _('F-22A ICP')}, Im sure ,if this is possible, without having more coding done deeper within the F-22, if so i would love to contribute to the cause for other simpit folks as i and many others have for many other modules in the DCS eco system.

I have this issue as well. The only wireless device i have is a logitech mouse. All devices have their sleep functions turned off and allow device to wake pc enabled. This seems to be some sort of issue embedded in DCS. To add to what ive done, ive disabled al power management features in the Device manager for every USB device that i have. This is annoying because it requires you to cycle a switch to get the sim to recognize it but in turn renders it out of sync to what the physical switch position and the in game position are at.

Im assuming this mod is to be installed in the saved games folder for DCS.

+1

Thats been done....unfortunately i dont think there is an easy resolution to my problem.

As the title states my USB devices timeout after an unknown period of time. What im experiencing is at the beginning of a flight i will flip a switch in my pit to activate something in the sim (ex. position lights) and the switch in the game moves as directed. However, after a while when i flip the same switch it doesnt react in the sim until i flip the switch forward again. this happens on all of my Bodnar boards, TM HOTAS etc. Has anyone seen this issue before? Im using two 7 port USB hubs with selective suspend disabled. all hardware is in signature. Ive searched for a solution online related to DCS and/or windows but cant seem to find anyone else that has had this problem. Im leaning towards it being a DCS issue with polling usb devices or something like that.

#27732 bricked yesterday. plugged into 3.0 usb powered hub. unplugged my pc and all devices from power outlet in case a rogue thunderstorm popped up when i was out of town. Got in the pit yesterday evening to enjoy the A-10C II and noticed the APU switch wasnt working. Hadnt even noticed until then that the LEDs were off. Browsed the forums, went through the troubleahooting from TM and came to the conclusion it is a bad mobo. Going to send off the PCB to Canada for a repair....possibly purchase a new one from TM for a spare...... if i ever here back from them.

Will we have caution and warning sounds played through the headset as the A10, F18 etc do? When ED finally added two audio channels this became possible. The external audio sounds play through my speakers and comms and caut/warn sounds through my headset with these aircraft. Just curious if this is even being considered.

MP3 play through headset??????? Is this in the works or even possible? i use external speakers for external sounds and headset for the obvious Commms side of DCS. Since ED made the audio split (THANK GOD it finally happened!!!), Bitchin betty screams in your headset as she should......and so should heavy metal music.....LOUD!

How extensive will the keybinds be on release? Will those of us with simpits have everything available to bind to switches and rotaries in our simpits?

Autopilot is working, The AFC switch to the right of the ALT hold has to be engaged before the ALT hold switch will lock.

Everytime you update dcs it creates a backup folder of all.the files that arent native to DCS. Just copy the folders in the backup folder and paste into the dcs directory. Boom all.of your cut and paste default.lua are loaded back in. No need for ovgme

not sure how someone could gain an edge (pun intended) with an unencrypted clickabledata.lua file but ok....if all clickable items are in the default.lua i can setup that so my pit will work....hope that is something theyd consider doing sometime.....thanks for the reply and thank you guys for your work!

Simpit guy here....was curious about editing the default.lua so i could add the fuel selector, mag switch, boost switch etc to bind to a switch in my simpit....unfortunately the clickabledata.lua file is encrypted. I also noticed that mixture isnt a bindable axis as well. Why the encryption and would it be possible to add keybinds for controllers for all clickable cockpit functions?

Bump

I have this same exact issue. Ive tried using long press and another suggestion to no avail. Something changed in dcs windows or rsmapper that doesnt allow the repeat funtion to work.

+2 on that SGT. You and I both have sounded the alarm on RAZBAMs saga of illegitimate keybind babies. They obviously have too much going on building other incomplete modules to fix the already released. It seems that they see our complaints as insignificant as the mouse funtionality in the clickable cockpit works as designed. Who cares about the guys that have simpits.