Lurcher

The issue just started happening again, on the latest OB. Attached is the server log and my crashing client log. Other players are crashing as well when they try to connect, like previously. Server uptime was slightly more than 1 day in this case. PS: Adding to the previous post, we have also already done a full (slow) repair on the server in the same maintenance window. dcs_client.log dcs_server.log

Update: We ran the suggested diagnostics script (I could not tell immediately if it fixed anything of importance). Also checked for any Realtek related software on the server, and could not find any. There's no mention in the DCS log of this either that I could tell. I'll update this thread if/when we have a next occurrence of these client-side crashes.

@Special K Thanks! We'll give this a try next time we do a full restart on all servers.

@Special K To clarify this affects all clients trying to connect. The server remains empty once it starts crashing clients. In my dcs(2).log example this should be enough resources, also running on an SSD without any antivirus except Windows Defender: 2021-09-19 15:21:44.190 INFO DCS: CPU cores: 8, threads: 16, System RAM: 32698 MB, Pagefile: 18432 MB No problem, thank you for helping us look into this so far!

dcs(2).log was my client log, and to be clear I was running the latest open beta at the time (mid September). I'm not sure why you think it's a closed beta version.

@Flappie This is the DCS server log for the crashes earlier today. At the end (2021-10-11 13:11:59.297 in the log) we shut down the server, which incidentally led to a server crash itself during shutdown. @Sandwich's connection attempt and client crash happens between 2021-10-11 13:07:57.926 and 2021-10-11 13:10:42.915 (corresponds to client log dcs(1).log above). We cannot ourselves see in the logs whether the server is in this client-crashing state. From the point of view of our server scripts, clients connect and just disconnect after a minute or two. dcs-server-log.zip

To add some more bits of info: This currently is only happening on our Marianas server. We can share the miz and scripts privately if needed. The server runs fine for 1-10 hours before the issue appears and players start being dropped from the server, and new players crash when trying to connect (with the above logs). The issue occurs roughly once or twice a week. The first occurrence was on version 2.7.5.10869, shortly after 2021-08-11. Appreciate any help, Lurcher / 4YA

No matter if the issue is specific to AMD cards (it seems to be), and whether or not it is actually caused by an AMD bug or not (we cannot tell), we should be able to agree at least that it is up to ED to deliver a game that runs adequately on the hardware they support. It was the 2.7 update that introduced the issue, not a driver update. The cause can be found somewhere in the (huge) 2.7 diff. Waiting for the right AMD driver update to come along does not work - keep in mind this issue already exists for 6 months now, and we have no way to tell whether it is an AMD driver bug and then whether AMD is aware and will prioritize a fix. ED will need to either fix their bug, or work around whatever AMD hardware/driver bug there may be, just like other software and game developers work around hardware and driver quirks. I may just be repeating others at this point, but the long wait for a solution is frustrating: I've not been able to properly make use of CA since 2.7 came out, and I keep restarting the game because the refuel/rearm menu messes up. Still I'm hopeful that this issue is solved earlier than my next hardware upgrade (A 5700XT *should* run most games just fine for a few more years).

We don't have much of a presence on the forums here, though we do have an active Discord (feel free to stop by to also discuss this ). I was not involved with making the Marianas mission, but I believe we lowered the player cap because it's a smaller mission with fewer targets, and fewer possible slots to spawn in, especially compared to Caucasus where we have a limit of 40.

First of all, using a webhook like this is a great idea and makes discord integration very easy, so thank you for sharing. However to anyone reading this, please, do not use any of these example Lua snippets directly, they are extremely unsafe. Filter your inputs.

I'm not the person you replied to, but I tried this as well. With the CA module disabled in the module manager I still get the same UI glitch. Anecdotally, it did take longer for the issue to show up this time.

Same issue. 5700XT card, latest stable channel drivers from AMD. It triggers almost every DCS session and makes the mission editor unusable. To make matters worse it's now merged to stable as well. Has anyone at ED managed to reproduce the issue? Is it being worked on, or is more information needed? I'll also gladly settle for any workaround that doesn't involve buying a NVIDIA card. edit: I would suggest changing the title. It's a general UI bug and triggers at least in any 2D map view as far as I can tell - the mission editor is also affected.