Jump to content

Lights assigned by axis


Recommended Posts

  • 4 months later...

Frankly I’m getting more and more disappointed when it comes to the A-10C II. I thought we were getting a brand new version of the airplane. Instead we got the exact same thing with a HMCS and some new weapons. All other new ED modules have light axis. I think we can demand such a feature in a new module. 


Edited by JackFlash

My latest project, the Multi Function Button Box can be found at Kickstarter.

Link to post
Share on other sites
36 minutes ago, JackFlash said:

I thought we were getting a brand new version of the airplane.

 

Wasn't it always marketed as an upgrade rather than a built-from-scratch kind of new development? At least that was always my understanding.

 

It's also worth considering all the stuff more or less under the hood that's been updated, including simple things like switches with new default positions or the new initial viewpoint. And in terms of SA, I simply can't get over how brilliant the HMCS is. That alone would have been worth the upgrade to me. Add to that all the backports to the old A-10C (one) module, the FM updates, and the push to fix a lot of old bugs and fulfil old community requests, and I'd say ED did deliver what they promised, if not more.

 

Not saying your request is unreasonable. Just saying disappointment is a matter of perspective. And yeah, there's some ancient stuff still not addressed, but these days I'm enjoying the A-10C more than ever.

  • Like 1
Link to post
Share on other sites
  • 2 weeks later...

+1

 

However, if you want a solution that will tide you over until it happens:

 

1 - Find C:\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick\default.lua (or equivalent location for your installation).  Make a backup copy just in case.

