CARTOK

Fantastic work on this! Can wholeheartedly recommend to open-source it and put a copy of GitHub (unless you got bigger plans, of course). In fact, over the last week I've been busy making (humble, but nonetheless) contributions to the MOOSE project - I would not have been able to do so without being able to use all the normal coding tools and PR processes. Many thanks for your continued efforts on this! And exciting to hear that further work is ongoing!

Ah, thanks! I had a feeling it might be the case, appreciate your assistance and fantastic work on this!

Noticed difference in function naming (the same is applicable for both Action and Event): null

How is it possible to get/set the state of buttons when you connect to DCS and start flying? I note that 'DCS-COINS -v' captures the following (extract): DCS-COINS v.2.2202.02: Verbose mode enabled. 2022-10-01T12:12:19.237Z [INFO] dcs-bios-api: parsed aircraft JSON - A-10C 2022-10-01T12:12:19.346Z : Munt.G_DCS-COINS :INFO: Connected to TouchPortal 2022-10-01T12:12:19.349Z : Munt.G_DCS-COINS :DEBUG: Info Message received Aircraft: [A-10C_2] CommonData: Loading aircraft parameters from ./acdb/A-10C.pp Event: mgdc_a-10c_st_aircraft_connection [ON] (a-10c: A-10C Thunderbolt/II) ALT_MSL_FT: 1 HDG_DEG: 1 HDG_DEG_FRAC: 0 DCS_BIOS: 0 PILOTNAME: 0 LAT_DEG: 0 AAP_CDUPWR: 1 AAP_EGIPWR: 1 Later on, and sometimes, all initial events are triggered: Event: mgdc_a-10c_st_aap_cdupwr [ON] Event: mgdc_a-10c_st_aap_egipwr [ON] For instance, I want to set the an "EGI" and "CDU" button status, respectively, to 'On' as per the information received (AAP_CDUPWR: 1, AAP_EGIPWR: 1, and the later received events). However, these initial events don't always get triggered, and when they do they don't seem to get processed. Any guidance/suggestions for setting initial status of buttons/text when starting a flight is appreciated. Edit: I had a log indicating that numerous initial events were triggered, including the EGI/CDU PWR events - however, re-running/starting they don't seem to happen any more. So not sure what is going on. Attached a log with some random output, search for "EGI" or "CDU" as a starting point to locate where the events were triggered. 2022-10-01 DCS-COINS log.txt

The issue was related to using DCS-COINS in verbose mode in parallel to the plugin ("DCS-COINS -v") - see next reply re. the coming fix to avoid this. To note; Using only "DEPRESS" causes weird issues in-game with stuck buttons, I'm now using "PRESS" and "DEPRESS" with good results (without two instances of DCS-COINS running). Thanks, that might explain some earlier issues I had. Sounds like a good solution, looking forward to the update!

Another observation; I've been setting up MFCD buttons for the A10C2. I notice that the only way to trigger the MFCD buttons correctly (and get the expected result) is to use the "DEPRESS" action option. Choosing "TOGGLE" changes the state of button, leaving it pressed (if it was not previously pressed). Using a combination of "PRESS" then "DEPRESS" with a 100ms wait between seems to trigger two actions in the A10 - first a button press on "PRESS", then another button press as the button gets "DEPRESS" (the animation in aircraft looks correct. Using "DEPRESS" avoids the issues and triggers only a single action, there's however no feedback in the cockpit of the action (more than the result of it). Is this a known thing? I assume it could be related to DCS-BIOS somehow. Edit: Is this caused by having "DCS-BIOS -v" running and thus sending duplicated actions? It seems to have stopped when killing it. null

Alright, this worked on first try! Obviously with a slight lag. With that, I recreated the initial version (to update on event change), and that works now. I believe user error somewhere. Thanks for your help!

Separate item to previous questions, in case I missed something. I've tried to use a set-up inspired by the F18 UFC panel, but the updates are flaky...at best. I want the CDU line 9 changes to be reflected on a button with the following setup (the actual variable is 0-based whereas the description the 1-based, as far as I can tell). However, the updates of the button title/label are (at best) intermittent. I've manually amended the variable to refer to "....line9" as indicated by regular updates in "DCS-COINS -v", but the button title/label updates only happens randomly - not just a delay, it's just randomly not happening at all. Changing CDU page sometimes triggers an update, but not always to what the "DCS-COINS -v" message indicates should be the outcome. Is there something obvious I'm missing here? Happy to experiment/test as directed, but no luck yet getting it to work as expected (i.e. to display what the "DCS-COINS -v" output indicates what should be displayed). null

Much appreciated, you've done some really good work here! I will keep my eyes open if I spot anything further. If there's anything specific you'd like me to test for the A10C2, let me know. I've tried to apply my (limited, but workable) Lua skills to understand the DCS-BIOS code, I'll keep looking to see if I can spot something and feed it back to the DCS-BIOS maintainer (I assume this is the current home to the most updated version: https://github.com/DCSFlightpanels/dcs-bios). Edit: Tested more in-depth using the DCS-BIOS Chrome App. Discovered the following: 'LASTE_AP_MODE' is working, and like magic the messages are now received by the Touch Portal app as well (showing up in 'DCS-COINS -v'), same with 'LASTE_AP_TOGGLE'. The latter seems to possibly have been related to me having a "Throttle button" set in the controls, rather than the "LASTE AP TOGGLE" - coincidentally it worked fine in the sim but did not trigger the DCS-BIOS message. Go figure... I discovered some other quirks related to how messages are sent or not by DCS-BIOS (or DCS itself) that are completely unrelated to your app. In summary: Things seem to work as expected now, the only observation is the reversed flap setting status as captured previously. Many thanks for your response!

