Jump to content

Touch Portal App


Recommended Posts

Am 14.3.2023 um 01:29 schrieb xoomigo:

Abeone,

The logs showed that Touch portal and DCS-BIOS interfaces are both working with the plugin. Please share how you setup your TP slider control.

I have done no configuration, weather in TouchPortal nor in DCS? please Tell me  what exactly  you need.

Link to comment
Share on other sites

16 hours ago, Abeone said:

I have done no configuration, weather in TouchPortal nor in DCS? please Tell me  what exactly  you need.

I thought you were building your own TP pages. Apparently, I was mistaken.

One thing to do firstly is to make sure that there's no conflict in any of the mods that you have installed. To confirm that, edit your Export.lua in the Saved Games\DCS\Script folder, and temporarily disable all the mods except for DCS-BIOS. You do this by adding a double hypen at the beginning of each line in the file. eg.

dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]])

--pcall(function() local pw=require('lfs');dofile(pw.writedir()..[[Scripts\pw-dev_script\ExportInit.lua]]); end,nil);

--pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil)
--local pw=require('lfs');dofile(pw.writedir()..[[Scripts\pw-dev_script\Export.lua]])
--dofile(".\\A10VCServer\\Main.lua") --A10VCHook
--local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua'

Then load up TP, run "DCS-COINS -v" in command prompt, load up DCS and just fly the hornet in the air and toggle some switches in the cockpit within the game (not using the F-18C touch portal pages) for about 2-3 minutes. Exit the aircraft. Then send me the screenshot of the output of DCS-COINS -v logs (as you have done earlier).

 


Edited by xoomigo
Link to comment
Share on other sites

  • 1 month later...

Hello guys !

I'm new on this forum.

I have discovered the A-4E-C Skyhawk which is a very good Mod to fly. I fly frequently the AV8BNA and helicopters MI8 and Gazelle.

So. I use Touch Portal to create specific interfaces for the Mods I fly. The best one I've ceated is for the AV8BNA, using DCS-Coins and DCS-Bios.

With the AV8BNA, Touch Portal and DCS are working very properly. I can control many systems and I have the return back about the position or the situation of these systems to create animated buttons or to control a selector or an indication light on the Touch Portal Interface of the concerned aircraft.

With the A-4E-C Skyhawk V2.1, it doesn't work at all ! I have the DCS-COINS module for this aircraft and I have effectively on Touch Portal all the controls usable for the A4EC. But these controls don't work on DCS !

DCS is in version 2.8, the A4EC Mod is the 2.1 version and DCS BIOS and DCS-Coins are installed in there latest version.

Is there anybody to explain me my mistake ?

Thank's for help !

Link to comment
Share on other sites

On 4/23/2023 at 9:44 PM, SuperTonique said:

With the A-4E-C Skyhawk V2.1, it doesn't work at all ! I have the DCS-COINS module for this aircraft and I have effectively on Touch Portal all the controls usable for the A4EC. But these controls don't work on DCS !

DCS is in version 2.8, the A4EC Mod is the 2.1 version and DCS BIOS and DCS-Coins are installed in there latest version.

SuperTonique,

Please share your snapshot of "dcs-coins -v" output in command line - at the point when you load your your Skyhawk mission in DCS. I need to see the aircraft name as reported by DCS-BIOS.

There's also a new DCS-BIOS release by FP which I have yet to test and bundle with the DCS-COINS package. It may be a fix to the issue.

Changelog Planes:
#A-4E - changes from 2.1 patch

I have been "grounded" for the past few weeks due to a home project. Need to find time... please be patient and check-in here or the DCS-COINS download page once in a while.

Link to comment
Share on other sites

On 4/27/2023 at 3:33 AM, SuperTonique said:

THANK'S for your answer !

