Trigati

I don't feel that openly posting a way to circumvent a mission builder's design choices is the right thing to do, not my style at least and would disrespect the effort and vision they have. I just wanted people who really do need to be able to make such changes (for me it's poor visuals that mean without labels I cannot ever see a bandit till well past the merge) that it is simple and possible to do without needing to hassle the mission/campaign builders or to miss out on their great content! @ChillNG -I loved OCN so much I purchased 'Weasels' on release day....even though I've never flown the F-16.....thanks for your work! Maybe in a few months of learning the Viper I get to fly it!

As a quick follow up...it is still possible for a user to manually remove the mission maker forced overides if they have 7zip and a text editor....and want to do it...although it then it gets corrected with every update but if they feel that strongly about wanting things their way (for whatever reason - and labels for some users seems to be a must for some with visual issues) it is possible to fly your missions with them fully on.

Alas overide does not work if mission maker ‘forces’ a setting…it only overrides a normal mossion setting with the clients choice for that feature. I think ED have not been that clear on how this works but I’ve tested it quite a bit. Sent from my iPhone using Tapatalk

So sorry I've not had time to get to this...but it is done now. F-14B.lua

Sure, that LUA file is used to send data out and I can easily add the lines to send the ICLS channel number. What the export does is send each bit of data under a separate Export ID For example(and made up)….speed is sent as a value on ID 292, heading is sent as ID 456, rpm left is sent under ID 2036 etc etc Whatever you connect to read the export looks for the ID it wants and then uses that data. Is there a particular ID number you wanted me to code this to? If not I’ll send as I’d 88912 as the raw switch position is 912

OK, is there a specific code number you want it output to?

Can you send me your lua and I can then see if I can add and rest it for you. Sent from my iPhone using Tapatalk

Is it possible you are checking this in a cold dark aircraft? If so then maybe you have not released the throttles from their locked off position? Sent from my iPhone using Tapatalk

Sure, although I'm not sure what I know will fully help you unless you are already familiar in getting a DCS data export into your chosen device (arduino or StreamDeck etc) as mI don't fully understand that level. If you're going to build a display I can recommend searching around for DCS-BIOS (flight panels fork might be best) and DCS-Export on github and this forum. GitHub - DCSFlightpanels/dcs-bios: DCS-BIOS Flightpanels Fork I use DCS Export Scripts asherao/DCS-ExportScripts: DCS World Export Scripts (github.com) Simple Explanation: This script file enables the export of data from DCS and is focussed on cockpit controls and gauges. In the F-14 the ILS selection dial is mainpaneldevice argument 912. DCS sends all these as a value usually between 0 and 1....and as there are 20 channels it works out as a value of about 0.05 per channel. So if the switch was set to channel 7 the value would be 7 x 0.05 = 0.35 In the LUA script that formats these export values you can run all sorts of functions and formatting, so you would reverse engineer this value to output the channel number in a readable format (if the value from DCS is 0.70 then divide that by the 0.05 to get channel 14. More Complex: But it's not quite that simple, the selection knob has no 0/off position so when DCS sends a value of 0.0 it means channel 1 but the above simple math would tell you channel 0 - which does not exist. So we have to get the best approximate value and formula that works which works, so we set 0.0 value to equal channel 1 (by adding 1 to whatever we calculate the control position to be) and then split the value range of 1 into 19 (not 20) which is 0.0526315 This formula can be used to get the channel number from the DCS value: (VALUE/0.0526315) + 1 but you'll then need to round it to a single whole number to be readable in a display. Here is my LUA code I use to do this: channel = Round(mainPanelDevice:get_argument_value(912)/0.052) + 1 And the Round() function I'm using in that is: function Round(num) -- Rounds UP/Down to Nearest Whole Number return num % 1 >= 0.5 and math.ceil(num) or math.floor(num) end -------- How this is done in DCS-BIOS I have no clue, but I hope it gives you a good idea of what's needed.

In an export script you can take the switch position and convert it to the channel number and output that. I’ve done this for a Streamdeck profile so should be just as possible for sending to another tool. Sent from my iPad using Tapatalk

I would guess that btn4 is already bound to a function in P51, that’s the only reason I can think it would not let you make it a modifier Sent from my iPhone using Tapatalk

Most surprising part was seeing how much time the pilots spent holding the canopy handles and not the stick/throttle. Sent from my iPhone using Tapatalk

I’ve only had issue reported, which wasn’t really in need of an immediate fix and one additional feature request so have not looked to update and release a new version. I’m not flying the 15 till I learn to fuel in the 18 or 14….promised myself I’d earn the right to play….so not found any issues myself. I’ll take a look at what you report in the next couple of days then issue an update if needed….so this is also an open shout out for any other requests? Sent from my iPhone using Tapatalk

ICP for me please. PayPal OK? Sent from my iPhone using Tapatalk

If nobody else helps before I get to my PC tonight I’ll take a look for you. Sent from my iPhone using Tapatalk

Brake switch is mainpanel argument 387 and nearly all cockpit parameters values 0 to 1. Probably safe to assume 1=on position Sent from my iPhone using Tapatalk

No, it shouldn't make a difference if the tablet is running or not, only iof thr cpode used to export the app is throwing an error that stops the code running for the flightpanels stuff. If the problem only comes when the app is running my guess would be they are both trying to communicate back to DCS via the same method and maybe they are clashing there?

I cannot answer your question but I might have a fix for you. Although I don’t know for sure I think exports are processed in the order they appear in your export.lua file. My guess is the line of code for this app appears before your flight panels line. I think I’ve observed certain errors in an export stopping it processing all remaining exports and starting its cycle again. So that’s where I’d look first to troubleshoot. Sent from my iPhone using Tapatalk

Maybe try use if the button off feature DCS has to add a binding for switching things off. Sorry, probably best to explain this a little more. DCS lets you bind both a 'button' action and a 'button off' action for every single DX button on any of your controllers. So if the Module bindings only have options for ON or OFF and you want to use the Warthog EAC 2 position Switch (ARM or OFF) then you would set this up by following these steps: 1. Go to the ON function in adjust controls you want to bind and double click the box as you normally do to bind a control. 2. Flick the switch to the ARM position, DCS auto sees that and populates the mapping binding. You click OK (Accept or whatever it is) to save it. 3. Go to the OFF function binding and again double click the box. 4. Then move the EAC switch to OFF (does nothing) and back to ARM....but DO NOT save this!!!! What it has done is given you the same button press, let us pretend that is BTN23. 5. Where that controller button is shown ther eis a little drop down list you can click, which lets you manually choose an option and you will see in that list is the button you just used but with _OFF written (something like BTN23_OFF). Select that and then save it. Now...when you move the EAC toggle switch to ARM the first binding will be triggered, when you move the EAC toggle switch to OFF the second one gets triggered. So using a mix of this, the different bind options that are provided by the Module it's possible to work out 99% of control setups without having to load custom bindings or use TARGET to program the Warthog. I hope this helps you whilst the Module developer considers your wishlist item.

Could’ve the export lua causing a data export failure due to it trying to send null data… which often happens with a cold n dark so I’d start by looking at the export lua sending data to the platform. A big culprit is any list indicator data. Sent from my iPhone using Tapatalk

What patch number/version DCS are you on? And what version number of the F15 LUA? Sent from my iPhone using Tapatalk

This would go in the Low Importance section of the LUA and send a rounded 'whole number' of the first two decimal places on code 6487 (but I've done this from memory as away from my DCS system right now): ExportScript.Tools.SendData(6487,string.format("%1d",mainPanelDevice:get_argument_value(487)*100)) But are you sure it's a straight conversaion like that?

Mmm, that should work fine for the UFC. I’m not sure about the BIOS thing, just the ExporrScript stuff. I’ll find a quick moment to test my LUA against Johnny’s profile. Sent from my iPhone using Tapatalk

Which version number of open beta are you on? And which version of the export lua? They changed the UFC code two patches ago so I reckon you are not fully up to date. Other possible issue is which Sd profile are you using? Sent from my iPad using Tapatalk

Good spot on the duplicate export, thanks. It should not cause any issues for now though. So I'm not sure why you exports have stopped working if you've updated to Open Beta 2.8.7.42583 which broke the UFC Exports and then the Export LUA 0.8 which was my fix it should be all good. By any chance have you updated one and not the other?