Lasko

F-15 fixes are released in version v1.3.2: v1.3.2 Feature Changes: F-15E: Sequences 1, 2, and 3 for waypoints will be used for routes A, B and C. If no sequence is specified, A will be used. If sequence None and sequence 1 are both used, sequence 1 will overwrite sequence None in route A. Bug Fixes: F-15E: Steer point B is selected before entering waypoints. Waypoints will be entered starting at 1A. Steer point 1A is set as current when finished. Popup window locations set to be within the program window.

Thanks, good tip. I will figure out the key sequence for that and have it in the next update.

New version released adding the F-15E Strike Eagle. Command files for send via TheWay are updated to version 2.0 which is not compatible with version 1.0. The cmd/*.json files from the previous version can be used if you are still using TheWay version 1.0. v1.3.1 Feature Changes: F15E Strike Eagle support added. Steer point 1 is not editable in the aircraft and the first waypoint entered will be steer point 2. F15 files for DCS-BIOS are not yet in a release version. The files to use can be manually downloaded from: https://github.com/DCSFlightpanels/dcs-bios Aircraft command files updated for TheWay version 2.0. F18 weapon mission entry does not work with this version. If you have problems with sending via TheWay.lua, use DCS-BIOS instead. DCS-BIOS version update to 0.7.48. Python version update to 3.11. Bug Fixes: A10C: Spaces were dropped from waypoint names. Added "Failed to connect' status for F10/F11 capture if the socket times out.

I looked at it briefly, I don't think it is going to work. The mission editor coordinate display doesn't always fill the leading 0's for minutes and seconds, although sometimes it does. There is also nothing usable on the map to indicate if the altitude is displayed in feet or meters.

Here is the sections from drivers.py for each aircraft with the waypoint types and maximum number: class HornetDriver(Driver): self.limits = dict(WP=None, MSN=6) class HarrierDriver(Driver): self.limits = dict(WP=None) class MirageDriver(Driver): self.limits = dict(WP=9) class TomcatDriver(Driver): self.limits = dict(WP=3, FP=1, IP=1, ST=1, HA=1, DP=1, HB=1) class WarthogDriver(Driver): self.limits = dict(WP=99) class ViperDriver(Driver): self.limits = dict(WP=127) class ApachePilotDriver(Driver): self.limits = dict(WP=None, HZ=None, CM=None, TG=None) class ApacheGunnerDriver(Driver): self.limits = dict(WP=None, HZ=None, CM=None, TG=None) class BlackSharkDriver(Driver): self.limits = dict(WP=6, TG=9)

Aircraft command JSON files were just uploaded. https://github.com/atcz/DCSWaypointEditor/tree/master/cmd The existing files can just be replaced in your current installation. F18 mission entry does not work yet with the new version.

It doesn't look like any code change is needed, just updates to the JSON cmd files or each aircraft. A10, Apache, Blackshark all seem fine with the update. F18 waypoint entry seems fine, mission entry is broken again. After I get a chance for some more testing I'll add the updated JSON files, they are just a drop-in replacement.

It does not, and not limited to VR. The capture F10/F11 pulls the coordinates directly from DCS without relying on the screen display in any way.

No, I mean the File menu "Run Target Jar" that launches a java app to display the screen center dot. This was originally part of "The Way" and doesn't have a native counterpart in Python, hence the separate application.

Great walkthrough, I like the idea of using scratchpad to display the center point. For 2D the "Display Target" option puts a purple circle on the center of the display. Can you toggle that on/off in VR, or does it need a VR option to launch with display turned on automatically?

Check the log.txt file to see if it records a status when you hit ctrl+t. If it's not playing a success/fail sound or recording anything, you may have a conflict with ctrl-t bound to something else. I've also seen ctrl-t also can stop working if DCS is restarted, and restarting waypoint editor will fix that. Also check that your setting for ctrl+t is entered correctly. There is no code checking for misspelling, extra characters, etc.

Final version 1.3.0 is now available with send via TheWay.lua and a few bug fixes. The latest DCS-BIOS version is now 0.7.47. v1.3.0 Feature Changes: Added an option to send aircraft commands through TheWay.lua instead of DCS-BIOS, selectable in the "Settings" window. Waypoint entry for most aircraft is much faster, but also dependent on your DCS frame rate. Aircraft commands for A-10C, AH-64D, F/A-18C, F-16C and Ka-50 have been tested. Commands for other aircraft were created based on various sources and need testing. Known Bugs: F/A-18C Mission Point Entry: OS button press does not always register and a latitude or longitude entry is missed. Sequence and timings have been adjusted to correct this, but not 100% reliable. Entry using DCS-BIOS is unaffected. DCS-BIOS version update to 0.7.47. Bug Fixes: A-10C: Set the AAP Page dial to OTHER as the first action. F-14A/B: Added CLEAR keypress before starting coordinate entries. F-14A/B: Changed keypress 3 (SPD) to 4 (ALT) before entering the waypoint altitude. F-16C: Enter elevation when it is zero. BUG: Settings window can be hidden behind other windows

Anything using OCR will not work in VR since it will not find the fields to capture. Using Capture F10/F11 View should work assuming you can place an F10 object in whatever it considers to be the center of the screen. F11 view should also work if you are viewing from the location of a target.

I've done some more work on the 1.3.0 beta release, and the second iteration is available. This has LUA commands for all aircraft, not all of which have been tested. If anyone can confirm the untested types as working or not, that would be appreciated. v1.3.0-b2 Pre-release Feature Changes: Added an option to send aircraft commands through TheWay.lua instead of DCS-BIOS, selectable in the "Settings" window. Waypoint entry for most aircraft is much faster, but also dependent on your DCS frame rate. Aircraft commands for A-10C, AH-64D, F/A-18C and Ka-50 have been tested. Commands for other aircraft were created based on various sources and need testing. Known Bugs: F/A-18C Mission Point Entry: OS button press does not always register and a latitude or longitude entry is missed. Sequence and timings have been adjusted to correct this, but not 100% successfully. Entry using DCS-BIOS is unaffected. DCS-BIOS version update to 0.7.46. Bug Fixes: A-10C: Set the AAP Page dial to OTHER as the first action. F-14A/B: Added CLEAR keypress before starting coordinate entries. F-14A/B: Changed keypress 3 (SPD) to 4 (ALT) before entering the waypoint altitude. BUG: Settings window can be hidden behind other windows

A new update is available now. This version reworks the OCR routines to eliminate most errors, and allows capturing coordinates from a selected map object. v1.2.5 Feature Changes: OCR capture will now capture the coordinates of a selected object/vehicle from the details box in the lower left F10 map. If no object is selected the cursor coordinates are captured from the top left as previously. Bug Fixes: Updated the OCR routines to resize the captured text x3 and convert to grayscale before sending the file to Tesseract. In testing, this has greatly reduced the number of character errors and "No matching pattern" errors.

A minor update was just made available: v1.2.4 Feature Changes: When capturing F18 MSN points, the next station is selected automatically in order 8-2-7-3 Bug Fixes: Currently selected Aircraft Type is retained when starting a new profile

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.