Jump to content

Any community binds for missing axis/switch controls?


Recommended Posts

Obviously we are in EA and I'm sure they will be added soon, but the F-15 has currently a poor selection of axes/switch binds available. Does anyone have any that they have created themselves to patch in for the moment?

Nothing by @Munkwolf so far. 

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

I have held back because I think we are having a "very early access" and there will be lots of additions by Razbam, but also I need to learn more about this bird..
But if you secifically list a reasonable number of high-priority items I might be tempted to get started.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

Well, off the top of my head there is all the lighting axis knobs, the radar and INS knob CW and CCW. 
Thanks for that. 

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

I took a shot at it and created axis commands for most of the rotating knobs. I added the lines below into the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-15E\Input\F-15E\joystick"

-- added HWF
-- Interior Lights
	{action = intlt_commands.console_lt_knob, cockpit_device_id = devices.INTLT, name = _('Console Lights Brightness Axis')},
	{action = intlt_commands.inst_pnl_lt_knob, cockpit_device_id = devices.INTLT, name = _('Instruments Panel Lights Brightness Axis')},
	{action = intlt_commands.ufc_bcklt_br_knob, cockpit_device_id = devices.INTLT, name = _('Gauges/UFC Backlights Brightness Axis')},
	{action = intlt_commands.chart_lt_knob, cockpit_device_id = devices.INTLT, name = _('Charts Spot Light Brightness Axis')},
	{action = intlt_commands.flood_lt_knob, cockpit_device_id = devices.INTLT, name = _('Storm FLood Lights Brightness Axis')},
	{action = intlt_commands.chart_lt_lamp, cockpit_device_id = devices.INTLT, name = _('Chart Spot Lamp Brightness Axis')},
-- Volume Knobs	
	{action = volctrl_commands.caution_vol, cockpit_device_id = devices.TEWS, name = _('Caution Volume Axis')},
	{action = volctrl_commands.launch_vol, cockpit_device_id = devices.TEWS, name = _('Launch Volume Axis')},
	{action = volctrl_commands.ics_vol, cockpit_device_id = devices.ICS, name = _('ICS Volume Axis')},
	{action = volctrl_commands.wpn_vol, cockpit_device_id = devices.PACS, name = _('WPN Voume Axis')},
	{action = volctrl_commands.ils_vol, cockpit_device_id = devices.ILS, name = _('ILS Volume Axis')},
	{action = volctrl_commands.tacan_vol, cockpit_device_id = devices.TACAN, name = _('TACAN Volume Axis')},