So, I'm so sorry but not very familiar with "command line"... I don't know what I've to do !

  1. Execute Touch Portal (if it's not loaded on start-up).
  2. From your Windows, right-click on the "Start" button and click on "Run".
  3. In Open field, type "cmd" (without the double quotes) and click "OK".
  4. In the pop-up window, type "cd \Users\"<your Windows user ID (eg. SuperTonique)>"\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS" and press ENTER.
  5. Type "dcs-coins -v" (again without the double quotes) and hit ENTER. You should get a series of messages indicating your selected aircraft modules and after that a series of event initialization, followed by DCS-BIOS events and TP response and commands on DCS execution. Note: If the A-4E-C is not listed in the list, you can run "DCS-COINS_Setup.exe" again to select it, and reload the generated TPP file into Touch Portal.
  6. Run DCS and load the Skyhawk mission.
  7. With that, switch back to the command prompt window, capture the output and paste it here.
  8. You may safely close the command prompt (and the dcs-coins program) after this.
Link to comment
Share on other sites

3 hours ago, xoomigo said:

capture the output and paste it here.

Many thank's fot your help. In fact, it's easy ! 😉

Here you are following the capture output...

 

Microsoft Windows [version 10.0.19044.2846]
(c) Microsoft Corporation. Tous droits réservés.

C:\Users\Admin>\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS
Le chemin d’accès spécifié est introuvable.

C:\Users\Admin>\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS
Le chemin d’accès spécifié est introuvable.

C:\Users\Admin>cd\Users\Admin\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS

C:\Users\Admin\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS>dcs-coins -v
DCS-COINS Version 3 (2210.07): Verbose mode enabled.
2023-04-28T20:06:10.745Z [INFO]  dcs-bios-api: parsed aircraft JSON - A-4E-C
2023-04-28T20:06:10.749Z [INFO]  dcs-bios-api: parsed aircraft JSON - AV8BNA
2023-04-28T20:06:10.755Z [INFO]  dcs-bios-api: parsed aircraft JSON - CommonData
2023-04-28T20:06:10.759Z [INFO]  dcs-bios-api: parsed aircraft JSON - MetadataEnd
2023-04-28T20:06:10.760Z [INFO]  dcs-bios-api: parsed aircraft JSON - MetadataStart
2023-04-28T20:06:10.769Z [INFO]  dcs-bios-api: parsed aircraft JSON - Mi-8MT
2023-04-28T20:06:10.776Z [INFO]  dcs-bios-api: parsed aircraft JSON - SA342
2023-04-28T20:06:10.782Z [INFO]  dcs-bios-api: parsed aircraft JSON - VNAO_T-45
2023-04-28T20:06:10.791Z [INFO]  dcs-bios-api: UDP client listening on 0.0.0.0:5010
2023-04-28T20:06:10.793Z : Munt.G_DCS-COINS :INFO: Connected to TouchPortal
2023-04-28T20:06:10.794Z : Munt.G_DCS-COINS :DEBUG: Info Message received
Aircraft: [NO]: Unavailable in installed DCS-COINS module list!
Aircraft: [A-NE]: Unavailable in installed DCS-COINS module list!
Aircraft: [A-4E-C]
CommonData:
Loading aircraft parameters from ./acdb/A-4E-C.pp
Event: mgdc_a-4e-c_st_aircraft_connection [ON] (a-4e-c: A-4E Skyhawk)
ALT_MSL_FT: 1
HDG_DEG: 1
HDG_DEG_FRAC: 0
DCS_BIOS: 0
PILOTNAME: 0
LAT_DEG: 0
LAT_SEC: 0
LAT_SEC_FRAC: 0
LAT_Z_DIR: 0
LON_DEG: 0
LON_SEC: 0
LON_SEC_FRAC: 0
LON_Z_DIR: 0
G_LOAD: 1
IAS_EU: 0
IAS_EU_INT: 0
IAS_US: 1
IAS_US_INT: 0
MISS_TIME: 1
MOD_TIME: 1
TIME_MODEL_HIGH: 0
TIME_MODEL_LOW: 0
TIME_START_HIGH: 0
TIME_START_LOW: 0
AFCS_1N2: 1
AFCS_1N2_COVER: 1
AFCS_AIL_TRIM: 1
AFCS_ALT: 1
AFCS_ENGAGE: 1
AFCS_HDG_100s: 0
AFCS_HDG_10s: 0
AFCS_HDG_1s: 0
AFCS_HDG_SEL: 1
AFCS_HDG_SET: 1
AFCS_PITCH: 0
AFCS_ROLL: 0
AFCS_STAB_AUG: 1
AFCS_STBY: 1
AFCS_YAW: 0
AOA_GREEN: 1
AOA_RED: 1
AOA_YELLOW: 1
D_ADVISORY_DIVE: 1
D_ADVISORY_INRANGE: 1
D_ADVISORY_SETRANGE: 1
CABIN_PRESS: 1
CABIN_TEMP: 1
WINDSHLD_DEFROST: 1
APC_ENABLE: 1
APC_LIGHT: 1
APS_COLD_STD_HOT: 1
ARM_BOMB: 1
ARM_EMERG_SEL: 1
ARM_FUNC_SEL: 1
ARM_GUN: 1
ARM_MASTER: 1
ARM_STATION1: 1
ARM_STATION2: 1
ARM_STATION3: 1
ARM_STATION4: 1
ARM_STATION5: 1
AWRS_DROP_INT: 1
AWRS_MODE: 1
AWRS_MULTI: 1
AWRS_POWER: 1
AWRS_QUANT: 1
MISSILE_VOL: 1
SHRIKE_SEL_KNB: 1
ACCEL_RESET: 1
ALT_PRESS_KNB: 1
AOA_INDEX_DIM: 1
FUEL_EXT_BTN: 1
IAS_INDEX_BTN: 1
IAS_INDEX_KNB: 1
MASTER_TEST: 1
OXY_SW: 1
RADAR_ALT_INDEX: 1
RADAR_ALT_SW: 1
RAIN_REMOVE: 1
STBY_ATT_INDEX_BTN: 1
STBY_ATT_INDEX_KNB: 1
BDHI_DME_FLAG: 0
BDHI_DME_Xxx: 0
BDHI_DME_xXx: 0
BDHI_DME_xxX: 0
BDHI_HDG: 0
BDHI_ILS_GS: 0
BDHI_ILS_LOC: 0
BDHI_MODE: 1
BDHI_NEEDLE1: 0
BDHI_NEEDLE2: 0
CURRTIME_HOURS: 0
CURRTIME_MINS: 0
CURRTIME_SECS: 0
STOPWATCH: 1
STOPWATCH_MINS: 0
STOPWATCH_SECS: 0
CM_ADJ1: 1
CM_ADJ2: 1
CM_AUTO: 1
CM_BANK: 1
CM_BANK1_Xx: 0
CM_BANK1_xX: 0
CM_BANK2_Xx: 0
CM_BANK2_xX: 0
CM_PWR: 1
APN153-DRIFT-GAUGE: 0
APN153-SPEED-Xnn: 0
APN153-SPEED-nXn: 0
APN153-SPEED-nnX: 0
ASN41-MAGVAR-Xxxxx: 0
ASN41-MAGVAR-xXxxx: 0
ASN41-MAGVAR-xxXxx: 0
ASN41-MAGVAR-xxxXx: 0
ASN41-MAGVAR-xxxxX: 0
ASN41-WINDDIR-Xxx: 0
ASN41-WINDDIR-xXx: 0
ASN41-WINDDIR-xxX: 0
ASN41-WINDSPEED-Xxx: 0
ASN41-WINDSPEED-xXx: 0
ASN41-WINDSPEED-xxX: 0
ASN41_LAT_SLEW: 1
ASN41_LON_SLEW: 1
ASN41_MAGVAR_BTN: 1
ASN41_MAGVAR_KNB: 1
ASN41_WINDDIR_BTN: 1
ASN41_WINDDIR_KNB: 1
ASN41_WINDSPEED_BTN: 1
ASN41_WINDSPEED_KNB: 1
DEST_LAT_BTN: 1
DEST_LAT_KNB: 1
DEST_LON_BTN: 1
DEST_LON_KNB: 1
DOPPLER_MEM_TEST: 1
DOPPLER_SEL: 1
NAV_DEAD: 1
NAV_SEL: 1
PPOS_LAT_BTN: 1
PPOS_LAT_KNB: 1
PPOS_LON_BTN: 1
PPOS_LON_KNB: 1
NAV_DEST_LAT_Xnnnn: 0
NAV_DEST_LAT_nXnnn: 0
NAV_DEST_LAT_nnXnn: 0
NAV_DEST_LAT_nnnXn: 0
NAV_DEST_LAT_nnnnX: 0
NAV_DEST_LON_Xnnnnn: 0
NAV_DEST_LON_nXnnnn: 0
NAV_DEST_LON_nnXnnn: 0
NAV_DEST_LON_nnnXnn: 0
NAV_DEST_LON_nnnnXn: 0
NAV_DEST_LON_nnnnnX: 0
APN153-MEMORYLIGHT: 1
NAV_CURPOS_LAT_Xnnnn: 0
NAV_CURPOS_LAT_nXnnn: 0
NAV_CURPOS_LAT_nnXnn: 0
NAV_CURPOS_LAT_nnnXn: 0
NAV_CURPOS_LAT_nnnnX: 0
NAV_CURPOS_LON_Xnnnnn: 0
NAV_CURPOS_LON_nXnnnn: 0
NAV_CURPOS_LON_nnXnnn: 0
NAV_CURPOS_LON_nnnXnn: 0
NAV_CURPOS_LON_nnnnXn: 0
NAV_CURPOS_LON_nnnnnX: 0
ECM_APR25_PW: 1
ECM_APR27_LIGHT: 1
ECM_APR27_PW: 1
ECM_APR27_TEST: 1
ECM_AUDIO: 1
ECM_MSL_VOL: 1
ECM_PRF_VOL: 1
ECM_SEL: 1
ECM_GO_LIGHT: 1
ECM_NOGO_LIGHT: 1
ECM_REC_LIGHT: 1
ECM_RPT_LIGHT: 1
ECM_SAM_LIGHT: 1
ECM_STBY_LIGHT: 1
ECM_TEST_LIGHT: 1
RWR_LIGHT: 1
HARNESS_REEL_CONTR: 1
SEC_EJECT_HANDLE: 1
D_FUEL: 0
D_FUEL_FLOW: 0
EGT_C: 0
OIL_PRESSURE: 0
PRESSURE_RATIO: 0
RPM: 0
RPM_DECI: 0
EXT_HOOK: 0
EXT_POSITION_LIGHT_LEFT: 1
EXT_POSITION_LIGHT_RIGHT: 1
EXT_SPEED_BRAKES: 1
EXT_STROBE_BOTTOM: 0
EXT_STROBE_TOP: 0
EXT_TAIL_LIGHT: 1
EXT_TAXI_LIGHT: 1
EXT_WOW_LEFT: 1
EXT_WOW_NOSE: 1
EXT_WOW_RIGHT: 1
DROP_PRESS_REFUEL: 1
EMERG_TRANS_FUEL_DUMP: 1
FUEL_CONTROL: 1
FUEL_TRANS: 1
MAN_FUEL_OFF_CATCH: 1
MAN_FUEL_OFF_LV: 1
GUNPOD_C: 1
GUNPOD_CLEAR: 1
GUNPOD_L: 1
GUNPOD_R: 1
D_GUNSIGHT_REFLECTOR: 0
GUNSIGHT_BRIGHT: 1
GUNSIGHT_DAY_NIGHT: 1
GUNSIGHT_KNB: 1
APG53A-GLOW: 0
LIGHTS-CONSOLE: 0
LIGHTS-FLOOD-RED: 0
LIGHTS-FLOOD-WHITE: 0
LIGHTS-INSTRUMENTS: 0
LIGHT_EXT_ANTICOLL: 1
LIGHT_EXT_FLASH_MODE: 1
LIGHT_EXT_FUSELAGE: 1
LIGHT_EXT_MASTER: 1
LIGHT_EXT_NAV: 1
LIGHT_EXT_PROBE: 1
LIGHT_EXT_TAIL: 1
LIGHT_EXT_TAXI: 1
LIGHT_INT_BRIGHT: 1
LIGHT_INT_CONSOLE: 1
LIGHT_INT_FLOOD_WHT: 1
LIGHT_INT_INSTR: 1
MCL_CHAN_SEL: 1
MCL_PWR: 1
ACCEL_CUR: 0
ACCEL_MAX: 0
ACCEL_MIN: 0
ADI_HDG: 0
ADI_OFF: 0
ADI_PITCH: 0
ADI_ROLL: 0
ADI_SLIP: 0
ADI_TURN: 0
ALT_ADJ_NNxx: 0
ALT_ADJ_xxNx: 0
ALT_ADJ_xxxN: 0
ATTGYRO_STBY_HORIZ: 0
ATTGYRO_STBY_OFF: 0
ATTGYRO_STBY_PITCH: 0
ATTGYRO_STBY_ROLL: 0
AngleOfAttack: 0
CABIN_ALT: 0
COMPASS_HDG: 0
D_ALT_100S: 0
D_ALT_10K: 0
D_ALT_1K: 0
D_ALT_NEEDLE: 0
D_IAS_DEG: 0
D_IAS_IDX: 0
D_IAS_MACH_DEG: 0
D_MACH_IDX: 0
D_OXYGEN_OFF: 0
D_RADAR_ALT: 0
D_RADAR_IDX: 0
D_RADAR_OFF: 0
LIQUID_O2: 0
VVI: 0
CANOPY_POS: 1
Canopy: 1
FLAPS: 1
GEAR_HANDLE: 1
GEAR_LIGHT: 1
HOOK_HANDLE: 1
JATO_ARM: 1
JATO_JETT_SAFE: 1
RUDDER_TRIM: 1
SEAT_ADJ: 1
SPEEDBRAKE: 1
SPEEDBRAKE_EMERG: 1
SPOILER_ARM: 1
STARTER_BTN: 1
THROTTLE_CLICK: 1
D_FLAPS_IND: 1
D_TAIL_HOOK: 0
GEAR_LEFT: 0
GEAR_NOSE: 0
GEAR_RIGHT: 0
RADAR_ANGLE: 1
RADAR_AOACOMP: 1
RADAR_MODE: 1
RADAR_VOL: 1
APG53A-BOTTOMRANGE: 0
APG53A-LEFTRANGE: 0
RADAR_BRILLIANCE: 1
RADAR_DETAIL: 1
RADAR_FILTER: 1
RADAR_GAIN: 1
RADAR_PROFILE: 1
RADAR_RANGE: 1
RADAR_RETICLE: 1
RADAR_STORAGE: 1
EMERG_BOMB_REL: 1
EMERG_GEAR_REL: 1
EMERG_GEN_BYPASS: 1
EMERG_GEN_DEPLOY: 1
MAN_FLIGHT_CONTROL: 1
TACAN_ANT_CONT: 1
TACAN_CHAN_MAJ: 1
TACAN_CHAN_MIN: 1
TACAN_MODE: 1
TACAN_VOL: 1
ARC51-FREQ-PRESET: 0
ARC51-FREQ-XXxxx: 0
ARC51-FREQ-xxXxx: 0
ARC51-FREQ-xxxXX: 0
ARC51_FREQ_10MHZ: 1
ARC51_FREQ_1MHZ: 1
ARC51_FREQ_50KHZ: 1
ARC51_FREQ_PRE: 1
ARC51_MODE: 1
ARC51_SQUELCH: 1
ARC51_VOL: 1
ARC51_XMIT_MODE: 1
D_CONTHYD_CAUTION: 1
D_FUELBOOST_CAUTION: 1
D_FUELTRANS_CAUTION: 1
D_GLARE_FIRE: 1
D_GLARE_IFF: 1
D_GLARE_LABS: 1
D_GLARE_OBST: 1
D_GLARE_WHEELS: 1
D_OIL_LOW: 1
D_OXYGEN_LOW: 1
D_RADAR_WARN: 1
D_SPDBRK_CAUTION: 1
D_SPOILER_CAUTION: 1
D_UTILHYD_CAUTION: 1
Event: mgdc_commondata_st_ias_us [47]
Event: mgdc_commondata_st_mod_time [1]
Event: mgdc_commondata_st_g_load [1.0]
Event: mgdc_commondata_st_g_load [1.1]
Event: mgdc_commondata_st_g_load [1.0]
Event: mgdc_commondata_st_mod_time [2]
Event: mgdc_commondata_st_mod_time [3]
Event: mgdc_commondata_st_mod_time [4]
Event: mgdc_commondata_st_mod_time [5]
Event: mgdc_commondata_st_mod_time [6]
Event: mgdc_commondata_st_mod_time [7]
Event: mgdc_commondata_st_mod_time [8]
Event: mgdc_commondata_st_mod_time [9]
Event: mgdc_commondata_st_mod_time [19]
Event: mgdc_commondata_st_mod_time [10]
Event: mgdc_commondata_st_mod_time [11]
Event: mgdc_commondata_st_mod_time [12]
Event: mgdc_commondata_st_mod_time [13]
Event: mgdc_commondata_st_mod_time [14]
Event: mgdc_commondata_st_mod_time [15]
Event: mgdc_commondata_st_mod_time [16]
Event: mgdc_commondata_st_mod_time [17]
Event: mgdc_commondata_st_mod_time [18]
Event: mgdc_commondata_st_mod_time [19]
Event: mgdc_commondata_st_mod_time [29]
Event: mgdc_commondata_st_mod_time [20]
Event: mgdc_commondata_st_mod_time [21]
Event: mgdc_commondata_st_mod_time [22]
Event: mgdc_commondata_st_mod_time [23]
Event: mgdc_commondata_st_mod_time [24]
Event: mgdc_commondata_st_mod_time [25]
Event: mgdc_commondata_st_mod_time [26]
Event: mgdc_commondata_st_mod_time [27]
Event: mgdc_commondata_st_mod_time [28]
Event: mgdc_commondata_st_mod_time [29]
Event: mgdc_commondata_st_mod_time [39]
Event: mgdc_commondata_st_mod_time [30]
Event: mgdc_commondata_st_mod_time [31]
Event: mgdc_commondata_st_mod_time [32]
Event: mgdc_commondata_st_mod_time [33]
Event: mgdc_commondata_st_mod_time [34]
Event: mgdc_commondata_st_mod_time [35]
Event: mgdc_commondata_st_mod_time [36]
Event: mgdc_commondata_st_mod_time [37]
Event: mgdc_commondata_st_mod_time [38]
Event: mgdc_commondata_st_mod_time [39]
Event: mgdc_commondata_st_mod_time [49]
Event: mgdc_commondata_st_mod_time [40]
Event: mgdc_commondata_st_mod_time [41]
Event: mgdc_commondata_st_mod_time [42]
Event: mgdc_commondata_st_mod_time [43]
Event: mgdc_commondata_st_mod_time [44]
Event: mgdc_commondata_st_mod_time [45]
Event: mgdc_commondata_st_mod_time [46]
Event: mgdc_commondata_st_mod_time [47]
Event: mgdc_commondata_st_mod_time [48]
Event: mgdc_commondata_st_mod_time [49]
Event: mgdc_commondata_st_mod_time [59]
Event: mgdc_commondata_st_mod_time [50]
Event: mgdc_commondata_st_mod_time [51]
Event: mgdc_commondata_st_mod_time [52]
Event: mgdc_commondata_st_mod_time [53]
Event: mgdc_commondata_st_mod_time [54]
Event: mgdc_commondata_st_mod_time [55]
Event: mgdc_commondata_st_mod_time [56]
Event: mgdc_commondata_st_mod_time [57]
Event: mgdc_commondata_st_mod_time [58]
Event: mgdc_commondata_st_mod_time [59]
Event: mgdc_commondata_st_mod_time [69]
Event: mgdc_commondata_st_mod_time [60]
Event: mgdc_commondata_st_mod_time [61]
Event: mgdc_commondata_st_mod_time [62]
Event: mgdc_commondata_st_mod_time [63]
Event: mgdc_commondata_st_mod_time [64]
Event: mgdc_commondata_st_mod_time [65]
Event: mgdc_commondata_st_mod_time [66]
Event: mgdc_commondata_st_mod_time [67]
Event: mgdc_commondata_st_mod_time [68]
Event: mgdc_commondata_st_mod_time [69]
Event: mgdc_commondata_st_mod_time [79]
Event: mgdc_commondata_st_mod_time [70]
Event: mgdc_commondata_st_mod_time [71]
Event: mgdc_commondata_st_mod_time [72]
Event: mgdc_commondata_st_mod_time [73]
Event: mgdc_commondata_st_mod_time [74]
Event: mgdc_commondata_st_mod_time [75]
Event: mgdc_commondata_st_mod_time [76]
Event: mgdc_commondata_st_mod_time [77]
Event: mgdc_commondata_st_mod_time [78]
Event: mgdc_commondata_st_mod_time [79]
Event: mgdc_commondata_st_mod_time [89]
Event: mgdc_commondata_st_mod_time [80]
Event: mgdc_commondata_st_mod_time [81]
Event: mgdc_commondata_st_mod_time [82]
Event: mgdc_commondata_st_mod_time [83]
Event: mgdc_commondata_st_mod_time [84]
Event: mgdc_commondata_st_mod_time [85]
Event: mgdc_commondata_st_mod_time [86]
Event: mgdc_commondata_st_mod_time [87]

Link to comment
Share on other sites

SuperTonique,

Looks like DCS-COINS is receiving DCS-BIOS data, and A-4E-C is setup and recognized.

Which controls have you tested which are not working? I have briefly tried a few and they worked except for the Canopy action.

Please share the segment of the output from DCS-COINS (command-line execution "dcs-coins -v") when you trigger a DCS-COINS action in TP. Expect the command to DCS-BIOS to be logged.


Edited by xoomigo
Link to comment
Share on other sites

On 4/30/2023 at 5:50 PM, xoomigo said:

SuperTonique,

Looks like DCS-COINS is receiving DCS-BIOS data, and A-4E-C is setup and recognized.

Which controls have you tested which are not working? I have briefly tried a few and they worked except for the Canopy action.

Please share the segment of the output from DCS-COINS (command-line execution "dcs-coins -v") when you trigger a DCS-COINS action in TP. Expect the command to DCS-BIOS to be logged.

 

I am sure you will laugh. I've tried the canopy command ! I've also tried with the spoilers arm control.

Yesterday, I have tried again with other controls yesteday evening and now it works nicely. I have install the latest A-4E-C version 2.1.1

Many thank's for your help and your work on the A4. It's a great plane very pleasant to fly.

Link to comment
Share on other sites

  • 3 months later...

Hello guys !

I hope somebody will help me...

My problem is the following :

- I have re-installed DCS-Bios and DCS-COINS because after the SA342 module DCS-BIOS was installed, touch portal didn't work normally.

- Now touch portal is working in only one way. The way workink is from DCS to TouchPortal. When I modifie the position of one control (switch for exemple) on DCS Screen, the switch on Touch Portal take the right new position. But if I try to modifie this switch from Touch Portal, the switch doesn't activate the control on DCS screen.

- I think that DCS-Bios is correctly installed because Helios is perfectly working.

- I think that the problem is comming from DCS-COINS installation. But I can't know where ! I have re-installed many time DCS-Coins without any success.

Is there somebody who has an idea about a solution ?

I have DCS 2.8 and DCS-COINS 2022-11-11.

Thank's for help.

Link to comment
Share on other sites

On 8/16/2023 at 12:36 AM, SuperTonique said:

Hello guys !

I hope somebody will help me...

My problem is the following :

- I have re-installed DCS-Bios and DCS-COINS because after the SA342 module DCS-BIOS was installed, touch portal didn't work normally.

- Now touch portal is working in only one way. The way workink is from DCS to TouchPortal. When I modifie the position of one control (switch for exemple) on DCS Screen, the switch on Touch Portal take the right new position. But if I try to modifie this switch from Touch Portal, the switch doesn't activate the control on DCS screen.

- I think that DCS-Bios is correctly installed because Helios is perfectly working.

- I think that the problem is comming from DCS-COINS installation. But I can't know where ! I have re-installed many time DCS-Coins without any success.

Is there somebody who has an idea about a solution ?

I have DCS 2.8 and DCS-COINS 2022-11-11.

Thank's for help.

Hi SuperTonique,

You are the first that I know who are using the plugin for SA342 Gazelle. I do not have this module.

DCS-COINS is merely a vessel to enable Touch Portal to interface with DCS with DCS-BIOS enabling the actual communication (commands and status updates between them).

From the sound of it, it appears to be a DCS-BIOS bug. Not all aircraft module parameters were 100% tested by end-users and some bugs were unknown or unreported for even older modules. I myself found a few in the Mosquito, and another (I believe it's the Hornet) - which either does not work or was labelled incorrectly. At least one or two DCS-COINS users had tried using it with the A-10C and encountered some issues for a few controls as well.

Option is to hope that it gets fixed in future DCS-BIOS releases - you can file a bug report with the developers. And sorry, I don't have any connections with them.

Cheers.

xoomigo

Link to comment
Share on other sites

  • 4 weeks later...

Hi all,

DCS-COINS release 2023-09-09 is now available.

- Fixed: F/A-18 Hornet variants not recognized
- Fixed: C-101 and variants not recognized
- Added: F-15E, MB-339 and Blackshark 3 support
- PP files updated with FlightPanels' DCS-BIOS v0.7.49
  (Refer https://github.com/DCSFlightpanels/dcs-bios/releases)

https://www.digitalcombatsimulator.com/en/files/3319022/

Cheers!

1 hour ago, Tanuki44 said:

Hello  xoomigo,

Sorry to reply so late, but the end of August was very complicated.

Here are the files I created

I don't really understand the "outputs" *.json file structure 

Thanks for your help

MH-60R.jsonpMH-60R.jsonMH_60R.luaBIOS.luaMH-60R.ppaircraftModules.pp

Munt.G_DCS-COINS.tpp 22.81 MB · 0 downloads

Hi Tanuki44,

Got it. I will take a look tomorrow and get back to you as soon as I can.

Thanks.

  • Thanks 2
Link to comment
Share on other sites

1 hour ago, xoomigo said:

DCS-COINS release 2023-09-09 is now available.

Great update, thanks for it!

I want to ask about Ka-50 III. When I start dcs-coins -v, I can see that various mgdc_commondata_* is coming in for L-39 or UH-1H, but not for Ka-50. Is that COINS or rather DCS BIOS problem?

I also tried to flip some switches, but these didn't log anything either, so it's not only common data, so it seems.

BTW: Have you been thinking about that GitHub or other project for DCS COINS? 🙂


Edited by virgo47

✈️ L-39, F-5E, F/A-18C, MiG-15, F-86F, C-101, FC2024 🛩️ Yak-52, P-47, Spitfire 🚁 UH-1H, Mi-8, Ka-50 III, SA342 🗺️ NTTR, PG, SY, Chnl, Norm2 📦 Supercarrier, NS430, WWII, CA 🕹️ VKB STECS+Gladiator/Kosmosima+TPR ▶️ DCS Unscripted YouTube 🐛 "Favourite" bugs: 1) gates not growing regress, 2) L-39 target size cockpit animation regress, 3) Yak-52 toggles not toggling, 4) all Caucasus ATC bugs

