Baldawg

I concur.....even though the M2000 is still in Beta and we are Lua hacking that as we speak......its not playing nice at all. this should be a no brainer for every sim. (can you say FSUIPC)

Bro......I didn't use your guess, i simply fixed something that was already there. the keyboard LCtrl + LShft + B works the switch. i found it in the keyboards default lua and made the correction to the joystick default lua and bam it works as intended. as far as reporting back, trying to add other switches with the "toggle" feature (ie Electric Transfer switch, Alternator 1 and 2, Hydraulic Emergency Pump, etc) is the issue that stands. im trying a few different things but they aren't showing up in the options controls menu after i implement them. still trying though. Heres an example code {down = device_commands.Button_520, up = device_commands.Button_520, cockpit_device_id = devices.PWRPNL, value_down = 1, value_up = 0, name = _('Main Battery Switch Toggle'), category = _('Engine')}, using steps from this thread http://forums.eagle.ru/showthread.php?t=89226&page=17

got it!!!! {down = iCommandBatteryPower, name = _('Toggle Main Battery On/Off'), category = _('Systems')}, will try to add the other switches for this toggle function and report back.

i've browsed the clickabledata.lua file and see where you got the information for this particular binding. It identifies these as ,devices.PWRPNL, device_commands.Button_520, and the operation is a default_two_position_tumb. I have even tried changing this to a default_button and adding the appropriate statements to the end of the code state but this renders it inoperative. As with the A10C......the down = iCommand%@$^%&, functions are way easier to adjust for toggles than the code in the M2000 default .lua. I'll keep hacking at it and if i Find the solution (Deezle) ill let you guys know. I'm not very optimistic however as i've seen some of your work Deezle and it seems you have your head around it a little better than mine.

Since we got no love from RAZBAM or ED on the key bind front, I'm trying to edit some of your code. I use a pulsed input toggle switch to operate some switches in my pit. The switch i use in my pit for every aircraft master battery is connected to a desktop aviator 2235 board which sends a pulse when you flip the switch which allows me a toggle feature, which comes in handy. For example your coding for the master battery requires you to have two buttons programmed to turn it on and off. i've tried editing your lua but when i flip the switch in my pit it turns the switch on then off in the sim.....i know that sounds confusing but its avoiding me how to get this thing to work right. i have been editing luas for a while now for key bind issues but this one is stumping me. here is my code i'm using....i changed it to have value=up 1 after the cockpit device id: {down = 3520, up = 3520, cockpit_device_id = 8, value_up= 1, value_down= 0, name = "Custom - Engine - Main Battery Switch Toggle", category = "Engine"}, taken from your code: {down = 3520, up = 3520, cockpit_device_id = 8, value_down= 0, name = "Custom - Engine - Main Battery Switch Off", category = "Engine"}, {down = 3520, up = 3520, cockpit_device_id = 8, value_down= 1, name = "Custom - Engine - Main Battery Switch On", category = "Engine"}, any insight would be greatful

just wanted to update you on this....as for 1.2.16 i got it working by editing the .diff.lua files in the saved games folder. however im unable to edit anything for the F-15c in 1.5.1. niether the default lua nor the diff.lua give results or they give negative results.

i installed the config tool per instructions and updated the xml to use with 1.5.1 i'm getting an error when i click on patch all. do i need to put in a different data.lua file in the scripts folder.....i've been able to manually edit luas for the a10c but trying to edit for the F-15c and having issues....i found this thread and hope your mod will help me out in this particular editing nightmare i'm in.

For some reason when i edit the default.lua for the F-15c it corrupts some of the bindings for the aircraft (like weapons release) when i try to edit the diff.lua as soon as i load DCS and get into the pit i have to rebind the edit joy button but it doesn't perform as desired. For ecxample the navigation lights are setup to work with a push button. im using toggle switches and want to have it operate as an on/off toggle. see below original ["d175pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN5", }, }, ["name"] = "Navigation lights", }, edited ["d175pnilu175cdnilvdnilvpnilvu-1"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN5", }, }, ["name"] = "Navigation lights", }, anyone have any advice?

Yes i've been using the encoders on other modules as well as the A10....just to let you know a fellow squad mate and i edited my default.lua in the 1.5 beta and viola....its working....we fly 1.2.6 in our squadron and for some reason the edits aren't working properly on that version so........i got it to work and 3 way toggles are functional.....thank you so much for being a good sport and pushing me to not give up.

I did copy and paste the modified code and removed the original code but that's why we are still chatting I'm not getting the results that your lua file gives me. I'm not a programmer so looking at the above code only makes my brain hurt a little. Either I'm missing a step or there is a particular why to take your modified code and put it into the original default.lua that I have. It seems simple enough but somewhere DCS doesn't like what I'm doing to it. Just so we are on the same page. I only copied the individual lines of code from your lua to mine. I was working with the inverter codes. I did not copy paste your entire lua into my default.lua. I just thought that may be what I need to do however there is a lot of the coding in your lua I don't need.

i tried adding your edits to my original to no avail..... i guess there is more to it then i'm seeing. The only switches i'm concerned about now are the Landing/Taxi Light, Position Lights, Inverter switch and IFFCC switch. I dont have any other 3ways setup (ie on the master arm laser etc etc on the armament panel) due to this hurdle with 3 way toggles. I feel that i'm real close but anything i try to do with my original barring taking coding for the non programmable buttons from my original and adding it to your edited version i'm at a loss.. hope that makes sense. Im open for thoughts questions guidance or a boot to the face.

