Kyle_Katarn

When I create a new Enumeration and later is used in the .pp file of the airplane, not all of them are working propertly I have attached my files so you can test it There are 4 new enums for the A-10C and only the LaserArm and the UhfPoint25Mhz are working more or less fine, because the UhfPoint25Mhz is being updated a little bit slower than other things. I need to comment a lot of events that I'm not using, maybe this could imprube a little the performance A-10C.pp aircraftEnums.pp

This evening TP has released a new version, une of the fixes is: Fixed dynamically created plug-in values not showing in text replacements list Could this one be related with the missing options for the F18?

I have re-do this subject and the NOT AVAILABLE is not shown anymore, but also my new enum is not shown Plugin uninstalled TP closed The .tp file have the correct value choices All the files in use have the more recent date

Ok, I'll try again the Enum adition fir the radios. Abaout the limitation of 10 issue, I have edited a second time my last post. Is no an issue on DCS-COINS side, is DCS-BIOS/DCS which have defines that the rotary knob for the left channel selector of the TACAN have 10 position, so DCS-BIOS report that the knob run throught the steps 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 and again use the position 0 to indicate the 100 Mhz, position 1 to 110 Mhz and the 2 for the 120 Mhz. Whit this when I recover the value of the left channel selector, is normal that I cant get anything over 9. I'll try to setup an Enum to this parameter, but first I must to achieve the radion working propertly

Dude, forget all about splitting the TACAN freq in two values. Reviewing the A10C pp file I have found a Left and Right channel selector related with the TACAN, so here they are the values what I was looking for. The only issue is that the definition is limited to 10, but now I know how to update this limit, thanks. Edit: I had tryed to update the ranges of the left and right channel selectors, but the behaviour is not the expected. With this definition the left channel selector range is from 0 to 9, the 10 is showed but instantly changed to 0, 11 is showed as 1 and 12 as 2 Edit: I see that DCS-BIOS is reporting exactly those values, so on DCS-COINS side everything is right

Edit: Comments were removed when posted I think that I have done the process right, because the modifications are shown in the files in the TP plugin folders In TP I can see the new named value, but the availables values are "NOT AVAILABLE"

I'm going for it dude!!! P.S.: I love this kid