Hi there, fantastic work on this, it was very easy to set up and get going with Touch Portal! I've had good progress so far but need some assistance with regards to possibly reversed and missing messages for the A10C2: The messages from: "a-10c Flaps Setting DN - MVR - UP" are reversed, i.e. DN is received when the flaps are actually up, and vice versa for UP. I'm not familiar with DCS-BIOS at all, but gather this is something that might be an error in DCS-BIOS that can be corrected? There are no messages received at all for "a-10c Autopilot Engage/Disengage": Tested with "DCS-COINS -v". There is no obvious reason for this in the DCS-BIOS nor the DCS-COINS: A-10C.pp: LASTE_AP_TOGGLE|laste_ap_toggle|Autopilot Engage/Disengage|4|0|OffOn|OFF A-10C.lua (DCS-BIOS/lib): definePushButton("LASTE_AP_TOGGLE", 38, 3002, 131, "LASTE Panel", "Autopilot Engage/Disengage") There are no messages received at all for"a-10c LASTE_AP_MODE". Tested with "DCS-COINS -v". There is no obvious reason for this in the DCS-BIOS nor the DCS-COINS: A-10C.pp (DCS-COINS/acdb): LASTE_AP_MODE|laste_ap_mode|LASTE_AP_MODE|1|0|UpTo2|0 A-10C.lua (DCS-BIOS/lib): defineTumb("LASTE_AP_MODE", 38, 3001, 132, 1, {-1, 1}, nil, false, "LASTE Panel", "AP MODE") I've tried download the latest DCS-BIOS from here: https://github.com/DCSFlightpanels/dcs-bios And have rebuilt and reinstalled the tpp file as per https://www.digitalcombatsimulator.com/en/files/3319022/ Any pointers would be much appreciated.

Truly fantastic work, it is quite impressive! And for those reading this, even simple and non-technical contributions (documentation etc.), as has been submitted by myself, has been greatly appreciated. Keep up the great work, Frank and Apple!

I was experiencing the same on my first run (in VR). But have been unable to recreate it. I'm not sure if it was user error or a bug. If you see it again, please post a reply.

Possibly, might have missed it then. Just checked Discord earlier today and got the impression it was updated very recently (yesterday) to be my turn. Getting closer either way... :-) Happy New Year!

Oh, I'm up! :-) PM sent, email inbound.

Perfect, thanks!

Thanks, checked out discord, noticed the long list. Please add me to it! I'll follow up there. Thanks for the reply!

Hi Miles, really intrigued about the PointCTRL, might get back to you with an order over the coming weeks. I understand some work is in progress for a diffusion dome, or something to that extent, to improve the tracking a bit. Should I hold on for these items to be finalized? Maybe there are other items you're working on where you would suggest to a potential new customer to hold on for a few moments? Great work on this!

It's not so much about whether the aircraft indicates that you're in afterburner or not (great effects by the way!), but rather the inability to reliably set the throttle without engaging them. This leads to lots of wiggling to find the right setting, repeatedly engaging/disengaging the afterburners. This is even more prevalent when you attempt quicker adjustments. To quote myself from a separate post: "...would eliminate a lot of frustrating throttle wiggling back and forth trying to find 100% MIL without constantly engaging/disengaging the afterburner." The functionality works so well on the F/A-18, and emulates/simulates sufficiently the existence of the real life physical indications (i.e. detents/lift etc.).

Hi Razbam, please consider adding an optional software afterburner detent a'la the FA18 to the M2000 module. Only for the purpose of limiting throttle input to 100% MIL without it being pressed. This simply works great on the FA18 and would eliminate a lot of frustrating throttle wiggling back and forth trying to find 100% MIL without constantly engaging/disengaging the afterburner.

Hi Heatblur, please consider adding an optional software afterburner detent a'la the FA18 to the AJ37 module. Only for the purpose of limiting throttle input to 100% MIL without it being pressed (not any afterburner stages). This simply works great on the FA18 and would eliminate a lot of frustrating throttle wiggling back and forth trying to find 100% MIL without constantly engaging/disengaging the afterburner.

Away from computer at the moment, has this been fixed yet?

To echo some of the other posters comments; please add an optional software afterburner detent - reference model is available on the FA18 and it works really well. I find myself constantly switching in and out of afterburner for no reason as my joystick can in no sensible way indicate such. The optional button press (as FA18 reference) simulates/emulates the physical action to activate afterburner in the real aircraft. The same holds true for the AJ37 as well.

Yes, please, this makes a big difference when flying the FA18 and works really well. Heatblur, please consider this type of functionality for both the F14 and AJ37. As it is already in use on the FA18 to great effect (for myself and many others), the button for this functionality is already reserved on my throttle.

Expericing the same bug. Not able to find a pattern to what is causing the pipper to be wrong (showing lower than actual impact point about 2/3 of the time).

The functionality of the recent update works great for me as it helps with staying out of AB when not desired, during all phases of flight. I do not have access to hardware detents on my system, I do however have enough buttons on my setup to map a dedicated, accessible button for the purpose. As such, I don't think a software detent is an unreasonable or unrealistic compromise to allow effective throttle usage. This functionality should ideally be implemented for all modules. However, understanding the many different hardware setups among users, the only viable option is probably to allow as much flexibility as possible. Thanks for an enjoyable module!