Link to comment
Share on other sites

2 hours ago, xoomigo said:

Hi all,

DCS-COINS release 2023-09-09 is now available.

- Fixed: F/A-18 Hornet variants not recognized
- Fixed: C-101 and variants not recognized
- Added: F-15E, MB-339 and Blackshark 3 support
- PP files updated with FlightPanels' DCS-BIOS v0.7.49
  (Refer https://github.com/DCSFlightpanels/dcs-bios/releases)

https://www.digitalcombatsimulator.com/en/files/3319022/

Cheers!

Hi Tanuki44,

Got it. I will take a look tomorrow and get back to you as soon as I can.

Thanks.

I forgot the entry.tp

entry.tp

Link to comment
Share on other sites

8 hours ago, virgo47 said:

I want to ask about Ka-50 III. When I start dcs-coins -v, I can see that various mgdc_commondata_* is coming in for L-39 or UH-1H, but not for Ka-50. Is that COINS or rather DCS BIOS problem?

I also tried to flip some switches, but these didn't log anything either, so it's not only common data, so it seems.

Ka-50_3 is only supported in DCS-BIOS version 0.7.49.

The "aircraft connection" event is crucial for DCS-COINS to determine the PP file to load the actions and events to interface with TP. If the aircraft connection parameter is not forthcoming or updated, the plugin will not recognize/respond to the TP aircraft-specific commands.

8 hours ago, virgo47 said:

BTW: Have you been thinking about that GitHub or other project for DCS COINS? 🙂

Yup, it's on my to-do list. 😉

 

Link to comment
Share on other sites

11 hours ago, Tanuki44 said:

I don't really understand the "outputs" *.json file structure

Frankly, neither do I. Basically, I just mined (programmatically extract keywords and their associated values) the DCS-BIOS json files to generate the PP files.

But if I had read you wrong and you have the json file already complete and ready, I get use it to generate the PP file concerned.

I will get back to you on the PP file details.

Link to comment
Share on other sites

5 hours ago, xoomigo said:

Ka-50_3 is only supported in DCS-BIOS version 0.7.49.

Ah, yes, my bad, I forgot that DCS-BIOS is not updated automatically. I removed the old one, DCS-COINS installer installed the new one and my Black Shark III reports properly again.

I wrote it to my notes, because I do it so rarely, that I bet it's not the first time I forgot to remove the old DCS-BIOS. 🙂

✈️ L-39, F-5E, F/A-18C, MiG-15, F-86F, C-101, FC2024 🛩️ Yak-52, P-47, Spitfire 🚁 UH-1H, Mi-8, Ka-50 III, SA342 🗺️ NTTR, PG, SY, Chnl, Norm2 📦 Supercarrier, NS430, WWII, CA 🕹️ VKB STECS+Gladiator/Kosmosima+TPR ▶️ DCS Unscripted YouTube 🐛 "Favourite" bugs: 1) gates not growing regress, 2) L-39 target size cockpit animation regress, 3) Yak-52 toggles not toggling, 4) all Caucasus ATC bugs

