Actium

Does it actually crash or does it quit with a Login session has expired popup message? I've reported the latter more than half a year ago:

The documentation for net.dostring_in() in %DCS_INSTALL_DIR%/API/Sim_ControlAPI.html was updated with 2.9.18.12722. Now, it calls net.dostring_in() obsolete: This is blatantly wrong. Any advanced scripting is dependent on net.dostring_in(). a_do_script() is no substitute whatsoever. Four examples: SRS, Olympus, DCSServerBot, and Lua Consoles require net.dostring_in(). The latter two actually exemplify how both functions are used together. I sincerely hope that this is just a documentation error and not a symptom of a lack of understanding of DCS' scripting engine by the developers. Removing this function would break many applications of Lua scripting that go beyond simple mission scripting. To avoid any misunderstanding, please fix the documentation.

Much appreciated! I does indeed work as of beta 15, at least on Linux with Wine. No reason to assume it wouldn't on Windows. Currently added as a TODO, waiting for the stable release.

Would love for AI to use such advanced tactics. Unfortunately, the AI is currently so inept that it will stall out on full afterburner in BVR engagements.

Not fixed in 2.9.20.15384. @BIGNEWY This core bug has persisted for 3 consecutive versions, so I presume it has flown under the radar.

Not fixed in 2.9.20.15384. @BIGNEWY This core bug has persisted for 3 consecutive versions, so I presume it has flown under the radar.

I appreciate the suggestion. If this does end up in the sim, it should however be in a backwards-compatible manner.

You have two options. For both, you have to open PowerShell. These are just educated guesses, as I don't have DCS installed via Steam, so, unfortunately, I can't check if it works. The first option is to run the two commands I've posted above. They will generate a new registry key that pretends the DCS World OpenBeta Server is installed where you installed DCS World via Steam. That should theoretically get the DCS Updater to search files there before downloading them instead. Alternatively, if it used to work from the old Steam directory on your D: drive, you could create a symlink from the D: drive to the E: drive. That way, if the DCS updater searches in the old location on D: it will be implicitly "forwarded" to the E: drive. Generate the Symlink as follows (note that the parent directories on D: must exist; create them if necessary): mklink /d D:\Steam\steamapps\common\DCSWorld E:\SteamLibrary\steamapps\common\DCSWorld

More informative error messages would certainly help. Same applies to the Error 500 issue. It shouldn't be too difficult to add human-readable error messages to the popup and the dcs.log, so users are not left absolutely clueless as to what is going on. I've even detailed a straightforward way to implement that. Should be feasible in a day's work.

The DCS_updater.exe checks for other install locations within your registry. AFAICT it checks the following registry keys to find other local DCS installations: HKCU\Software\Eagle Dynamics\DCS World OpenBeta\Path HKCU\Software\Eagle Dynamics\DCS World\Path HKCU\Software\Eagle Dynamics\DCS World OpenBeta Server\Path HKCU\Software\Eagle Dynamics\DCS World Server\Path A crude way of getting the updater to find your Steam installation would be to create one of the above registry keys, preferably one that does not yet exist on your system, and to set it to your Steam DCS directory. Haven't tried that, but should theoretically work. Obviously, try at your own risk. Update: Quickest way to do that would be through Windows PowerShell. This will not overwrite any existing registry keys, so should be relatively safe: New-Item -Path "HKCU:\Software\Eagle Dynamics\DCS World OpenBeta Server\" New-Item -Path "HKCU:\Software\Eagle Dynamics\DCS World OpenBeta Server\Path" -Value "E:\SteamLibrary\steamapps\common\DCSWorld"

@BIGNEWY Maybe merge with https://forum.dcs.world/topic/312603-login-session-expired/

I wrote a benchmark script for the dedicated server. Exemplary results.

Having a look at all occurrences of ASYNCNET on your dcs.log, it appears the session expiration occurred out of the blue by decision of the DCS master server: 2025-09-19 12:51:52.652 INFO ASYNCNET (4780): Login success. 2025-09-19 12:51:54.241 INFO ASYNCNET (4780): Got auth data. 2025-09-19 12:51:54.605 INFO ASYNCNET (Main): ProtocolVersion: 408 2025-09-19 12:51:54.605 INFO ASYNCNET (Main): Adding LAN search interface 0: 127.0.0.1 "IPv4 Loopback" 2025-09-19 12:51:54.605 INFO ASYNCNET (Main): Adding LAN search interface 0: 255.255.255.255 "IPv4 Broadcast" 2025-09-19 14:40:01.848 ERROR ASYNCNET (4780): The session has expired (401). Exiting... Unless you started another DCS instance with the same account credentials, there's no good reason for the master server to do that. This is not a an issue with a spotty internet connection. If it were, the log would include messages indicating failed connection attempts. Thus, this lies within the hand of ED to figure out via logs from their master server. As BIGNEWY recommended above, do file a support ticket.

The F-16 Early Access Guide Page 465 defines the small circle on the DLZ as the Radar Activation Range: However, as of DCS 2.9.19.13478 that small circle is now located above the current range caret although missile activation is still 50 seconds away. Documentation and actual implementation are inconsistent. From the looks of the documentation screenshot, the docs may be in need of an update. Track file from which the screenshot was taken: F16_DLZ_Radar_Activation_Range.trk

You made my day! I appreciate your passion and support for the DCS Train Simulator Community! Maybe ED should consider to integrate train conducting into Combined Arms @cfrag Thank you for your very concise and to the point summary of the state of DCS. I do agree wholeheartedly. The tools situation is exacerbated by the lack of official documentation for almost everything, a tendency to break the scripting interface, and an utter lack of developer attention to core bug reports combined with apparent zero pre-release testing [1, 2]. What adds insult to injury is that the Simulation Control API Documentation (see %DCS_INSTALL_DIR%/API/Sim_ControlAPI.html) claims that scripting API centerpiece net.dostring_in() is now allegedly obsoleted by a_do_script(). That conclusion is ill-conceived and makes me wonder whether ED still understands their own code base. I do have my doubts. Bug triage, i.e., presumably forwarding confirmed bugs to an internal bug tracker, and testing is outsourced to community volunteers, who recently got this new and shiny badge to bolster morale. Sadly, only a tiny fraction of General Bugs filed within the last 2+ months have received any official attention. Reporting bugs in the faint hope to get them fixed seems like a waste of time now. A general note on managers: Managers typically work on behalf of the short-term shareholder value. Not the employees, not the long-term sustainability, and certainly not the customers. Boeing is a prime example of the application of this management mantra. Just to put expectations into perspective. Despite its many flaws, I do love and enjoy DCS thanks to the squadron I fly with. They make it worthwhile. However, I am outspoken about DCS' shortcomings in order to get its issues enough attention from ED. To make DCS better for everyone, including the evangelists who repeatedly suggest us critics to walk away. I'm terribly naive, I know ... My wish: These efforts to fall on fruitful ground and be appreciated and considered. By ignoring the content creators, ED is leaving vast resources untapped and fallow.