Lasko

New version released today. Ka-50 was added, M2000C entry was fixed, and some other minor updates. v1.2.3 Feature Changes: Ka-50 Black Shark support added. Up to 6 waypoint (WP) and up to 9 target (TG) points can be entered. Region select changed to a pull-down list. On startup, all JSON files in the ./data directory are read and added to the preset location list. Files that contain a "region" -> "name" value will be added to the region selection list. Selecting a region name will load only those waypoints. Selecting the blank region name will reload all JSON files. Added a filter button to the profile list. Bug Fixes: Updated M2000C key sequences, coordinates now support 3 digit decimal minutes. Waypoints over the aircraft limit were not being skipped correctly. F18 MSN is reset to PP1 after entering multiple targets. Selecting a MSN waypoint from the profile waypoint list displays the correct station number.

I think it probably is wrong. I updated the M2000C key sequences using Chuck's Guide. The attached file has the new keypresses for two waypoints. I don't have M2000 installed to test. If you can try that key sequence to see if it works, I can include it in the next update. mirage_wp.txt

There will be an entry in the log something like this that shows what OCR found: 2022-10-10 07:10:00,570:gui: DEBUG - Raw captured text: 24°27°11"N 56°01 '05"E, 1624 ft 2022-10-10 07:10:00,573:gui: DEBUG - Text found 24°27°11"N 56°01 '05"E, 1624 FT but did not match any known pattern. Here it put an extra space in the longitude between 01 and '05, so it could not parse the text. If it persists, change to a different coordinate format (LAlt-Y) and use DD-MM-SS.ss or MGRS. Another option is to install DCSTheWay and use the Capture F10/F11 View instead.

I don't see anything changed wrt harrier. Is there something else going on, dcs-bios problem or something else?

Here's an update for v1.2. I haven't had time to work on the bugs in v1.3 send via LUA, so I rolled all of the other changes in to v1.2.2. v1.2.2 Redesigned the window layout to reduce size. Grouped the capture buttons together and changed the titles: Capture Coordinates - Single OCR capture from F10 map to the Position frame Capture To Profile - Toggle on OCR capturing to the profile list and Position frame. Remains active until canceled. Capture F10/F11 View - Toggle on non-OCR F10 or F11 view coordinate capture to the profile list and position frame. Remains active until canceled. "Stop capturing" button corresponds to the current capture mode. Previously was always on "Capture from F10 Map." Added a definable hotkey for "Capture F10/F11 View," default is ctrl-shift-u. Fixed field alignment in the settings window.

A new beta release is available for testing. This release contains a GUI redesign, and the option of sending aircraft commands through TheWay.lua instead of DCS-BIOS. This is experimental and currently available for 3 aircraft. For other aircraft, continue using DCS-BIOS. v1.3.0-b1 Pre-release Redesigned the window layout to reduce size. Grouped the capture buttons together and changed the titles: Capture Coordinates - Single OCR capture from F10 map to the Position frame Capture To Profile - Toggle on OCR capturing to the profile list and Position frame. Remains active until canceled. Capture F10/F11 View - Toggle on non-OCR F10 or F11 view coordinate capture to the profile list and position frame. Remains active until canceled. "Stop capturing" button corresponds to the current capture mode. Previously was always on "Capture from F10 Map." Added a definable hotkey for "Capture F10/F11 View," default is ctrl-shift-u. Added an option to send aircraft commands through TheWay.lua instead of DCS-BIOS. Aircraft commands are implemented for A-10C, AH-64D and F/A-18C. This functionality is currently experimental, and does not work for F/A-18C weapon missions. Entry of waypoints is much faster through this method.

A new version is now available with a few minor bug fixes. v1.2.1 Persian Gulf locations file - Corrected all airport locations, added all elevations. Added a File menu entry to run Target-jar-wtih-dependencies.jar. AH-64D 3-character FREE field will ignore spaces. Al Minhad becomes ALM, Al Dhafra becomes ALD. Name field is not reset to NULL when capturing coordinates. Default aircraft type list uses the aircraft name instead of driver name. For example, F/A-18C instead of hornet.

Are you positive the WP1 isn't coming from the mission editor? I don't know anything about the Harrier or have it to experiment, but if it is really creating a random WP1 that seems like a bug.

I think I follow what you're saying now, but this won't work for everyone. For example, in multiplayer you are given a pre-configured jet with waypoints 1 through X and anything you want to enter as a user defined point will be X + 1.

What is the significance of the first entered point being #2 instead of #1? Isn't the number of points initially programmed dependent on the mission editor, and how would we know which point number to use? I'm still not getting it I guess. Also how would you enter points 1, 2, and 3, and then add points 4, 5 and 6? Without know the number of points that already exist, it seems like the only reliable thing you can do is add a new point to the end. Otherwise you have to know in advance if you are adding or editing a particular point.

I honestly don't understand the WP1 issue. Are you saying WP1 should be deleted before entering more? I could do that but will need to know the keys to use. Also how would it know if WP1 exists or not when entering subsequent points?