Link to comment
Share on other sites

5 hours ago, xoomigo said:

Frankly, neither do I. Basically, I just mined (programmatically extract keywords and their associated values) the DCS-BIOS json files to generate the PP files.

But if I had read you wrong and you have the json file already complete and ready, I get use it to generate the PP file concerned.

I will get back to you on the PP file details.

Unfortunately, there is no DCS BIOS file for this mod.
Attached is the clickabledata.lua file if it is useful for building the MH-60R.pp

I'm looking for the DCS-BIOS contact, it seems they can add the mode to their work...
Thanks for your help

 

clickabledata.lua

Link to comment
Share on other sites

1 hour ago, virgo47 said:

Ah, yes, my bad, I forgot that DCS-BIOS is not updated automatically. I removed the old one, DCS-COINS installer installed the new one and my Black Shark III reports properly again.

I wrote it to my notes, because I do it so rarely, that I bet it's not the first time I forgot to remove the old DCS-BIOS. 🙂

Ah, great to hear that it's working for you now. 😄

Link to comment
Share on other sites

58 minutes ago, Tanuki44 said:

Unfortunately, there is no DCS BIOS file for this mod.
Attached is the clickabledata.lua file if it is useful for building the MH-60R.pp

I'm looking for the DCS-BIOS contact, it seems they can add the mode to their work...
 