:thumbup: this definitely makes the switches perform as they should.....however it has removed my ability to program buttons to certain switches in game (ie the lighting panel.) I cant program my rotary encoders to adjust the formation lights, console lights etc etc. In theory, could i copy and paste the edited lines for the 3 way toggles into the original default.lua and preserve the code for the other buttons that i don't want changed from the original?

@Hans, thanks for this....to be honest I forgot posted this thread, @Ian ...... disregard the post on the other thread from you to me. The answer to my question, my friend, is answered in here. With that said, does anyone have the time or know the guru with patience to step me through the Lua editing process. I understand the concept, have notepad ++, and novice level programming skills. I do see in the coding how the inverter switch works appropriately from test to off. Once I can get that one working from stby to off then everyone else will be a breeze.

OK Ian I know you're referring to DCS Bios.....unless I'm missing something I would be required to setup an arduino board to implement toggles and communicate through to DCS WORLD. I don't currently nor am I in the near future (I will in the distance future) plan on getting into arduino. If I can however use DCS bios with my current Leo Bodnar boards and get the results I'm looking for please, PRETTY PLEASE let me know.

Why hasnt anyone done this for the A-10C?

Possible to edit lua? I found a tutorial from TigersharkBAS showing how to edit the lua files.....its obvious that things have changed dramatically since the tutorials creation and unless i'm missing something there is no way to manually edit these lua files to make a 3 way toggle switch perform as it should. Please correct me if i'm wrong. IF I am right then let me know....either way i have been using on-on-on switches and binding the inverter stby test and off to its own button. i would like to avoid this because buying more button boards is getting expensive and i'm running out of room. I went into some of the lua files and found this code....i noticed that when i flip my toggle from off to test and back it works as it should but from stby to off doesnt work. look at lines 2 3 and 4. i tried adding up = iCommandElectricalPowerInverterOFF as it is for the inverter test section of the code next to the inverter stby but i got strange results......there has to be a way!!!!! --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')},

so ive been busy with work stuff and haven't been able to retest this until today. started with a fresh profile and still have the same problem. i can live with setting it up with dcs-bios but it baffles me as stated before that it worked before. your initial response on the matter was correct and from what i gather it works for you if you program the keys to the virtual key. one interesting thing though is in the log on the bottom right of the PZ70 screen. see attached pic and let me know if this looks a miss to you.

i actually want the light lit as the EGI switch stays lit when active on the nmsp panel so thats no issue with me. ill test further but i did make a few attempts aside creating a new profile which im not really wanting to being i have three panels. as stated before ill test further and get back.

ill try and make another profile to see if that fixes the issue. it worked before but im not sure what changed.. ironically i set all of the nmsp buttons as the first seven number keys on the keyboard. funny how you did the same.

somehow i lost the ability to use the lit keys on the multi panel....i had keys bound to each key to control the NMSP panel. i can get the buttons to work in the sim if i bind them to dcs-bios but the wont toggle as a momentary switch. for example the EGI switch stays pushed in. i tried to set the state as an action/toggle but it doesn't toggle as a momentary. it worked perfectly when the keys were bound but i cant figure out why they wont work any longer.

Question to anyone that uses Aries. I'd like to know whether or not its compatible or should i say works properly with Flight panels? For example Aries being a separate program that integrates with DCS, does Aries radio freq change when you change it in the sim or do you change the freq in aries and it changes in the sim? edit::: question retracted....it works fine......

I recently started tinkering with my BIP and have to say I think its pretty awesome. as a matter of fact I'm using you're profile for my a10c. one thing I was thinking in regards to the custom tiles and labels is if the ink is messy why not spray a flat clear coat on the labels before you use them. After they dry then you could stack them so the opacity is greater around the letters and the ink won't smear. Just a thought. You may be able to use hairspray as a fixative as well.

@Arturdcs and Darkwolf I wanted to thank you both again for helping me out with my issues a couple of weeks ago. I'm enjoying the panels even more now. I did have another issue with DCS Virtual cockpit which is an android app (same developer of I control) which was causing flight panels to stop working. Through a few emails and some more testing the developer has updated his scripting and cleared the conflict. Keep up the good work. I look forward to seeing more out of this great software.

SOOOOO.... i've been enjoying the A10 and have my simpit set up pretty well but my main issue is the 3 way toggles. i have on - off - on toggles but they didn't perform as i thought so i bought on - on - on switches and they work but when i go from say switch 1 to switch 2 to switch 3 it moves and the sim switch moves as it should. However, if i go from position 3 to position 2 it doesn't move. I know there is programming to be done but have no idea what i need to do. i have notepad ++ and have looked through the lua files for the warthog to compare. Is anyone a "GURU" in lua programming around that might be able to lead the blind to the light if you know what i mean???

Not sure what "status" your wanting but currently i deleted everything associated with flight panels, including dcs bios which was installed and had been working at some point btw. The developer kit for chrome that was in the dcs -bios instructions never worked. I never saw any values so dont really know if dcs bios was working properly. i also, on initial installation in the beginning, had to search for the libusbdotnet which was not apart of the 1st version of flight panels that i downloaded. through a lot of frustrations i did get both panels to work correctly. im not sure what things transpired but after some point, either an update to windows or my use of helios the radio panels ceased to work properly. Darkwolf pm'd me so hopefully we can figure this out.