Lasko

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?

The F10 map not found issue is a tough one, I haven't figured out what triggers it. There is something with the way the screen capture interacts with DCS that the screen isn't always complete, or is just a blank base map. However... In the screen capture you posted, the DCSWE window is obscuring the coordinates at the top. The screen capture looks for the blue MAP letters, then finds the numbers to the right of it. Anything obscuring that like in the screen capture, the frame rate display, SRS window or anything else in the top left corner will make it fail. Here is the sample it is looking for: But this example here will definitely cause it to fail because the sample MAP that it looks for won't be found. One other thing you can do is change settings.ini save_debug_images = true. This will save the images that it captures in a directory for each capture attempt. When you get an F10 error, the image should show you what was captured and it will probably be obvious why it couldn't find the blue MAP letters.

PM me if you are interested in testing the Apache Pilot and CPG that I'm working on. DCS Bios has updated files available, not packaged in a release yet. I built a framework for it based on available templates but don't have the Apache to actually try it out.

"No matching pattern" means that Tesseract mangled the characters somehow, either misidentifying a character or adding something that isn't there. The log.txt file will tell you what it found, just look for the "Raw captured text" line. Version 1.1.1 has two fixes for this. Extra phantom characters at the beginning of the line like the ‘N reported by @P-inna are ignored, and I also found it was seeing * or ° instead of " in DD MM SS format and it will now accept any of those.

A new version with some minor fixes was just made available: https://github.com/atcz/DCSWaypointEditor/releases v1.1.1: Added a confirm popup for Delete Profile. Added an overwrite popup for Save and Save As if an existing profile name is entered. Tesseract occasionally adds a random phantom character at the beginning of the line. This character is now ignored as long as the text string otherwise matches an expected pattern.

The problem is the ‘N that it found, not sure what that symbol is or how it found it, but that is throwing it off. I will have to see if there is a way to have it ignore anything before N/S. Otherwise it looks like you have everything working.

Sometimes tesseract is glitchy with finding characters that aren't there. In the log.txt it will record what it found, something like this: 2022-04-22 11:23:06,438:gui: DEBUG - Raw captured text: 42°46'46"N 41°47'04*E, 2918 ft 2022-04-22 11:23:06,441:gui: DEBUG - Text found 42°46'46"N 41°47'04*E, 2918 FT but did not match any known pattern. Here it put in a * instead of " and that one I've seen before. I will add to the regex in the next release to allow * in that spot. You can change coordinate format with Lalt-Y and I have the best luck with ddd mm ss.ss or MGRS formats. You should not need to run as administrator. I think there was something mentioned in DCS-BIOS about running as administrator but for what we're doing it's not needed and I don't run it that way. IMO, anything that makes you run as administrator is just forcing you into a workaround for bad coding, in most cases.

Final version 1.1.0 is available now: https://github.com/atcz/DCSWaypointEditor/releases

I have it working, and it will add any line starting with FIX and containing four fields as a waypoint or mission point. Not sure if there can be other data in the file, or if it is appropriate to import something other than FIX.

That doesn't seem like it would be a problem, there is already code to do an import from the clipboard or a file. If someone can attach an export file I will take a look at it. Can probably implement it as import or export.