Unfortunately, I am no good with LUA. 😅

Yes, it would be great if someone from FlightPanels mod team can build the support for your mod. Once done, let me know and I will generate the PP file for it.

Anyway if you or anyone is still interested, here's the PP record structure:

  1. paramID:  Aircraft parameter ID
  2. tpstID: TP State ID
  3. tpstDesc: TP State Description
  4. tpActionType: TP Action Type: (0: No action)
    1. "set_state"
    2. "fixed_step" DEC INC by 1
    3. "variable_step" -<num> +<num>|"suggested_step":<num>
    4. "action": arg:"TOGGLE"
    5. "hold"/"set_state"
    6. "connector/slider control/variable_step" (superset of "3")
  5. tpActionStep: Increment/decrement value
    1. tpActionType 1: "0"
    2. tpActionType 2: "0"
    3. tpActionType 3:  <"incr/decr value eg. 1, 3200">
    4. tpActionType 4: "0"
    5. tpActionType 5: "0"
    6. tpActionType 6: <"incr/decr value eg. 1, 3200">
  6. tpValType: Data type, enumerated list of options
  7. tpstDef: Default/Starting value in TP

 

Link to comment
Share on other sites

3 hours ago, Tanuki44 said:

If we could generate the pp file without the json, would that work ? or is it absolutely necessary ?

Sadly, no. The JSON file is part of the DCS-BIOS mechanism to work a specific aircraft module. The JSON file for each aircraft selected during DCS-COINS setup is also replicated into the TP plugin folder - as it is also needed by the "dcs-bios-api" (a 3rd party library by Daniel Tian) which made DCS-COINS possible.

Were you able to get any of the FP's DCS-BIOS modder to commit on supporting your mod?

Link to comment
Share on other sites

  • Recently Browsing   0 members

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