Jump to content

How to set up toggle switches (a tutorial)


Recommended Posts

  • 2 weeks later...

Hi all, I would like to do the same type of hold button for on type mapping, but when I go to

 

C:\Users\[NAME]\Saved Games\DCS\Config\Input\A-10C\joystick

 

and open up the .LUA file corresponding to the particular Bodnar input board, which is

 

Button Box Interface BBI-64 {EC6A0470-1BF1-11e9-8001-444553540000}.diff.lua

 

the contents of the file look nothing like the code that you are quoting like

 

{down = iCommandPlane_APU_Off, name = "APU Off", category = "Engine Control Panel"},
{down = iCommandPlane_APU_Start, name = "APU Start", category = "Engine Control Panel"},
{down = iCommandPlane_APU_Start, up = iCommandPlane_APU_Off, name = "APU Start/Off", category = "Engine Control Panel"},

 

Instead, this is what it looks like

 

		},
	["a2004cdnil"] = {
		["name"] = "Throttle Both",
		["removed"] = {
			[1] = {
				["key"] = "JOY_Z",
			},
		},
	},
},
["keyDiffs"] = {
	["d1071pnilunilcdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN25",
			},
		},
		["name"] = "APU generator power",
	},
	["d1072pnilunilcdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN19",
			},
		},
		["name"] = "Emergency flood",
	},
	["d1073pnilunilcdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN17",
			},
		},
		["name"] = "Battery power",
	},
	["d1074pnilunilcdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN21",
			},
		},
		["name"] = "Inverter STBY",
	},
	["d1075pnilunilcdnilvdnilvpnilvunil"] = {
		["added"] = {
			[1] = {
				["key"] = "JOY_BTN13",
			},
		},

 

Either I have the wrong file or something has been changed in the way the files are set up, as the original instructions don't appear (to me at least) to cover the content of the file I'm seeing. Can anyone confirm that it's the correct file?

 

By the way, this was opened in Notepad++

 

Cheers

 

Les


Edited by lesthegrngo
Link to comment
Share on other sites

You are looking at the wrong file. You should be looking at the "default.lua" under "...DCS World OpenBeta\Mods\aircraft\A-10C\Input\A-10C\joystick".

The .diff.lua files under "Saved Games" record the bindings you have added or removed via Options/Controls.

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

I haven't seen any recent post from the author of post #1 so I assume he is no longer active, and I cannot modify someone else's post. Note there is a tutorial document under post #214.

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

Thanks - the 14 page tutorial deals with lots of examples, except for the A10-C! It has some great information but I was looking for an example to use for learning purposes.

 

I would like to know if, for example, the APU Generator can be made to perform as being on while in X position, then off when moved away from that position

 

 

The code in the .LUA is this

 

{down = iCommandAPUGeneratorPower, name = _('APU generator power'), category = _('Electrical power control panel')},

 

I tried this without success

 

{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPower, name = _('APU generator power'), category = _('Electrical power control panel')},

 

and this (also without success)

 

{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPowerOFF, name = _('APU generator power'), category = _('Electrical power control panel')},

 

Clearly I am not getting the syntax or idea correct. What would be the correct way to write it for this switch?

 

Cheers

 

Les

Link to comment
Share on other sites

The file for the TM Warthog throttle is "Throttle - HOTAS Warthog.lua".

It has this code for the APU switch:

{combos = {{key = 'JOY_BTN20'}}    , down = iCommandPlane_APU_Start            , up = iCommandPlane_APU_Off                       , name = _('APU Start/Off')                        , category = _('Engine Control Panel')};

The part "combos = {{key = 'JOY_BTN20'}} ," produces a default binding to the APU switch on the TM WH throttle. For use with your button box you should leave that out and use this:

{down = iCommandPlane_APU_Start, up = iCommandPlane_APU_Off, name = _('APU Start/Off'), category = _('Engine Control Panel')};

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

Ok, I think we may be at crossed purposes here, the switch I am referring to is on the Electrical power control panel

 

--Electrical power control panel
{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPower, name = _('APU generator power'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterSTBY						, name = _('Inverter STBY'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterOFF						, name = _('Inverter OFF'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterTEST,up = iCommandElectricalPowerInverterOFF, name = _('Inverter TEST'), category = _('Electrical power control panel')},
{down = iCommandEmergencyFlood									, name = _('Emergency flood'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorLeft								, name = _('AC generator power left'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorRight								, name = _('AC generator power right'), category = _('Electrical power control panel')},
{down = iCommandBatteryPower									, name = _('Battery power'), category = _('Electrical power control panel')},

 

 

The APU on / off is already serviced by a two position switch on the HOTAS, whereas the electrical panel is a set of six toggle switches, and the in game binding for the APU generator is an on / off toggle switch, press once for on, press again for off. I want to use a two position switch, so when the switch is in a particular position it will turn the APU gen on, and when moved away it is off.

 

If you want, use the 'BATTERY PWR' switch as an example, it is functionally the same

 

Cheers for your help!

 

Les

Link to comment
Share on other sites

You are right, I wasn't paying attention. But here is a whole litany of 2- and 3-position commands I created over time - some for myself and some for other gamers. Some of the Electrical Power Control Panel commands are included.

{down = iCommandPlaneAHCPGUNPACArm, up = iCommandPlaneAHCPGUNSafe, name = _('GUN/PAC switch 2-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')},
{down = iCommandPlaneAHCPGUNPACArm, up = iCommandPlaneAHCPGUNSafe, name = _('GUN/PAC switch 3-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')},
{down = iCommandPlaneAHCPGUNArm, up = iCommandPlaneAHCPGUNSafe,    name = _('GUN/PAC switch 3-Pos GUNARM/SAFE'), category = _('Armament HUD Control Panel')},

{down = iCommandPlaneAHCPLaserArm, up = iCommandPlaneAHCPLaserSafe, name = _('LASER switch 2-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')},
{down = 3004, up = 3004, cockpit_device_id = 7 , value_down = 1.0, value_up = -1.0, name = _('TGP switch 2-Pos ON/OFF'), category = _('Armament HUD Control Panel')},
{down = iCommandPlaneAHCPIFFCCOn, up = iCommandPlaneAHCPIFFCCTest, name = _('IFFCC switch 2-Pos ON/TEST'), category = _('Armament HUD Control Panel')},
{down = iCommandPlaneAHCPMasterArm, up = iCommandPlaneAHCPMasterSafe,name = _('Master switch 3-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')},
{down = iCommandPlaneAHCPMasterTrain, up = iCommandPlaneAHCPMasterSafe, name = _('Master switch 3-Pos TRAIN/SAFE'), category = _('Armament HUD Control Panel')},
{down = 3006, up = 3006, cockpit_device_id = 7 , value_down = 1.0, value_up = 0.0, name = _('AHCP HUD Mode 2-Pos DAY/NIGHT'), category = _('Armament HUD Control Panel')},

{down = 3007, up = 3007, cockpit_device_id = 49 , value_down = 1.0, value_up = 0.0, name = _('Emergency Flood Light 2-Pos DAY/NIGHT'), category = _('Electrical power control panel')},
{down = 3007, cockpit_device_id = 49 , value_down = 1.0, name = _('Emergency Flood Light DAY'), category = _('Electrical power control panel')},
{down = 3007, cockpit_device_id = 49 , value_down = 0.0, name = _('Emergency Flood Light NIGHT'), category = _('Electrical power control panel')},
{down = 3001, up = 3001, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('APU Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = 3004, up = 3004, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('AC Gen Left Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = 3005, up = 3005, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('AC Gen Right Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = 3006, up = 3006, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('Battery Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},

-- Landing/Taxi Lights 3-Position
{down = iCommandPlaneLGPLandLight, up = iCommandPlaneLGPLightsOff, name = _('Landing Lights ON/OFF'), category = _('Landing gear panel')},
{down = iCommandPlaneLGPTaxiLight, up = iCommandPlaneLGPLightsOff, name = _('Taxi Lights ON/OFF'), category = _('Landing gear panel')},

{down = 3012, up = 3012, cockpit_device_id = 49, value_down = 1.0,    value_up = -1.0, name = _('Nose Light 2-Pos switch ON/OFF'), category = _('Lighting Panel')},
{down = 3004, up = 3004, cockpit_device_id = 49, value_down = 1.0,    value_up = -1.0, name = _('Accel & Compass Light 2-Pos Bright/DIM'), category = _('Lighting Panel')},
{down = 3013, up = 3013, cockpit_device_id = 49, value_down = 1.0,    value_up = -1.0, name = _('Signal Lights 2-Pos BRIGHT/DIM'), category = _('Lighting Panel')},

{down = 3029, pressed = 3029,up = 3028, up = 3028, cockpit_device_id = 38, value_down = 1.0, value_pressed = 0.0, value_up = 1.0, value_up = 0.0, name = _('Anti-Skid 2-Pos ON/OFF'), category = _('Landing gear panel')}, -- heureka, this works!
{down = 3029, pressed = 3029, cockpit_device_id = 38, value_down = 1.0, value_pressed = 0.0, name = _('Anti-Skid Button ON'), category = _('Landing gear panel')},
{down = 3028, pressed = 3028, cockpit_device_id = 38, value_down = 1.0, value_pressed = 0.0, name = _('Anti-Skid Button OFF'), category = _('Landing gear panel')},

I hope this helps you.

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

Yes, that was extremely helpful - there are a number of ideal examples in there and using this and cross referencing the other data, I think I can at least start having a proper go. I hope to report some success shortly

 

Again, many thanks for your help and patience

 

Les

Link to comment
Share on other sites

One further question, the new code replaces the old, correct? so if I put in

 

{down = 3006, up = 3006, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('Battery Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},

 

I have to delete the associated line

 

{down = iCommandBatteryPower, name = _('Battery power'), category = _('Electrical power control panel')},

 

I don't want to delete the line even if it appears to work only to find that there is a hidden effect that causes other issues

 

Cheers

 

Les


Edited by lesthegrngo
Link to comment
Share on other sites

There is no need to delete the original line.

However, the name of the added command must be different from the original command(s).

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

No. That's not the name of the binding. I mean the content of the "name" field, like "Battery Power 2-Pos ON/OFF"

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

Hi again

 

Sorry for the delay in responding. I spliced in the code that you gave as examples to test this, on the A10C config, but it isn't functioning. This is how I have inserted the code (obviously the rest of the .lua file is untouched)

 

--Electrical power control panel
{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPower, name = _('APU generator power'), category = _('Electrical power control panel')},
{down = 3001, up = 3001, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('APU Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterSTBY						, name = _('Inverter STBY'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterOFF						, name = _('Inverter OFF'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterTEST,up = iCommandElectricalPowerInverterOFF, name = _('Inverter TEST'), category = _('Electrical power control panel')},
{down = iCommandEmergencyFlood									, name = _('Emergency flood'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorLeft								, name = _('AC generator power left'), category = _('Electrical power control panel')},
{down = 3004, up = 3004, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('AC Gen Left Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorRight								, name = _('AC generator power right'), category = _('Electrical power control panel')},
{down = 3005, up = 3005, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('AC Gen Right Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandBatteryPower									, name = _('Battery power'), category = _('Electrical power control panel')},
{down = 3006, up = 3006, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('Battery Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},

 

I'm pretty certain that I have put it in correctly, but would appreciate a quick look for anything obvious

 

I also tried it with the value_up command value set to -1.0, again, it didn't work

 

Thanks

 

Les


Edited by lesthegrngo
Link to comment
Share on other sites

You have apparently inserted the added lines between existing lines for the electrical power control panel. That is not a good practice in terms of maintenance. It's better to add the new bindings in a block close to the beginning (or the end) of the key commands in the file as explained in the tutorial. But that is not the reason why it's not working for you.

You do not describe what's not working, so I cannot determine with certainty what the cause is.

However, there is definitely a problem with your first line:

{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPower, name = _('APU generator power'), category = _('Electrical power control panel')},

1. You have created a new command but it has the same name as the existing command ("APU generator power"). As I said: you must not duplicate command names. It produces a conflict.

2. Even if you changed the command name, the command would not be good. It would toggle when you switch ON and toggle again when you switch OFF. Depending on the state of the cockpit pit switch and the state of your button box switch at mission start, the two switched could be out of sync. I recommend you get rid of that line altogether and try again.

 

If you want me to check more, post your file so I can see what happens on my rig.

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

Thanks for looking at this ***EDIT**** it has just occurred to me that you may not have realised that I am making my own cockpit simulator and so the intent is to actually replicate the physical movement of a real toggle switch - photo of my actual switch panel attached now

 

I confess to being totally confused. The script I used was what you posted before, albeit in a different order, thinking it was a working example. In each case this is what I desire to happen.

 

example - battery power switch

 

The physical switch I have in my real world cockpit is a two position toggle switch. When the switch is in the 'up' position, it is energised, when in the down position it is de-energised. The 'up' position corresponds to 'BATTERY ON', the 'down' position to 'BATTERY OFF'.

 

The intent is that when I put my real toggle switch in the 'up' position, the in game on screen switch should move to the 'BATTERY ON' position, and stay there until I move my real world switch to the 'down' position, and the on screen switch should then move to the 'BATTERY OFF' position.

 

In actual fact, what happens is that starting with my real world switch in the 'down' position, when I move it to the 'up' position, the in game effect is that the on screen toggle switch moves to the opposite position to which it was in, ie when I move my real switch to 'up', if the on screen toggle switch was in the 'BATTERY ON' position, it will move to the 'BATTERY OFF' position and vice versa. When I move my physical switch from the 'up' position to the 'down' position, nothing at all happens. Effectively the real world toggle switch is still being read as a momentary press button switch.

 

As for renaming, again I am really confused - when I look at the names in there I see 'AC generator power right' on one line and 'AC Gen Right Power' on the next line, which to me look like different names. The second one is the same as your example, so again I thought that it was one that was correct or at least OK to use.

 

I hope that I'm explaining this satisfactorily, it's tricky to explain my thoughts sometimes!

 

Cheers

 

Les

20200626_135952.thumb.jpg.04e87cf6bdb5b2a09d4d0c008ff2a09e.jpg


Edited by lesthegrngo
Link to comment
Share on other sites

I'll just focus on these 2 points:

1. Battery Power Switch

If you have bound (in Controls/Options) your button box switch to "Battery Power 2-Pos ON/OFF" then the command should just work as you desire. I have just re-tested the command in my system, and there is no way it can behave as you describe. Even if the physical and the Sim switch are in opposite position at mission start, they will synchronize.

2. Name duplication:

I don't understand why you argue about the "AC Gen Right Power". I never referred to that. I referred only to this line:

{down = iCommandAPUGeneratorPower,up = iCommandAPUGeneratorPower, name = _('APU generator power'), category = _('Electrical power control panel')},

That line is not in the original file so I assumed that you added it, and that would have duplicated the name. But it seems that you actually modified the line, adding "

up = iCommandAPUGeneratorPower," and that would actually produce the behavior where it doesn't synchronize with your physical switch.

 

 

PS: all the commands I posted have been tested in the system, and most are currently used in my set-up.


Edited by LeCuvier

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

Bizarre - I did not add the extra line, and I have just checked the unmodified .bak file I created before starting an it is in there too. I can only assume that at some point in the past I have done something

 

Let me have another go taking out those parts you state and the spurious repeated section

 

Cheers

 

Les

Link to comment
Share on other sites

Well, I think I found why - you stated this

 

"If you have bound (in Controls/Options) your button box switch to "Battery Power 2-Pos ON/OFF"" and I was thinking to myself that I hadn't ever seen that option. When I went to controls setup, sure enough it wasn't there.

 

I did some digging around, and I can only conclude that at some point the game had been taken off simulation mode, as when I went and made sure all the advanced options were checked, the 2 position option is now visible. When the game updates does it change these setting, as I had set them to simulator mode previously.

 

This throws up an interesting point, which is if you are unaware of the existence of something you are unlikely to check it! Now that I know that it is there I have tried to assign the cockpit button to it, but now it will only allow me to assign it to a button on the HOTAS, and won't let me assign it to the Bodnar boards. That's a completely different question that I will take elsewhere, as (I don't think) it's anything to do with modifying the .lua script

 

Cheers

 

Les

Link to comment
Share on other sites

Here is a video showing the behaviour I am describing, I will try and attach the .lua file as well

 

 

.lua file now attached

 

Cheers

 

Les

As requested, I've had a look at this too.

I don't have a HOTAS connected, so editing the file you linked doesn't help me.

 

I added these to the A10's default.lua file:

{down = 3001, up = 3001, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('TIM APU Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorLeft, up = iCommandPowerGeneratorLeft, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('TIM LEFT MAIN Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorRight, up = iCommandPowerGeneratorRight, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('TIM RIGHT MAIN Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},

So the Electrical power control panel section now looks like this:

-Electrical power control panel
{down = iCommandAPUGeneratorPower								, name = _('APU generator power'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterSTBY						, name = _('Inverter STBY'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterOFF						, name = _('Inverter OFF'), category = _('Electrical power control panel')},
{down = iCommandElectricalPowerInverterTEST,up = iCommandElectricalPowerInverterOFF, name = _('Inverter TEST'), category = _('Electrical power control panel')},
{down = iCommandEmergencyFlood									, name = _('Emergency flood'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorLeft								, name = _('AC generator power left'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorRight								, name = _('AC generator power right'), category = _('Electrical power control panel')},
{down = iCommandBatteryPower									, name = _('Battery power'), category = _('Electrical power control panel')},

{down = 3001, up = 3001, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('TIM APU Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorLeft, up = iCommandPowerGeneratorLeft, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('TIM LEFT MAIN Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},
{down = iCommandPowerGeneratorRight, up = iCommandPowerGeneratorRight, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('TIM RIGHT MAIN Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')},

 

When I fire up DCS and look at the A10 controls in the Electrical power control panel section, I see 3 new controls:

TIM APU Gen Power 2-Pos ON/OFF

TIM LEFT MAIN Gen Power 2-Pos ON/OFF

TIM RIGHT MAIN Gen Power 2-Pos ON/OFF

 

I assigned buttons 5,6 and 7 of my T16000M joystick to those controls.

 

See attachment.

 

When I run DCS, the switches turn on when I press the button and off when I release it.

I even tried firing up with one pressed in case it would go out of sync, but it didn't.

 

 

EDIT: This may answer your last question about not allowing assignment to the Bodnar board.

2036442752_luacontrols.thumb.png.155c43c1068b803dd918ba2cf40663c4.png

Link to comment
Share on other sites

So the 2 position control selection only appears if you have changed the .lua file?

 

 

**Edit**

 

I cleared the assignments of those controls, but all the control input options are greyed out apart from the Warthog HOTAS column. None of the other input devices are selectable, even if I set all the switches to non-assigned positions and restart

 

Cheers

 

Les


Edited by lesthegrngo
Link to comment
Share on other sites

So the 2 position control selection only appears if you have changed the .lua file?

 

 

**Edit**

 

I cleared the assignments of those controls, but all the control input options are greyed out apart from the Warthog HOTAS column. None of the other input devices are selectable, even if I set all the switches to non-assigned positions and restart

 

Cheers

 

Les

They wouldn't show up at all for me when I only edited the HOTAS file. - I don't have a HOTAS attached.

I think that if you only edited the HOTAS file, they'll only be available for assignment to HOTAS buttons. Try doing the edits to the default file. That worked for me.

Link to comment
Share on other sites

Thanks for this No1sonUK - with the default.lua file modified I now have the toggle switches working as they should and in line with LeCuvier's description

 

There were some huge gaps in my understanding, and I hadn't grasped that once it was modified in the .lua file that it then had to be selected in game, and of course being set to something other than sim didn't help

 

So I have to thank Fusedspine33, LeCuvier and No1sonUK for their patience and inputs here and behind the scenes, now I have a better grasp on how this functions I can go on to set other controls

 

Cheers again for all the help

 

Les

Link to comment
Share on other sites

  • Recently Browsing   0 members

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