2 - Open it, find the line:      axisCommands = {

3 - Add the following just below it:

 

-- extra axes
{action = 3011, cockpit_device_id  = 54, name = _('UHF Radio Volume Axis'), category = _('Extra - Radio Volumes')},
{action = 3005, cockpit_device_id  = 55, name = _('VHF AM Radio Volume Axis'), category = _('Extra - Radio Volumes')},
{action = 3005, cockpit_device_id  = 56, name = _('VHF FM Radio Volume Axis'), category = _('Extra - Radio Volumes')},

{action = 3005, cockpit_device_id  = 49, name = _('Flood Lights'), category = _('Extra - Lighting')},
{action = 3001, cockpit_device_id  = 49, name = _('Engine Inst Lights'), category = _('Extra - Lighting')},
{action = 3002, cockpit_device_id  = 49, name = _('Flight Inst Lights'), category = _('Extra - Lighting')},
{action = 3003, cockpit_device_id  = 49, name = _('Aux Inst Lights'), category = _('Extra - Lighting')},
{action = 3009, cockpit_device_id  = 49, name = _('Formation Lights'), category = _('Extra - Lighting')},
{action = 3006, cockpit_device_id  = 49, name = _('Console Lights'), category = _('Extra - Lighting')},

 

4 - Save it and try it out.  There should now be bind-able axes for radio volumes and the lights.  It is not perfect, though, as you'll need to mess about with custom curves to get something that behaves close to properly, but it is still a lot better than pressing and holding buttons in my opinion!

5 - The file may get replaced when updates happen, so either keep a copy to switch in manually, or use OVGME or something to turn it into a mod.

 

Now...  if they'd get the HSI course/heading knobs to be bind-able axes I'd really be delighted.  Tried the above approach with those and couldn't make it behave the way you'd expect.

Link to post
Share on other sites
3 hours ago, Seapiglet said:

+1

 

However, if you want a solution that will tide you over until it happens:

 

1 - Find C:\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick\default.lua (or equivalent location for your installation).  Make a backup copy just in case.

2 - Open it, find the line:      axisCommands = {

3 - Add the following just below it:

 

-- extra axes
{action = 3011, cockpit_device_id  = 54, name = _('UHF Radio Volume Axis'), category = _('Extra - Radio Volumes')},
{action = 3005, cockpit_device_id  = 55, name = _('VHF AM Radio Volume Axis'), category = _('Extra - Radio Volumes')},
{action = 3005, cockpit_device_id  = 56, name = _('VHF FM Radio Volume Axis'), category = _('Extra - Radio Volumes')},

{action = 3005, cockpit_device_id  = 49, name = _('Flood Lights'), category = _('Extra - Lighting')},
{action = 3001, cockpit_device_id  = 49, name = _('Engine Inst Lights'), category = _('Extra - Lighting')},
{action = 3002, cockpit_device_id  = 49, name = _('Flight Inst Lights'), category = _('Extra - Lighting')},
{action = 3003, cockpit_device_id  = 49, name = _('Aux Inst Lights'), category = _('Extra - Lighting')},
{action = 3009, cockpit_device_id  = 49, name = _('Formation Lights'), category = _('Extra - Lighting')},
{action = 3006, cockpit_device_id  = 49, name = _('Console Lights'), category = _('Extra - Lighting')},

 

4 - Save it and try it out.  There should now be bind-able axes for radio volumes and the lights.  It is not perfect, though, as you'll need to mess about with custom curves to get something that behaves close to properly, but it is still a lot better than pressing and holding buttons in my opinion!

5 - The file may get replaced when updates happen, so either keep a copy to switch in manually, or use OVGME or something to turn it into a mod.

 

Now...  if they'd get the HSI course/heading knobs to be bind-able axes I'd really be delighted.  Tried the above approach with those and couldn't make it behave the way you'd expect.

Awesome! I have to try this out. 
Regarding the HSI since there is no limit to the turn of the CRS-nob I don’t think this ever will be possible. 

My latest project, the Multi Function Button Box can be found at Kickstarter.

Link to post
Share on other sites

True, the A-10C II has only a very minimal set of axis commands.

It also lacks commands like Clockwise/Counterclockwise (1 step at a time) for some of its multi-position switches.

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 post
Share on other sites

+1

To add a few more to what Seapiglet already gave - if you really have too many pots to spare 😉

 

{action = 3007, cockpit_device_id = 5, name = _('RWR Volume Knob')},
{action = 3016, cockpit_device_id = 58, name = _('TACAN Audio Volume')},
{action = 3014, cockpit_device_id = 58, name = _('ILS Audio Volume')},

 

I haven't checked all these axes for the Hawg, but at least most of them (if not all) will require settings ("Axis Tune") as in the picture below.

 

P.S. If you lack axes in any plane, it's good to go to clickabledata.lua and see what's there. Some planes acutally do have lots of axes, but they're not "dragged out" into \input\joystick\ files. For instance, Mi-8 has quite a lot of them, but they're buried in the clickabledata.lua.

 

curve.png

  • Thanks 1

i7-8700K GTX1060(6GB) 16GB 27"@1080p TM Hawg HOTAS TPR TIR3 SD-XL button/pot box
UH1 Mi8 Ka50 AJS37 10CII 18 5 86 MiG15 109 Spit 51 47 A8 superc. PG NTTR Norm. Channel

Link to post
Share on other sites
  • 4 weeks later...

Hello !

 

How do you determine or find the code to use for the "action" label ?

 

For example :

 

{action = 3005, cockpit_device_id  = 55, name = _('VHF AM Radio Volume Axis'), category = _('Extra - Radio Volumes')},
{action = 3005, cockpit_device_id  = 56, name = _('VHF FM Radio Volume Axis'), category = _('Extra - Radio Volumes')},

{action = 3005, cockpit_device_id  = 49, name = _('Flood Lights'), category = _('Extra - Lighting')},

 

Il I look into the vanilla default.lua, the only reference I can find is about seat elevation :

 

--Seat Adjustment
{down = 3004, up = 3004, cockpit_device_id = 39, value_down = -1.0,    value_up = 0.0, name = _('Seat Adjustment Up'), category = _('Systems')},
{down = 3005, up = 3005, cockpit_device_id = 39, value_down = 1.0,    value_up = 0.0, name = _('Seat Adjustment Down'), category = _('Systems')},

 

Not so much relation with Radio buttons nor Flood Lights ^^

 

I tried to understand how to change the same for another plane (C-101 by instance) and add some more axis for rotaries or sliders.

 

Thanks !

 

[sIGPIC][/sIGPIC]

Link to post
Share on other sites

for the "action" code you open "clickabledata.lua". Find the command and its button number. Add 3000 to the button number. That's yur action code.

For the cockpit_device_id code: note the mnemonic device_id from "clickabledata.lua". Open "devices.lua" and look for that device. At the end of its line you will find a number. That's your numeric cockpit_device_id.

Both .lua files are usually in "...\Cockpit\Scripts", for some modules in ...\Cockpit\.

  • Thanks 2

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 post
Share on other sites

Read here this morning and decided to just do all the rotary knobs (including lights panel) but forgot to cross-post here when i was done.

 

 

Hopefully caught them all 🙂 Still +1 on OP to have ED include it so nobody needs to crawl lua files and care for updates resetting them.

bts_100.jpg.22eae5ddd2a463fc09375990ad043870.jpg

 

Hardware: MSI B450 Gaming Plus MAX | Ryzen 5 3600X (6*3.8 Ghz) | 32 GB RAM | MSI Radeon RX5700 | Samsung SSD 860 QVO 1TB | DCS dedicated @ WD Blue 500 GB SSD | Win 10 (64-bit) | TM Warthog HOTAS, MFD and rudder pedals, TrackIR5

 

Wishlist:  Northern Germany/Baltic Sea theater | Full Fidelity Su-25A | Asset packs (80s Iran, Lebanon 1982, Syria 2011+ factions)

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...