I'm advancing in the A10 pages with the new version of DCS-COINS, but I'm missing a couple of things, not the most important but... The TACAN channel is reported as a single string, Could you add a tens variable and a units variable, without the X/Y channel? As you can see in the next image, al bottom left I have the TACAN channel selector one for the tens and one for the units, but DCS BIOS only report the full TACAN. Next to TACAN it's the ILS freq selector. DCS BIOS can report Khz and Mhz but you are reporting the full freq, Could you add the separated channel as DCS BIOS report? Other missing things are the preset channels of three radios and the freq selector of the FM and AM are reporting the degrees of rotation of the rotary selector, wierd thign of DCS BIOS. I you could to the calculation to report the correct number would be amazing, because I was traying to calcylate it working with TP values, but this is a very limited feature and I can't achieve it. In the other hand I was living without the live channel and freq selector for each radio showing their numbers in the TP app so If you can`t improve this subject, COINS will continue being a great piece of software. You could be proud

But the downgrade allowed me to use all the values related to the F18 that I couldn't use with the 3.X, so I'm going to keep this version until we could find what is breaking this list. I prefer to use all the features of your plugin than all the new features of TP at this point.

Well, This is the list of issues I have found in the F18, sure that some of them are from my side but here they are: The Trouchlight linked to the mouse cursor, this event I cant get it working ç The ALR-67 modes are reporting from 0 to 4, maybe is more user friendly to report N I A U F RWR mode OFFSET: It have the green light status and the pushbutton status, but not the Enabled status (like the RWR-Display button) Dispenser switch is reporting 0 to 2 instead of Bypass/On/Off EMERGENCY_PARKING_BRAKE_ROTATE is reporting 0 to 2 instead of other kind of literal. I really don't know what means each status but could be something like VERTICAL/HORIZONTAL/ etc etc. What do you think? Radar switch is reporting from 0 to 3 instead OFF/STBY/ etc etc Aside Note: If you see in the controls list of DCS, there is only the posibility to bind a keystroke or button to the CW rotation of the switch, when you reach the milestone in the development of send commands to DCS-BIOS we could send the CCW command to this switch which will make things more easy BAttery swhitch is reporting from 0 to 2 instead of ORIDE/OFF/ON And this is what I have found that could be changed IMHO, not bad or good just maybe need a second thingking about

Ok then, I'm goin to rollack to version 2.x. Starting with the A10 I have seen that DCS-COINS in vervose mode return to me this I'm goin to reinstall TP and later attack this issue, I think that creating again the file could solve it

Here I have attached the two pages and the iconpack I'm using. If anyone find something broke, give me a shout. All the buttons have a keystroke that need to be mapped in DCS F18_TouchPortal_Kyle_Katarn.rar Not really. I saw that the A10 has available the plugin dynamic text variables and F18 not, but I go forward with the F18 pages, I'm going to spend some time on A10 right now. In the F18 I saw that some events supossed to return ON/OFF and return 0/1, I could review it and list it so you can find it faster if you want.

Ok that give some answers about why the frequences and the tacan channel didnt got updated. Are you using the dcs-flightpanels branch of dcs-bios, right? A week ago or so the release a couple of new versions. It's recommended to update, because I'm using a version from October/November

The small map was a button to open a page with the central DDI and some other things but then I get a third thrustmaster mfd so I need to rearrange the pages and this page was deprecated and now is obsolete, I didnt removed this button because reasons The big map button open/close the kneeboard

Well, my first iteration with the DCS-COINS is a success. I can't update the controls when I jump in to the aircraft, but all the other things work fine. I need to solve this issue. Here is the two pages what I use with the F18. If anyone want I could share it.

First test with the Master Arm and Master Caution in F18, this works like a charm dude Outstanding work!!

Thank you dude! First I'll install and try it to learn the usability implemented and later will look in to the code to learn about it and how you manage the things inside. I'm not java or node.js user but will do my best. It's possible that I would start to spam questions to you, so sorry In advance

Cool Another aircraft what I'm interested is the A10 and comming Apache. Do you have a github or something like that sharing the code? I dont have use java or node.js, but if I could help to implement this modules I will

WOOOOHOOOOOOOOOO!!!!! I lost the track to this post, but for the mother of good, xoomigo you get what I was trying to do. Are you at the TP discord? I'm out until Jan 7th, but for sure I will try your pluging and give you my feedback. Are your pluging able to syncronize the controls if TP is open after the simulation has started? I have lot of questions but is better to me wait and try it by myself. I want to try it as soo as I return to home, but with the short clip of Marcos it seems to work like a charm, excelent work xoomigo, outstanding!!!!

You need to create a plugin for touch portal. With the plugin you can read and process the stream of data from DCS-BIOS or DCSExporter, and associate to a the value of each parameter exported to the value of a state. To read it basically you need to read a TCP/UDP port from data server, basically the loopback IP, unless you have the data server in another PC. The you just need to send the key stroke with TP to DCS and the change of the value in DCS will trigger the change of the state in TP. Cheking the value of the state, you can set the appropiate icon to the correct button, or change a text dinamically with the data readed. I was developing a plugin in C# using a C# SDK, but the job, Cristmas holdays and the moving to a new house render all of my time to continue. I was using DCSExporter to extract the info from DCS. The pros are that the stram of data is very straight forward, paramId:paramValue. Cons, paramValue is a percentage, or the int value of an Enum, and you must to process the values before to send to TP. In the other hand DCS-BIOS have a more complex or more structurated stream of data and you must to process the raw information to know how many parameters are in the package received. Pros the paramValue is processed and have the same information you see in the cockpit or at least is much more user friendly than the information you can read from DCSExporter. I would like to use DCS-BIOS but I can't really undesrtand the way the information is packed, when I thought I have the key I found another package which break my rule... If you have that key I would like to know pleaseeeeeeee To create the plugin it's need to do some tedious work and is that you mut to create in a JSON file (or seneral files, as you wish), the hole set of states and the posible valueas of each one. I found the way to do it more easly with an Excel spreadsheet, and using the functions to search in matrix and concatenating text string. The result was a set of rows which you could copy and paste in noteapd++ and you had the final JSON file. The state of the development was very early because I was learning to use the SDk, which was abandned by the guy who was developing it and also understaing the way TP works and readind the docs for the plugins development. It's not difficult but some times the things were not working as I spected.

Use the tab On Hold. When you use the On Press tab, ontouching the buttton, TP will mimic just one press of the keystroke combo. You can use the virtual press or the low level key press. But if you use the On Hold tab, when you just touch the button, like a simple key stroke, the low level key press only will send the simple key stroke to DCS. Instead, if you tpuch and hold on a button, TP will send the low level key press all the time you are pressing the button. Using the On Hold tab you are forced to use the low level key press, but this is not a problem because is a much more compatible way to program a combo key press. Even more, the virtual key press can't mimic the left or right shift, alt, ctrl or windows key, but the low level key press can do it, so it is much more versatile. So my advice is, use always the low level key press. Use only On Press tab if the button don't have two different actions (one on press andone on hold) I'm in love with this app. Previously I was using Macro Deck but it don was too much reliable for me and one day stop to working the 70% of the times I wan to change the page. TP is not free, in my tablet take almost one sec to change between pages, but it's infinite more powerfull and don't fail (cross fingers) I don't have any poblem setting multiple key binds using shift or ctrl or alt or window key combined with other modifiers and keys. The only keys I can't get working inside DCS are the Pause key and the Print Screen. Attached images of my F18 and A10-C pages, I have almost every thing (this shit is always evolving XD) I need to fly and only touch the keyboard to press the Function key on comunications to AI by radio.