The release version v1.2.0 is now available. DCS Bios published a new release with AH-64D support, and AH-64D support is now complete: v1.2.0 Feature Changes: AH-64D Pilot and CPG support. The first three characters of the waypoint name are entered in the FREE field. Added waypoint types HZ, CM and TG for AH-64D. DCS BIOS v0.7.45 is required for AH-64D support. An Update button is now available in the Settings window. Added a capture option for the The Way LUA data source. This capture source does not use Tesseract or OCR. If you have previously installed The Way in Export.lua, the "Capture from The Way" button will connect to the data source and capture the coordinates for the current camera view. When on the F10 map, it captures the coordinates of the center of the map. A target dot in the center of the map can be displayed using The Way, or the included Target-jar-with-dependencies.jar which requires Java JRE. Default aircraft type added to the Settings window. This previously was set to "hornet" automatically. Bug Fixes: Corrected the key sequences for F-16C. Added decimal fill for F-16C coordinates, e.g. 04107.500 instead of 04107.5 Enforced the A-10C waypoint name limit of 12 characters, the name is now truncated. Allow lowercase when entering MGRS coordinates. Retain the "Name" field when updating MGRS coordinates.

New version up, hopefully this fully fixes the F16 key sequences. v1.2.0 Beta 4 Added decimal fill for F16 coordinates, e.g. 04107.500 instead of 04107.5

New version is up with F16 fixes, and new waypoint types for AH64D: v1.2.0 Beta 3 Added waypoint types HZ, CM and TG for AH-64D. Enforced the A-10C waypoint name limit of 12 characters, the name is now truncated. Corrected the key sequences for F-16C Set the current default aircraft after using the Settings window As far as VR, I don't remember seeing anything mentioned about it is any of the DCSWE threads here or Reddit. I'm willing to put in a fix for it, but it's not clear what would be changed at this point. The way I understand it, waypoints are just added to the end of the existing list, assuming there aren't already more than 77. Is there something else that needs done now?

Thanks, good to know. For now I will leave it as 77. I added default aircraft type in the AH64D update, and the next version will make sure the correct default is set when selecting a new blank profile. The next version will also have new waypoint types (HZ CM TG) for AH64 and fixes for F16, I just need to get a sense that what I have put in is correct. The updated key sequence for F16 is in https://github.com/atcz/DCSWaypointEditor/issues/1

It looks like the 77 is arbitrary, a different implementation uses 99. Are you sure that's the problem? It might be related to this: DCS: AV-8B N/A by RAZBAM Simulations Fixed: Steerpoint elevation is automatically updated when entering coordinates

A new version is now available with working AH64 waypoint entry. DCS Bios has to be fully updated from the DCSFlightpanels/dcs-bios repository. There are changes in multiple files, beyond just the two that I originally thought were needed. v1.2.0 Beta 2 Corrected AH64D sequences. The first three characters of the waypoint name are entered in the FREE field. Set default aircraft when loading a blank profile. Added debug output for F16 keypresses.

https://github.com/DCSFlightpanels/dcs-bios/releases I've been using DCS-BIOS_0.7.44.zip for all testing. Also if you want to use the AH64D, you need the updated BIOS.lua and lib/AH-64D.lua from the repository which have not been packaged in a release yet.

I don't have any knowledge about that part of the code or interaction with DCS Bios. Since you mentioned UFC, I assume this is for F18? I time it as entering 16 digit waypoint in 12 seconds, or mission point with elevation in 16 seconds. That does not seem unreasonable.

Not sure if that is possible, and the altitude being on a separate line complicates it. To be really precise, I would zoom the map in far enough to provide better accuracy.

I've been doing updates on it the since February, check it out: https://github.com/atcz/DCSWaypointEditor/releases I just added the AH64 (not tested) and capture from The Way yesterday.

Good catch, that will never work. You might try the new version that uses the LUA capture. It doesn't need to read anything from the screen so that would work fine.

You might want to try using DCS Waypoint Editor which includes support for import/export and saved profiles. I also just added the ability to capture coordinates using the data source from The Way Export.lua method.

A beta version for Apache support was just published. I also added a capture option to the use the same method as The Way to capture coordinates without using Tesseract OCR. This works by moving the center point of the F10 map to the coordinates you want to capture, then retrieving the camera position directly from DCS. v1.2.0 Beta 1 Added AH64D Pilot and CPG support. Apache functions are preliminary and have not been tested. The key sequences were created based on the ED Apache Quick Start Manual. Apache support also requires updated DCS Bios. Added settings option for default aircraft type. This previously was set to "hornet" automatically. Added capture option for the The Way LUA data source. If you have previously installed The Way in Export.lua, the "Capture from The Way" button will connect to the data source and capture the coordinates for the current camera view. When on the F10 map, it captures the center of the map. The Way displays a dot in the center of the display to mark the location being captured, which does not seem possible in Python. The target dot can be displayed using The Way, or the included Target-jar-with-dependencies.jar which requires Java JRE.

I found the problem, not sure what the fix is. The screen scaling is different, so the sample MAP text is not the right size. If it doesn't find a 90% match it assumes it did not find the F10 map. The top one if from your image, second is what it is looking for, and third is the one I get for 1080 screen capture. Do you have font scaling or GUI scaling turned on?