davidp57

Hello, We regularily have our dedicated servers randomly quit the mission with this error message in a dialog box (meaning that, additionnaly, we need to connect to the remote server to click on the button): The last error in the log (with no other error or context linked to it) is: ERROR ASYNCNET (12668): The session has expired (401). Exiting... This is not related to the latest version, we've been having this behavior since a few weeks/months. We started a log of the date and time it happens. Can you please help us? We've got 4 servers up, and a specific one that can be used to test. Cheers, Zip.

Nice! I'll try that asap.

Hi, do you have more information on this file please?

Ditto, in VR too, please remove this effect or at least make it optional!

And that would work very well in multiplayer, too

Thank you for the F-4E export script and profile. Here's a nice icon for this plane on your Streamdecks:

Merci!

Nope, and I stopped looking a few years ago. Sorry!

That's not true anymore. Since a few months/years it works now

Done; I merged the conflicting file and did a new commit. https://github.com/asherao/DCS-ExportScripts/pull/13/

And I made another one to optimize the AH64D export (changed my life, this one); see this post by my friend Ian.

@Bailey I submitted a PR for the F15E UFC changes.

Oh my, sorry Bailey I forgot that we were hijacking your thread ^^ Your repository should be the master, you're the one who reignited this torch. I don't know why I chose to fork S-D-A as your repo is more active. I'll change this.

The "legacy" Git repositories for DCSExportScripts are now almost dead - they rarely update - and the one I chose to fork (S-D-A) has not seen any updates for 4 years. Don't you think it's time to start a new repo, or designate one (maybe ExoLight's, which seems on the bleeding edge) as the "master of masters"? Is there a more up-to-date "official" repo?

Thanks. You may also want to change the index (for the UFC screen data) to 9 instead of 8, as in PILOT_UFCa(ExportScript.Tools.getListIndicatorValue(9)) I've done it in my fork.