Black screen for a long time after loading game before connecting to server

Often when I start the game (as in load and start the actual game from Windows, not start a match) I get a black screen that can last from a few seconds up to like a minute. Then I see the proper loading screen and it says “connecting to server” and all that. It just does something really weird in the background for a long long time sometimes. I have no idea what it is. Is it the driver having problem initializing? I updated it. No change. I even tried deleting all the direct3d cache files as instructed on the support page (https://support.gaijin.net/hc/en-us/articles/30268449678994-How-to-clear-NVIDIA-and-DirectX-cache).
I also recently see a long delay when i CLOSE the game, like the whole interface freezes for several seconds.
Personally I think it’s either something with the anti-cheat that chokes and does something weird on startup and shutdown, or some graphics initialization. It’s only with War Thunder of course.
I’m on Windows 10, Ryzen 9 5900X, 32GB RAM and RTX3080 on a good 1000Mbit line and haven’t had these problems before and I’ve been running this install for a long time, like 3-4 years. It just started appearing maybe a month ago or something, maybe more, but relatively recently.
Is this familiar?
Just don’t tell me to “reinstall drivers” or “reinstall windows”… There’s a specific problem and there must be a specific fix, not the shotgun “reinstall everything”.

1 Like

That’s likely not what they meant.

The usual advice is to clear out the cache folder in the game folder.

But I do notice that that black screen you are making mention of is there, for a while now compared to usual. It’s not quite a full minute, but it is up there.

And are you on Steam? Because I know Steam suuucccckkkssssss for literally not having any messages of the loading progress overall anyway.

1 Like

I found the link. Edited the post above.
The reason I did that is because I was wondering if shaders were being recompiled or something else just got stuck in a refresh each time, but that’s just guessing since I have no idea what’s happening. I see the anticheat window pop up as a separate application briefly sometimes and I don’t know if that’s causing it, or some graphic init re-initializing every time, or something else…
Yes I’m on Steam… but god damn… I mean even when shutting the game down it freezes for a few seconds. Not sure it used to before, at least not that long.
And yeah the loading black screen is not always 1 minute, sometimes 10 seconds, sometimes 30. I think it was close to 1 minute today (didn’t time it), but it shouldn’t take that long. It shouldn’t even take 10 seconds.
Something’s bugged since a while back.

1 Like

Yea, the Steam version of the client sucks man. It shows no messages overall.

Try clear that cache folder in the game folder though (Which will be in your Steam Library of the game folder) with the client closed.

If you get graphical issues, the folder to clear in the game folder is the compiledShaders folder.

But as I mentioned, I too feel that blank screen portion is something, and I just use the normal client, not steam.

Same too with the ‘hang’ that happens when you go to close the game, it does hold for like 6-10 seconds, and that too is the same on the normal client.

I’d wonder whether Linuxs native client has this happen.

1 Like

You want to head to this thread just saying.

Seems like it’s possibly related to the DirectX 12 setting.

1 Like

The reports in the related loading-delay thread make this look broader than a Steam-only or BattlEye-only problem. Users have reproduced it on both NVIDIA and AMD hardware, and at least one user reported a clean A/B result: the delay occurred with DX12 but not with DX11. Updating the GPU driver also did not resolve it for another affected user.

A useful test would therefore be:

  1. Time startup and shutdown on DX12.
  2. Fully restart the client, select DX11, and repeat the same test.
  3. Keep DX11 as a temporary workaround if the delay disappears.
  4. Add the exact client build, driver version, DxDiag and the .clog from each test to the existing bug report.

I would avoid attributing it to BattlEye without log evidence. Adding comparable DX11/DX12 data to the existing report is more useful than creating several duplicate reports or repeating broad reinstall suggestions.

1 Like

̶M̶o̶s̶t̶ ̶l̶i̶k̶e̶l̶y̶ ̶B̶a̶t̶t̶l̶e̶E̶y̶e̶.̶ I do not use Steam for War Thunder, and I have a very fast computer and GPU. Loading into War Thunder has always been mere seconds for me. But the last weeks/month it has taken a LONG time to load in. Every single time. Doesn’t matter if I am just reloading the game to see if there is an update/patch etc. I highly doubt it is Nvidia. I am actually still using a driver that is a few months old because the most recent drivers caused FPS drops.

̶S̶o̶,̶ ̶i̶m̶o̶,̶ ̶o̶d̶d̶s̶ ̶a̶r̶e̶ ̶e̶x̶t̶r̶e̶m̶e̶l̶y̶ ̶h̶i̶g̶h̶ ̶t̶h̶a̶t̶ ̶i̶t̶ ̶i̶s̶ ̶B̶a̶t̶t̶l̶e̶E̶y̶e̶ ̶d̶o̶i̶n̶g̶ ̶s̶o̶m̶e̶t̶h̶i̶n̶g̶ ̶i̶n̶ ̶t̶h̶e̶ ̶b̶a̶c̶k̶g̶r̶o̶u̶n̶d̶.̶ ̶A̶l̶s̶o̶,̶ ̶e̶v̶e̶n̶ ̶c̶l̶o̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶g̶a̶m̶e̶ ̶h̶a̶s̶ ̶b̶e̶e̶n̶ ̶s̶l̶o̶w̶e̶r̶.̶ ̶E̶x̶i̶t̶i̶n̶g̶ ̶n̶o̶r̶m̶a̶l̶l̶y̶ ̶a̶n̶d̶ ̶h̶a̶r̶d̶ ̶c̶l̶o̶s̶i̶n̶g̶ ̶l̶i̶k̶e̶ ̶A̶L̶T̶+̶F̶4̶.̶

I have not tested DX11. I can try, one minute. (I have always been using DX12 since it was available for War Thunder.)

Ok, that was a bit faster, but still not as fast as it was before this slowdown period. Let me test closing WT too.

OK SHUTTING DOWN WAR THUNDER WAS NEARLY INSTANT using DX11.

I am getting a timer and will post results for starting up between DX11 and DX12.

DX11 =
~25 seconds until loading screen shows
45 seconds for main menu AND my lineup becoming usable (until my lineup’s units are not greyed out)

DX12 =
40 seconds until loading screen shows
1 min 3 seconds for main menu AND my lineup becoming usable (until my lineup’s units are not greyed out)

Ok, yeah there are HUGE differences in startup/load times between DX11 and DX12. ESPECIALLY shutdown time. DX11 is effectively instant, but DX12 is very very slow to shut down. I’ve had it take nearly a minute to shutdown with DX12.

Yup, I concur. Again, I do NOT use Steam for War Thunder. There is definitely something going on with DX12. I still think it might involve BattleEye, but it is for sure linked to something with DX12.

I also added my loading time results to the bug report on the thread you linked to 👍

EDIT:

I have also tried deleting my cache and compiledShaders folders in /AppData/Local/WarThunder folder, and doing a file check through the War Thunder launcher. These steps have had no effect on the startup/loading times.

2 Likes

Yeah this is beyond retarded. I had well over a minute of total black screen today before the loadscreen appeared. Once it did the little spinner kept moving along in a jerky motion and it also took its sweet time. This is getting worse and worse.
Did you try, for the first time in a day, with DirectX11 selected, switching to DirectX12 and comparing?
I’m just curious if the improvement when going from DX12->DX11 is in part or wholly because you ran the game once already, like it does something on first start.

I think I will try to switch to DX11 as well and see next time. This is like loading a cassette game on the C64 in the 1980s (Yes I’m that old). While I am very nostalgic about those times, waiting for games to load is not something I miss…

1 Like

Makes no difference. I changed back and forth 4 or 5 times without restarting the computer. Same results, DX12 is absurdly slow, while DX11 is extremely fast, no change between any of the tests. I timed the startup delay with DX12 multiple times, it was identical down the second that day.

Fwiw, I JUST had a 2-3 minute load up with DX12 while I was reading and replying to your reply. (Significantly longer and worse than my previous tests.)

i have got the same trouble as yours, one month ago everything is just fine, but few weeks ago it took long time to show the screen of connecting to the server, black screen is common . as well as took me long time to start downloading the update before starting…

1 Like