#Mysteriously long loading time

1 messages · Page 1 of 1 (latest)

peak rock
#

The game loading time is very long. The game loads eventually, so for single player it is not a problem, but this prevents me from successfully joining, or hosting multiplayer games.


System: Archlinux
CPU: AMD Ryzen Threadripper™ 2990WX × 64
GPU: AMD Radeon RX 6900 XT


I included logs for loading a singleplayer game and for one of multiplayer game attempts.
From what I have observed loading seems to hang somewhere at "LuaUI" and this is more-less where Watchdog starts to complain, but I am not good enough in this to figure out what exactly caused this problem. Help would be appreciated.

midnight swallow
#

did you put it by any chance on HDD and not SSD?

peak rock
#

I'm using nvme, so I don't think it's the drive issue.

wanton whale
#

I see errors with audio in the logs: so maybe checking that you have updated your audio packages?

peak rock
#

Hm... I'm using the newest available drivers for arch.

#

Using pipewire instead of pulseaudio. May this be a problem?

lime relic
peak rock
#

I'm afraid it's every time.
Loading slows to a crawl on LuaUI and loads after a longer while.

#

When game loads everything seems to work just fine.

lime relic
#

hmm then i have a separate issue then

midnight swallow
#

Flatpak or AppImage?

#

Try the other if possible

#

Also, what DE?

peak rock
#

Appimage.
I will try Flatpak.

midnight swallow
#

Wayland or x11?

peak rock
#

GNOME (Wayland)

midnight swallow
#

Ok, you can also try setting SDL_VIDEODRIVER=wayland env variable to run engine natively on Wayland

#

Maybe it will help

#

(with flatpak you can enable Wayland for game and add env variable using flatseal program)

#

(overall: it should work out of the box, but let's try some things out)

peak rock
#

On Appimage with this env it doesnt want to start the game at all

peak rock
#

Just checked the Flatpak version, but unfortunately the issue persists.
Attached the log. The loading slows down seriously after 02:23.580974

#

Each time the game loads there is a hang and a bunch of warnings after this one "LuaMemPool", but what it's about is beyond me.

hollow hound
#

found 32 cores and 64 logical cpus

#

holy crap

#

Anyhow, 20 seconds elapse here:
[t=00:00:26.960362][f=-000001] [LoadScreen::SetLoadMessage] text="Parsing Map Information" [t=00:00:43.879851][f=-000001] [LoadScreen::SetLoadMessage] text="Loading SMF"

#

Another 10 lost here:
[t=00:01:10.675607][f=-000001] Loading widget from mod: Metalspots <gui_metalspots.lua> ... [t=00:01:21.839790][f=-000001] Loading widget from mod: Mouse FX <gui_mouse_fx.lua> ...

#

Then a full minute is lost here:
[t=00:01:26.026432][f=-000001] Skirmish AI <BARbarIAn-stable>: BARbarIAn 1.6.1 (2) Initialized! [t=00:01:26.027647][f=-000001] [AIWrapper::SendUnitEvents][AI=2 team=3] numUnits=0 [t=00:01:26.027662][f=-000001] [~ScopedOnceTimer][Game::LoadSkirmishAIs] 569ms [t=00:01:26.044873][f=-000001] [LuaMemPool::LogStats][handle=LuaIntro (unsynced)] index=2 {numAllocs[*],allocSums[*]}={0,0} {int,ext,rec}Allocs={0,612036,0} {chunk,block}Bytes={0,0} [t=00:01:56.023603][f=-000001] Warning: [Watchdog] Hang detection triggered for Spring 105.1.1-1354-g72b2d55 BAR105. [t=00:01:56.023665][f=-000001] Warning: (in threads: {main,load,audio,vfsi}={1,0,0,0}) [t=00:01:56.023686][f=-000001] [CrashHandler] Warning: Suspended-thread Stacktrace (main) for Spring 105.1.1-1354-g72b2d55 BAR105: [t=00:01:56.024778][f=-000001] [CrashHandler] Warning: Unable to create suspended stacktrace [t=00:01:56.024808][f=-000001] [CrashHandler] Warning: Suspended-thread Stacktrace (audio) for Spring 105.1.1-1354-g72b2d55 BAR105: [t=00:01:56.025474][f=-000001] [CrashHandler] Warning: Unable to create suspended stacktrace [t=00:02:26.034166][f=-000001] Warning: [Watchdog] Hang detection triggered for Spring 105.1.1-1354-g72b2d55 BAR105. [t=00:02:26.034220][f=-000001] Warning: (in threads: {main,load,audio,vfsi}={1,0,0,0}) [t=00:02:26.034243][f=-000001] [CrashHandler] Warning: Suspended-thread Stacktrace (main) for Spring 105.1.1-1354-g72b2d55 BAR105:

#

Which is quite strange, as it is not a metal map, just a regular (and quite small) using map "Glacier Pass 1.2"

hollow hound
brisk finch
delicate crane
peak rock
#

@delicate crane Just tried that. There are 7 distinct "bar related" processes + one for spring engine. I'm not sure which one is the most important, but I've pinned one at random to 6 cores and it didn't change the loading time.

delicate crane
hollow hound
#

Loading the map takes 2x15 seconds on your machine, when it should take at most 1or2

#

Very unusual

#

There is no antivirus or anti malware software interfering?

peak rock
#

@delicate crane These are all the processes I was able to identify. There may be more. I'm sorry for the images, but I honestly don't know how to copy this information as text.

#

@hollow hound No additional antivirus/antimalware software beyond a simple firewall, but it shouldn't affect a single player game at all.

#

@hollow hound Is it possible that the game doesn't like this particular hardware configuration?

delicate crane
delicate crane
#

P.S I don't know how to detect proper cores to set cores affinity (i don't know how cores sorted on linux) that located on one CCX module and not virtual ones.