--UFC
	{action = ufc_commands.UFC_VOL_R1, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 1 Volume Axis')},
	{action = ufc_commands.UFC_VOL_R2, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 2 Volume Axis')},
	{action = ufc_commands.UFC_VOL_R3, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 3 Volume Axis')},
	{action = ufc_commands.UFC_VOL_R4, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 4 Volume Axis')},
	{action = ufc_commands.UFC_BRT_CTRL, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UFC LCD Brightness Axis')},

I did not test every item because I have only one slider I can mess with. Generally, they use only half of the available input signal range, and you need to invert them.
The lines need to be inserted in the axis commands part of the file near its end. I inserted them right underneath the line s for Hud Control.
The commands added to this file work only from the pilot's cockpit. If you want to use them also from the WSO cockpit, you need to add them the the file under "...\Mods\aircraft\F-15E\Input\F-15E_WSO\joystick", and you need to bind them again.
Anything else you want please let me know specifically by item. I did not find any missing knob for Radar and I did not find anything for INS.
My method works only for rotating knobs. If the cockpit has a rocker switch I cannot turn that into an axis.

  • Like 1
  • Thanks 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

That's great, thank you.

I used the lighting axes successfully. Full 0-100% of signal range so no need for any adjustment.

I would say, that I never put extra commands into the install folder default.lua files as they just get overwritten with every DCS update.  I always use - and can highly recommend that everyone does use - Quaggles injector mod for these binds. They are stored in Saved Games so never get touched.

Re the INS and radar knobs, are you saying that a bind has to exist to modify it?  New ones can't be created?

Currently, there is no radar knob CW or CCW bind, nor is there anything for the INS knob.

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

Follow up on this. Sorry, you were correct. Only 50% of range recognised.  I've noticed a couple of modules that are like this with lighting commands.  Already raised it with BN/NL.

Still, the way round that is as per the attached.

Regarding other binds (in addition to radar and INS already mentioned), ones that come to mind are - Formation, Position, and Warning/Caution Brightness. All lighting knobs.

sn.jpg


Edited by imacken
  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

2 hours ago, LeCuvier said:

I took a shot at it and created axis commands for most of the rotating knobs. I added the lines below into the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-15E\Input\F-15E\joystick"

-- added HWF
-- Interior Lights
	{action = intlt_commands.console_lt_knob, cockpit_device_id = devices.INTLT, name = _('Console Lights Brightness Axis')},
	{action = intlt_commands.inst_pnl_lt_knob, cockpit_device_id = devices.INTLT, name = _('Instruments Panel Lights Brightness Axis')},
	{action = intlt_commands.ufc_bcklt_br_knob, cockpit_device_id = devices.INTLT, name = _('Gauges/UFC Backlights Brightness Axis')},
	{action = intlt_commands.chart_lt_knob, cockpit_device_id = devices.INTLT, name = _('Charts Spot Light Brightness Axis')},
	{action = intlt_commands.flood_lt_knob, cockpit_device_id = devices.INTLT, name = _('Storm FLood Lights Brightness Axis')},
	{action = intlt_commands.chart_lt_lamp, cockpit_device_id = devices.INTLT, name = _('Chart Spot Lamp Brightness Axis')},
-- Volume Knobs	
	{action = volctrl_commands.caution_vol, cockpit_device_id = devices.TEWS, name = _('Caution Volume Axis')},
	{action = volctrl_commands.launch_vol, cockpit_device_id = devices.TEWS, name = _('Launch Volume Axis')},
	{action = volctrl_commands.ics_vol, cockpit_device_id = devices.ICS, name = _('ICS Volume Axis')},
	{action = volctrl_commands.wpn_vol, cockpit_device_id = devices.PACS, name = _('WPN Voume Axis')},
	{action = volctrl_commands.ils_vol, cockpit_device_id = devices.ILS, name = _('ILS Volume Axis')},
	{action = volctrl_commands.tacan_vol, cockpit_device_id = devices.TACAN, name = _('TACAN Volume Axis')},
--UFC
	{action = ufc_commands.UFC_VOL_R1, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 1 Volume Axis')},
	{action = ufc_commands.UFC_VOL_R2, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 2 Volume Axis')},
	{action = ufc_commands.UFC_VOL_R3, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 3 Volume Axis')},
	{action = ufc_commands.UFC_VOL_R4, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 4 Volume Axis')},
	{action = ufc_commands.UFC_BRT_CTRL, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UFC LCD Brightness Axis')},

I did not test every item because I have only one slider I can mess with. Generally, they use only half of the available input signal range, and you need to invert them.
The lines need to be inserted in the axis commands part of the file near its end. I inserted them right underneath the line s for Hud Control.
The commands added to this file work only from the pilot's cockpit. If you want to use them also from the WSO cockpit, you need to add them the the file under "...\Mods\aircraft\F-15E\Input\F-15E_WSO\joystick", and you need to bind them again.
Anything else you want please let me know specifically by item. I did not find any missing knob for Radar and I did not find anything for INS.
My method works only for rotating knobs. If the cockpit has a rocker switch I cannot turn that into an axis.

What about exterior lights, Formation, Position.  Thanks TC

  • Like 1

Win 10 Pro 64bit | Half X F/T Case | Corsair 1200AT ps | Asus ROG Maximums XIII Extreme | I9 11900K Clocked@4200 | Nepton 240 W/C | 64GB DDR4-3600 Gskill Mem | Asus 3080 gpu/8gb | SB-Z audio | Asus 32" 1440 Monitor | Winwing Super Tauras/Super Libra | Crosswind R/P | Track-ir-5 |

Link to comment
Share on other sites

Yep, I mentioned them above.

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

I tried putting in the Formation and Position lights, but although I got them to appear OK in the Axis Menu, they didn't work as well as expected . I think it's to do with the fact that they have discrete positions in the F-15 rather than the normal rotary knob.  But, on the other hand, it is probably me!

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

1 hour ago, imacken said:

Re the INS and radar knobs, are you saying that a bind has to exist to modify it?  New ones can't be created?

Currently, there is no radar knob CW or CCW bind, nor is there anything for the INS knob.

1. No, I'm saying that a "rotating knob" must be defined in the "clickabledata.lua".
2. There is already an axis binding for radar antenna elevation. What other radar commands are you looking for? Please state explicitly!
Edit:
To my surprise I could produce an axis binding for the INS Mode knob although it's really a multi-position switch:

{action = snsrctrl_commands.ins_knob, cockpit_device_id = devices.INS, name = _('INS Knob Axis')},

and same for the Radar Mode selector:

{action = snsrctrl_commands.rdr_power_sw, cockpit_device_id = devices.AN_APG70, name = _('Radar Mode Selector Axis')},

But I guess you are looking for CW/CCW button commands. Not sure if I can produce these. Will try.
 


Edited by LeCuvier
  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

The radar mode selection knob.  Currently there is only commands for individual positions, e.g. standby, on, etc., rather than the normal CW and CCW.  Same with the INS knob.


Edited by imacken
  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

28 minutes ago, imacken said:

The radar mode selection knob.  Currently there is only commands for individual positions, e.g. standby, on, etc., rather than the normal CW and CCW.  Same with the INS knob.

 

These CW/CCW commands are already there, they just have funny names like "AN/APG-70 Radar: OFF/STBY/ON/EMERG" and "AN/APG-70 Radar: EMERG/ON/STBY/OFF".
Same for INS mode. Problem is, these commands don't work. Bugs or WIP?

  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

53 minutes ago, imacken said:

I tried putting in the Formation and Position lights, but although I got them to appear OK in the Axis Menu, they didn't work as well as expected . I think it's to do with the fact that they have discrete positions in the F-15 rather than the normal rotary knob.  But, on the other hand, it is probably me!

Try these:

	{action = extlt_commands.formation_lt_knob, cockpit_device_id = devices.EXTLT, name = _('Formation Lights Axis Axis')},
	{action = extlt_commands.pos_lt_knob, cockpit_device_id = devices.EXTLT, name = _('Position Lights Axis')},

 

  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

10 hours ago, LeCuvier said:

Try these:

	{action = extlt_commands.formation_lt_knob, cockpit_device_id = devices.EXTLT, name = _('Formation Lights Axis Axis')},
	{action = extlt_commands.pos_lt_knob, cockpit_device_id = devices.EXTLT, name = _('Position Lights Axis')},

 

Yep, that's exactly what I tried, but as I said above, it doesn't work. I think it's to do with the dials being stepped in the F-15 rather than a normal full rotary.

 

10 hours ago, LeCuvier said:

These CW/CCW commands are already there, they just have funny names like "AN/APG-70 Radar: OFF/STBY/ON/EMERG" and "AN/APG-70 Radar: EMERG/ON/STBY/OFF".
Same for INS mode. Problem is, these commands don't work. Bugs or WIP?

Yes, I saw them yesterday, but couldn't get them to work. Seems to be a lot of binds not working atm on the F-15.

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

12 hours ago, LeCuvier said:

Edit:
To my surprise I could produce an axis binding for the INS Mode knob although it's really a multi-position switch:

{action = snsrctrl_commands.ins_knob, cockpit_device_id = devices.INS, name = _('INS Knob Axis')},

and same for the Radar Mode selector:

{action = snsrctrl_commands.rdr_power_sw, cockpit_device_id = devices.AN_APG70, name = _('Radar Mode Selector Axis')},

But I guess you are looking for CW/CCW button commands. Not sure if I can produce these. Will try.
 

 

Yes, that works. Well done!

However, for me, I would like CW and CCW commands for encoders rather than axes for these as I have run out of axes!


Edited by imacken

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

4 hours ago, imacken said:

...However, for me, I would like CW and CCW commands for encoders rather than axes for these as I have run out of axes!

 

Understood. But there is nothing I can do there. All the multiposition switches of the sensor panel have that problem. Probably due to WIP.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

On 7/4/2023 at 1:45 AM, imacken said:

Obviously we are in EA and I'm sure they will be added soon, but the F-15 has currently a poor selection of axes/switch binds available. Does anyone have any that they have created themselves to patch in for the moment?

Nothing by @Munkwolf so far. 

Started working on them this morning. Should have something later today or tomorrow.

  • Like 2
Link to comment
Share on other sites

5 hours ago, LeCuvier said:

Understood. But there is nothing I can do there. All the multiposition switches of the sensor panel have that problem. Probably due to WIP.

Yep, so many binds just not working atm.  Hopefully, we'll get an update soon.  Thanks for your efforts.

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

just committed my first pass at pilot seat binds: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/F-15E/Input/F-15E/joystick/default.lua

thank you to @shdwp for doing the initial commit and noticing the 'joystick abstractions' commands weren't bindable to keyboard and that it would be useful to be able to do so.

also kudos to razbam to quantizing some of the multiposition controls so they work ok with axis (fuel totalizer knob being the exception i noticed). some modules don't do this so it's nice when it is done. most have to be inverted and half saturation. i tested all of the custom axis binds - canopy lever and landing gear lever work well as axis. i haven't tested most of the custom button binds yet.

will cut an actual release on github this weekend after i do more testing get through the wso seat.

  • Like 1
Link to comment
Share on other sites

Great piece of work. Thanks.

Just a couple of things.  Firstly, the radar selection knob is missing from the axes.  I manually put it in for the moment as per @LeCuvier post earlier in this thread.

Wasn't sure what you meant by the 'kudos to razbam' para.  I still have to set all axis knobs to slider with a user curve starting at 50% for these new commands.

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

3 hours ago, imacken said:

Great piece of work. Thanks.

Just a couple of things.  Firstly, the radar selection knob is missing from the axes.  I manually put it in for the moment as per @LeCuvier post earlier in this thread.

Wasn't sure what you meant by the 'kudos to razbam' para.  I still have to set all axis knobs to slider with a user curve starting at 50% for these new commands.

thanks for the heads up. i will have an update later with the radar knob and some other fixes.

kudos part was for the controls quantizing properly with axis values. like with the radar selection and ins knobs. where on a rotary, they will snap to valid positions. compared to some other modules (or the fuel totalizer knob) where trying to use an axis doesn't snap to valid values and unusable with an axis no matter what is done with user curves.


Edited by Munkwolf
  • Like 1
Link to comment
Share on other sites

Got you!

 Thanks a lot. 

  • Like 2

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

2 hours ago, imacken said:

Got you!

 Thanks a lot. 

you're welcome! just pushed an update.

added radar mode knob to axis.

added proper controls for the canopy handle (locked/down/hold/up)

the relative controls for volume knobs and the nav flir brightness/gain are broken. I added 0%/33%/50%/66%/75%/100% absolute controls as a workaround for now (i use a 2x2 block of buttons with 0/33/66/100 options).

fix for where the binds for the fuel totals selector knob were offset by a position (i didn't realize BIT was negative value instead of 0).

added 'pressed' commands for the lighting knobs. Default is with 'down' where it changes by 10% per press instead of being able to hold down the button.

time to start on wso seat.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

@Munkwolf thank you for making this. I was looking through the joystick default.lua and saw an axis binding for radar mode selector. I didnt see any bindings at all for this setting. Is it referring to OFF/STBY/ON/EMERG knob? I wish there was a RADAR mode CW and CCW binding. Is it possible to add that? or perhaps an 'on else standby' as there is for the TF radar. Whichever is easier.


Edited by skypickle

4930K @ 4.5, 32g ram, TitanPascal

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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