Lasko

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.

New version up just now: v1.1.0-rc3 Created a "File" menu to access the Settings window or Exit. Added a selectable setting for PySimpleGUI Theme to choose any of the available color themes. Moved setup specific functions to first_setup.py

Thanks, I noticed the version number after posting it and it will get fixed for the release version. I've been using it quite a bit, and it's fun launching 8 JSOW or 8 JDAM and watching them all hit from external view. It would take 10 minutes to program in all the coordinates separately. This needs an AH-64 driver written for it now, will have to figure out how you get the display names and button presses for it.

Definitely something went wrong building that, new version is up now. I also added handling empty elevation, so if you enter lat/lon or MRGS then "Add" it will just add it and set elevation to zero. https://github.com/atcz/DCSWaypointEditor/releases/tag/v1.1.0-rc2

There is one last change for this round of updates. The mission order entry for F18C is changed from 8-7-3-2 to 8-2-7-3 which is the order the aircraft "Step" button uses. Before, if you were entering 4 mission coordinates you had to select station 7 for the target you wanted on station 2, etc. The caveat is that if you have saved mission profiles they may need updated to match the new order. https://github.com/atcz/DCSWaypointEditor/releases/tag/v1.1.0-rc1 I've been using this version for a couple of days and it seems solid.

It's hard to tell what they meant by Capture and Quick Capture. The terms are used interchangeably in the code, but I fixed it so the Quick Capture hotkey does the same as clicking "Quick Capture." There is a bug of sorts that if the first thing you do is Ctrl-Shift-T it will ignore it because the window is not initialized until some other action, clicking a button, etc. There are a couple of other things included that I was testing out. "No matching pattern" should not happen often, and usually is because OCR completely misses a letter. The "F10 map not found" problem is either something in the Python Desktopmagic library, or in the way DCS is drawing the screen. When you get that error, it is usually because the captured image is just a blank map like this: v1.0.1-beta-6 Quick Capture hotkey now works the same as clicking "Quick Capture." Added success and error sound files for capture feedback. Capture status will now show a failure reason: F10 map not found - Captured image did not include coordinates. No matching pattern - Text found but did not match a pattern we are looking for. Removed some unused code related to Tomcat alignment

Another minor update added today: v1.0.1-beta-5 Added sorting for the profile list. Moved the "Enter into aircraft" button next to the Add/Update/Remove buttons. Removed Qty selection from F18 MSN points, there is no way to know which stations to select. F18 MSN entry now selects PB19 Return when done, was selecting PB6 which incorrectly selects TOO mode.

After deleting the profile instead of the waypoint for the idon'tknowhowmanyth time, I posted a minor beta4 update today. The profile buttons are moved to the Profile menu, and the waypoint action buttons are moved the center right. I think the layout is more intuitive and less prone to error, let me know what you think. Also a few typos were fixed in cauc.json, airport waypoints should now all match the center of the runway.

I was able to use it a bit yesterday and it seems fine so far. A new beta3 release is available now: https://github.com/atcz/DCSWaypointEditor/releases I'm still looking at the F-18 mission loading but haven't figured out what is wrong with it. Sometimes it loads the correct stations, other time not. It also keeps switching to TOO mode after loading the coordinates, so something is wrong there. It will take some more time to look further into those issues.

I'm working with a test version that has a "Save As" button, and fixed a crash when deleting a profile. I've also gone through the cauc.json file and updated the airports with the runway lat/lon/elev. I will get something out in a few days after I have a chance to test it out.

Here you go: https://github.com/atcz/DCSWaypointEditor/releases/tag/v1.0.1b2

There is a test release available now v1.0.1b1: https://github.com/atcz/DCSWaypointEditor/releases I still want to do some more with it like straighten out the F18 MSN routines, but the other bugs were annoying and easy to fix.

Unless you build it yourself from the source files you won't see the change. I'll get a test release built this morning, probably with the AV8 test code. If DCS bios you have is working I wouldn't worry about touching it. I don't have any experience with Python before this, but I'm getting it figured out.

The only mod I have is F18, but AV8 looks simple enough. Is that the odu("2") in between enter lat and enter lon? For North: ufc("2") For South: ufc("8") enter_number(lat_str) -> odu("2") For East: ufc("6") For West: ufc("4") enter_number(lon_str) odu("2")

I've made some of the fixes people have asked for, and made the UI E/W friendly. I'm not sure how to build a downloadable version, but the source files are at: https://github.com/atcz/DCSWaypointEditor Here's the notes on changes in my version: - The version nag window does a number compare instead of text compare to eliminate false alerts. - Added N/S/E/W radio buttons, adjusted frame alignments. - Created data files for Marianas, Nevada and Syria airports. - Added buttons for preset location to load only Caucasus, Marianas, Nevada, Persian Gulf or Syria airports. - Fixed some of the OCR issues: - Negative altitude was not being recognized, now found and adjusted to zero. - MGRS parsing misses a space, e.g. 40 RCM or 40R CM instead of 40 R CM. The spaces are now optional. - Added a replace to change ) to J, and £ to E. Whitelist would be better, but could not get it to work. 2022-03-01 17:31:11,441:gui: DEBUG - Raw captured text: N26°28.412 £49°37.163, 91 ft 2022-03-01 17:31:11,494:gui: DEBUG - DD MM.MMM input found: 26 28.412 N 49 37.163 E 2022-03-01 17:31:48,532:gui: DEBUG - Raw captured text: 39 RY) 37006 31277, -117 ft 2022-03-01 17:31:48,595:gui: DEBUG - MGRS input found: 39RYJ3700631277 - OCR was mixing up ° and ', will now accept either one. - It still sometimes fails for no apparent reason. The screen is captured with no top bar and no overlays, or just a partial image. - Capturing should no longer become unresponsive after a failure to parse the text string, and a debug is logged: "Text found " + coords_string.rstrip() + " but did not match any known pattern. Sorry about that." - Updated the DCS bios version to 0.7.44. - Changed the GUI theme to 'Reddit'.