peak rock
#

@delicate crane I've used the cores with adjacent numbers, but I don't know, if these are physically adjacent.

wanton whale
# delicate crane I seached latency of 2990WX for cache... Damn, that's high. https://3dnews.ru/as...

That's inter-core latency, which is different from cache latency. Still good to know, but I wouldn't have expected it to have a significant impact on its own. As for thread enumeration. CPUS follow a simple, consecutive pattern. So virtual CPUs 0-31 are spread over the 32 cores (in order.) If the processor has SMT, then the next 32 virtual CPUs are the alt hardware threads spread over the 32 cores (in order.) This is all rather a moot point however, because game loading is only MT during path cache generation and loading models (IIRC.) The rest of it is single threaded.

delicate crane
silver hull
#

me and one of my buddies have the exact same issue.
so some do but others don't..

#

that happens the first time a game load. all the next games don't have this issue

wanton whale
silver hull
#

if i reboot the pc it happens again

wanton whale
#

That is because the AV is scanning all the files.

#

It does it first time you access those files after reboot.

silver hull
#

well it makes us having to wait for several minutes the first time we launch a game, solo or not

#

and in multi it actually disconnect us after finishing loading. and so we have to reconnect to it

#

tho this isn't the case if spectating

wanton whale
#

There's 3-minute (I think it's 3-minutes) timeout for players joining matches. It is annoying. @dapper totem do you recall how long the join match timeout is now? Seems it may not be long enough given this initial loading issue.

lime relic
#

beherith bumped it up i think

wanton whale
lime relic
#

to 4 min maybe

silver hull
#

i do not have this issue with zero-k tho

hollow hound
#

I bumped from 2 mins to 4 mins

#

Zk has way less files strewn about

brisk finch
#

Wait so it is certain this is due to AV?

#

Let me try adding an exception

brisk finch
#

lmao it worked 😄

verbal mantle
#

