Lasko

This happens all the time on the Hoggit servers. I exported the server Tacview into Excel from one about a year ago. At 6 seconds it recorded 773 HasEnteredTheArea events, then 11 seconds later 711 HasBeenDestroyed events. I don't think a client track or Tacview will help because by the time you connect it has already happened.

I managed to do it just now, it took about 10-15 tries but the Abrams sank below ground level then exploded when I tried to control it again. Hope this helps. Persian Gulf At War 1.0.0_morning-20231004-134355.trk

OK, that wasn't exactly true, I do have the track file but it is 88MB. If it will help, I can try to reproduce it at the beginning of an MP track which should be fairly small.

Here is something I've run into from time to time, only on multi-player. I wasn't even sure how to describe this and haven't found anything by searching. Re-create steps: 1. Stop the vehicle on a dirt area. I don't recall it ever happening on pavement. 2. Open the menu with ESC, choose "Select Role" 3. Close the role screen with ESC, you are left in the JTAC slot. 4. Change to F7 view. 4. Vehicle sinks into the ground. If you attempt to control it again, it explodes. If you exit the server and rejoin, it will be back on the surface. I don't know if other players see it buried, but suspect not. Sorry for no track, I've never been able to cause it in a single player setting. 2023-09-30_16-24-36.mp4

Agree, the cockpit display issue can be fixed by changing the shadow setting. I set it to "flat only" a long time ago before changing hardware, but also never had the unreadable issues until recently. The terrain brightness issues started around the same time, so I tied them together.

Here's an example from the A10C landing lesson. "Press the Space bar key to proceed when the radio is tuned to 131.000" Right.... null

The only thing I can offer is that I have encountered this also and don't know how to cause it. My setup is super simple with an RTX 3070 and one monitor displaying DCS and the second monitor displaying Chrome, Discord, etc. I just played about 3 hours on a PGAW night mission and it didn't happen at all. My feeling is it must be related to the brightness problem when switching views, like F11 back to F1, but what triggers it when not switching views I have no idea.

This is a big problem that needs more attention. I was doing the A-10C training missions yesterday and the cockpit radios and other instruments are unreadable without moving the view position fully forward or back, and the HUD is completely unreadable in many of the lessons from the "haze" in the sky. I've also noticed this in some of the Ka-50 training and IA missions, the cockpit instruments are completely opaque so that you can't read the channel number on the R828, for example.

DCS Aircraft Command Entry This is a utility to build command sequences for DCS aircraft, which are then sent as DCS-BIOS commands. DCS-BIOS supports nearly every switch and knob in DCS aircraft. Selecting an aircraft type builds a list of all commands for that aircraft, along with the range of values corresponding to the possible settings. Commands are added to a profile with the selected setting, and the command sequence is sent to the aircraft by clicking a button or via hotkey. Profiles are stored in a database and can be shared between users via a text string or JSON file. Aircraft supported in the initial release: A-10C AH-64D F-15E F-16C F/A-18C Ka-50 Mi-8MT UH-1H F-15E support requires updated DCS-BIOS files not available in a release yet, but they can be downloaded from Github. Support for all DCS-BIOS aircraft will be added. Release information and more complete instructions are available on the Github project page: https://github.com/atcz/DCSAircraftCommandEntry Thanks @Epiic_Penguin for inspiring me to move this project forward into a working prototype.

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