search

51st-Vfw / JAFDTC

JAFDTC DTC tool for DCS
GNU General Public License v3.0
0 stars 1 forks source link

AV8B #2

Open MadogPL opened 6 months ago

MadogPL commented 6 months ago

Hallo!

I'm the guy from this thread: https://github.com/51st-Vfw/DCSWaypointEditor/issues/29#issuecomment-1867160420

and again, I'm late to test things, but I finally did it.

I've just tested the newest build, and generally harrier does not work at all :P

It starts inputing things but after initial data edit mode - it goes south.

IF you need any help - I promise I will be responsive and provide any help you need :)

I guess this is the function I've requested for the harrier as a "edit not add waypoint" right?

image

ilominar commented 6 months ago

Yes, I figured you'd drop by eventually.

And you're correct: that checkbox is supposed to do the "edit not add" thing.

Sorry about the issues, I don't own the module and our Harrier squadron shut down a while back, so it's been hard to test.

I'll take a look and see if I see anything obvious since it was based off the DCSWE code that did work. I probably need to break down and buy the module to make debug easier though.

What would be helpful is if you could send me a configuration for a very simple setup (like 1-2 waypoints). You can find configurations in Documents/JAFDTC/Configs/AV8B. Just ship me the .json for the short test configuration (if you name it "test" it will be something like "test.json"). I can turn on some debug code and ship you a list of what buttons are being pressed as a starting point. If that's correct, it may be either a screw up in the button to DCS device ID mapping or JAFDTC may be mashing buttons too fast for the module.

ilominar commented 6 months ago

I found a bug that may have been the source of the problem (the ODU_OPT2 command was being sent to the wrong aircraft device). Fix will be in the next release.

As a checkpoint, when entering a single waypoint at N 41 36' 33'' E 41 36' 00'' with "Add Waypoints to Avionics Following Last Known Waypoints" not set, the following keys are pressed:

LMPCD.MPCD_L_2
UFC.7
UFC.7
UFC.UFC_ENTER
ODU.ODU_OPT2
UFC.2
UFC.4
UFC.1
UFC.3
UFC.6
UFC.3
UFC.3
UFC.UFC_ENTER
UFC.6
UFC.0
UFC.4
UFC.1
UFC.3
UFC.6
UFC.0
UFC.0
UFC.UFC_ENTER
ODU.ODU_OPT1
LMPCD.MPCD_L_2

with "Add Waypoints to Avionics Following Last Known Waypoints" set, the following keys are pressed,

LMPCD.MPCD_L_2
UFC.0
UFC.1
UFC.UFC_ENTER
ODU.ODU_OPT2
UFC.2
UFC.4
UFC.1
UFC.3
UFC.6
UFC.3
UFC.3
UFC.UFC_ENTER
UFC.6
UFC.0
UFC.4
UFC.1
UFC.3
UFC.6
UFC.0
UFC.0
UFC.UFC_ENTER
ODU.ODU_OPT1
LMPCD.MPCD_L_2

Let me know if those sequences are correct.

MadogPL commented 6 months ago

2 Waypoints.json

MadogPL commented 6 months ago

looks correct :)

I don't think it's mashing too fast. The WayPoint Editor has TheWay support, it's like the fastest typing input that I've seen and it has no problems.

ilominar commented 6 months ago

This will be rolled in to the next beta (due next few days).

MadogPL commented 5 months ago

no joy on beta.31

It types mambo jumbo with no sense.

MadogPL commented 5 months ago

@ilominar

I've recorded you a video :) Maybe it will help.

https://youtu.be/NCycvaHn7i4

ilominar commented 5 months ago

Hmmm. Ok, will take a look again. Think I need to break down and buy the module...

ilominar commented 5 months ago

Also, one other thing that would be helpful is if you could attempt to load something, quit out of JAFDTC and DCS then send along the Documents/JAFDTC/jafdtc-log.txt and Logs/JAFDTC.log from your DCS directory in Saved Games (mine is Saved Games/DCS.openbeta, path may be slightly different based on what version of DCS you have).

MadogPL commented 5 months ago

jafdtc-log.txt