I'd have time to practice doing a back-flip if I could get my load times reduced from the 45s-2min I take to load every single game. Anthem, The Division 2 and GTA V load faster.

Also nvme 2.0, ryzen 2700. By the time I get in games people have written several chapters in a novel, and I almost always get last pick and forced start.

The loadscreen just hangs about 70% through the load.

brisk finch
#

Share your infolog, maybe we can check what hangs it

#

Also are you using SSD or HDD drive

#

?

verbal mantle
#

Nvme 2.0

#

I'll shoot them tomorrow. I've been in bed peeking at everything on here, trying to fall asleep.

#

Though I've given you plenty!!!! The load times aren't any different, would there not be the info needed in my other logs I've shared?

peak rock
#

Can you share logs related to this issue in this thread?

brisk finch
#

must have missed it, this discord is a maze

midnight swallow
#

Because we don't.

#

Or at least i don't have such powers, I can't even access all the logs.

verbal mantle
#

Not magical, just didn't know the ones I sent weren't easily accessible. Apologies ptaq, I'll send some qhen I wake up. Thanks for helping though!

hollow hound
midnight swallow
hollow hound
#

@dim summit , could you please give access to log s to marek

dim summit
#

Sure thing. Infologs right?

midnight swallow
#

Yeah, launcher logs I only know go to some S3 bucket i don't know who owns

dim summit
#

Sure thing. I'm doing some housework right now so might be an hour or two but I'll do it.

hollow hound
#

But you can fuzz the urls

#

And also move one folder up

#

Ideally, launcher could put logs on teiserver the same way?

midnight swallow
#

Looking at commit history in launcher, @sturdy herald added it

midnight swallow
dim summit
#

Should be sorted now. I'm happy to add launcherlogs to teiserver if it helps.

verbal mantle
#

@brisk finch should i start a game, load it up, and then send the latest info, or will any of them do?

brisk finch
#

yeah load it up and thats it

verbal mantle
#

The log shows it was made 1:36 pm and the starts, I've done after this. @brisk finch

#

Not sure which infolog you'd need specifically.

#

Nevermind it made one at 145, 2 minutes before I said this but didn't show until i refreshed

silver hull
brisk finch
#

I added exceptions to windows defender, not only AV

#

Have you tried that?

#

Marked the whole install folder

silver hull
#

i only have windows defender

#

i did add the whole BAR folder in the exclusion tab

midnight swallow
#

do you have your install on ssd?

silver hull
#

HDD

wanton whale
#

Ooh. That's going to be sloooooooow. That could explain why the later attempts are fast: because the OS has cached the files in memory.

midnight swallow
#

Yeah, no mystery at all then @silver hull : #1065610080113922048 message

silver hull
#

it's funny, sometimes, when i join a big already running game as a spectator it instantly load despite being the first game i joined atfer launching the game.
one would expect that the game will load for 3-5min but no. ¯_(ツ)_/¯

midnight swallow
#

if you didn't do reboot, it can be expected

silver hull
#

i launched the PC just before.

silver hull
#

but maybe the pc kept a cache of my previous BAR games earlier the same day?
since all i did was play BAR, shut down the pc, eat and do stuff, come back, launch the pc and play BAR ^^.

arctic cloak
#

Did this ever get resolved? I have experienced the same as OP described: running Endeavour OS (arch based), extremely long loading times EVERY time. I think it started a week or 2 ago. Both appimage and flatpak have this issue. If the game loads, it works kind of fine, although I have noticed the game is less responsive than it used to be.
My setup is a bit different: AMD Ryzen 7 2700X cpu and nvidia GeForce RTX 2060 graphics.

midnight swallow
#

There weren't any changes to loading code for many months.

arctic cloak
#

Can I send some logs for you to look at? Or what else can I do?

midnight swallow
#

If this changed recently for you, it's something in your system that changed

#

There is nothing helpful in log to determine why something got loaded slowly

lime relic
#

could something like this be related to a drive dying by chance?