Posts by Devourer

If your game version is really 0.14.0.28375, you have to downgrade it to a lower version supported by AKI 3.7.6, that would be: "0.13.5.3.26535 (released 10th October 2023)" <-- taken from SPT github.
You can downgrade EFT with the downgrader available as one of highlighted mods next to SPT-AKI itself

Otherwise If you have the correct version of Tarkov, i would try reinstalling, and running it vanilla first.

//Devo

Not entirely sure if this file is necessary, but you have this in one of the logs:
``File not exist. File: "EscapeFromTarkov_BE.exe". ElapsedMilliseconds:86``

Try to copy that file over from "normal tarkov".

//Devo

You could try launching the server as administrator, it seems that there are some permission issues, and server is unable to write to it's folder.

//Devo

Quote from Nyntex

Could it maybe be that the server has ram limitations? When I fill my inventory the game uses like over 18 gigs of Ram and maybe the server can't handle that

My System has 32 Gigs for clarification

The server will not that resource hungry to fill up 32 gigs together with tarkov client. Problem is with some raider waves, and no one knows why at the moment.

Have a good day,
//Devo

Hi Nyntex,

At this point I think most of the people who are invested into this issue suspect that this may be a SPT-AKI server problem, not any mods. Right now we have to wait for someone to find the root of the problem.

Have a nice day,
//Devo

Quote from Surviv0r1969

have that but launcher and server different 322 and 323?

The 3.2.2 on the second picture just shows on which SPT-AKI version the profile was created.

Have a nice day,
//Devo

Quote from Surviv0r1969

ah that makes sense now i think, so the bug was on the server of theirs not here? sp how come the same thing is or did happen?

thanks for explanation

Purely coincidental i would say. I am like 99% sure that the underlaying issue is very different in their case than in ours, but i may be wrong. Until the root cause of this issue is found on SPT side, we won't know.

Have a nice day,
//Devo

Quote from Surviv0r1969

so if they have a bug when you use the files it dont mean you got the bug too?? ah excellent. strange but awesome non the less. so is there anything to be done to fix the no ai or not exiting the raid black screen?

thanks for info

Let me explain, SPT-AKI is using its own back-end (server), which handles requests from the client.
BSG have their own infrastructure (servers) for the same purpose, and this servers are not in any way associated with spt-aki.

The problem BSG fixed, was on their server, which in no way affects SPT-AKI server, thus this does not affect us.

Have a nice day,
//Devo

Quote from CWX

So from what I can tell is this thread is a mod issue? Recommendation is message the modders on their thread and let them know. I’ll leave this thread open till tomorrow

It seems like the issue is with bot-raiders in SpawnRework mod, so yeah, you can close this, Lua is well aware of the issue.

//Devo

Quote from Kpoof

Hey! Thanks for the quick response. I read through the link you posted but I'm curious as to how black screen extraction is the same as Node JS server breaking, forcing a crash to desktop for the client.

Was there anything in the logs that indicated that it had to do with bot configuration requests? This happened the second I double-clicked a weapon component. I've seen quite a few short freezes before when doing this, but never that it actually crashes to desktop because of it.

KcY-SeeItemValue(SIV for short) requests data from the server to show you how much an item costs. When server is in a crashed/frozen state, it does not respond to such requests, and SIV waits for ~20 seconds for a response freezing the whole game.
If you're lucky enough you get crashed. I had the same issue, and thought that it was related to SIV, but after ~4hrs of testing i got to a conclusion that it was SpawnRework
Either way, if that happens your raid is dead, unless you use my "wonky donky workaround", but it's really better to remove the SpawnRework.

In the logs, the last visible entry is "bot confiuration request", when i restarted the server mid-raid, the request was resent, and the server froze the moment that this request was received.

Good luck,
//Devo

Quote from Lua

Blackscreen is known issue but lack of info and testing, let me know If you found something to solve the problem.

Currently I'm counting on EFT or SPT update fixes this.

Hey Lua,

If you could prepare a version of your mod, which would throw out a dump of both bot request from the client and bot request response to the server console (before sending it to the client), i could try troubleshooting this issue further. I got kind of invested into this issue here: extraction black screen

I also noticed that this problem did not occur for me on Factory or Reserve, but occured every time on Customs.

I found a workaround, but it only lets you extract, no new bot waves will spawn.
Turning off the server and opening it again just before extracting will let you save your progress, but as soon as the bot request from the client is retried the server hangs.

//Devo

Hi Kpoof,

Short version:
Spawn rework breaks the server upon some bot configuration request, i recommend removing it for the time being.

Long version:
Please read through this thread:
extraction black screen

Have a nice day
//Devo

Hi Guys,

I did some more testing, and i wasn't able to reproduce this issue without SpawnRework mod. (I did around 10 long Customs runs)
To anyone having this issue, i recommend removing the mod for the time being, or if you're stubborn and can't live without the mod, just use my "wonky donky workaround" 3 posts above.

Somewhere in the comments of SpawnRework creator said that this can be connected to BSG's post "We fixed an issue with bots not spawning in offline raid", but i doubt it to be the case.

Best Regards,
//Devo

Hey there again.

First of all, again, i am sorry for triple-posting, but hopefully my engagement in the topic will excuse my actions (also the fact that i want to keep the posts readable, and not a gigantic mess).

After extensive testing, i believe that this issue is caused by spawn rework, hear me out.

First of all, server hanged every time on customs after some in-game time and some bot-requests, so i kept it to customs.
When i removed the SpawnRework mod, it just stopped hanging the server, i tried only once, but i got this problem every time, plus i had a short-stutter every time when inspecting items with the SpawnRework, and didn't get those short-stutters without it.

Theory plus some trace reading leads me to below conclusion:

When the server hangs, it hangs after a bot request from the client, however client never receives any response from the server because the server decided to die.

What's interesting here, is that the whole console is hang, i ran it on WSL and it hang whole console instance, namely ctrl+c did not kill the process, and ctrl+z did not suspend it, the console just stopped responding, but windows did not detect that, even after a prolonged period of time.
When the server is restarted, there is a time set for a retry on said bot-request, and this is the time, after which the server hangs again. So, the server hangs again when the previous unanswered request is re-sent.

However, i haven't had this problem on Factory, so i believe that some config for bots on customs for LUA-SpawnRework is causing this error.
This could possibly happen on other maps too, but i focused where the problem was always visible for me.

At last, being a proffessional troubleshooter found some use in real life, imagine how proud of myself I am right now.

However, knowing the nature of things, i will keep trying to trigger the problem without the mod installed, but i need a break, so... Later

Have a nice day,
//Devo

Hey again.

I decided to make it as a separate post, since i have just discovered what i would call a "Wonky Donky workaround"...
(I am sorry if i should have merged the posts, but i wanted to keep it nice and clean, and not a one gigantic post)

First of all, i am quite sure, that this is an SPT-AKI issue, why? See below:

First you need some kind of a tell, to check if the server died. Either load https://127.0.0.1:6969 or have KCY-seeItemValue (SIV for short). (Airdrops are not 100% accurate tell it turns out, as i had an airdrop load properly and it had items inside)
When you inspect an item, you havent inspected yet, SIV will request the price from the server. If your game hangs, it means that the server is dead.
When you're sure that the server died minimize the game, kill/close the server, run the server again and it will work for some time again, but will die eventually (mostly within 10-15 seconds).
I even managed to extract with that method, but i had to kill and rerun the server.exe just before going into extraction.

However, while it helps to extract, it is pointless since no new bots will spawn as every bot config request will fail if the server is hanged, and it hangs within a very short time after restarting it...

Sooo... Wonky Donky Workaround, but i am very proud of myself.

Conclusions:
1: Client works fine, since after restarting the server the communication resumes.

2: Server hangs withing a very short time after restarting. Maybe the client sends some gibberish data to the server forcing it to hang itself?

3: Running the server via powershell didn't help. Will try with WSL linux shell later.

Patience runs out, but as my swan song I may try wiresharking the hell out of this issue.

Anyone knows if it's possible to enable higher logging level for the server.exe?

@edit@
Not sure if relevant but this error started to appear before the server hangs after restart:

unable to find bot assaultGroup isPmc: true in cache

TypeError: Cannot read property 'logger' of undefined

TypeError: Cannot read property 'logger' of undefined

at generateBot (D:\SPT AKI\obj\bundle.js:3279:18)

at BotController.generate (D:\SPT AKI\obj\bundle.js:3273:20)

at BotCallbacks.generateBots (D:\SPT AKI\obj\bundle.js:52:61)

at $de60112e0288ef4d$export$1dd35d19c79daa7c.action (D:\SPT AKI\obj\bundle.js:16329:42)

at BotStaticRouter.handleStatic (D:\SPT AKI\obj\bundle.js:15226:61)

at Proxy.handleRoute (D:\SPT AKI\obj\bundle.js:15542:41)

at Proxy.getResponse (D:\SPT AKI\obj\bundle.js:15532:30)

at HttpServer.sendResponse (D:\SPT AKI\obj\bundle.js:17221:38)

at Inflate.cb (D:\SPT AKI\obj\bundle.js:17247:22)

at Inflate.zlibBufferOnEnd (zlib.js:153:10)

See you soon,
//Devo

Hey guys,

@Edit2@ If you want to skip my journey through troubleshooting this issue, please go directly to my 3rd post where I believe is a conclusion @/Edit2@

Same here, since 3.2.3 i get black-menu every now and then when i extract, however i've digged deeper into the issue.
Some time ago i discovered that my Windows10, for whatever reason would have problems loading websites, meaning nothing would happen and i would timeout. Problem fixed after ~30 seconds but reappeared every now and then. Disabling `IP helper` (which is basically IPv6 helper) in services.msc fixed the issue, but i have to do it every PC restart.

I did encounter the black-extraction-screen on older versions, but only when the IP-helper was enabled.

However this fix does not work anymore for SPT-3.2.3 as i still get that extraction black screen of disappointment and super sadness (let's call it E-BSODASS for short). I discovered that it is the server that hangs itself and refuses to work and respond to any HTTP requests (Checked that by connecting with a browser to the spt server (https://127.0.0.1:6969/), no response at all, normally it shows some kind of an HTTP response (checked when server was fine).

First indication of this issue for me, is the air drop (so i set the air drop to 100% chance for troubleshooting).
When the plane drops it's cargo I either get a freeze for about 10-20 seconds, or not. When i get the freeze, it means that this issue happened, and i will not be able to extract (black menu), but when i don't get the freeze, i'm good to go.

It is hard to say for now, but i am puzzled between this error being either on the SPT server side as it hangs, or if the issue is somewhere on my pc and SPT just freezes as such events are not predicted in the code.

General error in the logs i get, both when i extract, and when the plane drops the cargo:
[Exception] : GException0: Backend error: Request timeout
<Gigantic meaningless stacktrace as it is a request timeout>

In the logs i would also see this:
2022-09-20 12:10:57.081 +02:00|0.12.12.31.19428|Error|backend|<--- Error! URL: http://127.0.0.1:6969/client/game/keepalive?retry=5, isNetworkError:True, isHttpError:False, responseCode:0

Another tell of this issue was when i had KCY-seeItemValue, it would freeze for 20 seconds on item inspection and my raid was f... slept with. Really frustrating...

I am still going to try and troubleshoot this issue, but my patience runs out, so I thought writing it down when i still had the motivation was a good idea.

Stay tuned,I will post again when i find out more.

@edit@
Server mod list:

CWX-WeatherPatcher 2.4.4

Faupi-MunitionsExpert 1.6.4

Kobrakon-UltimateClearNVGs

Lua-FleaMarketPriceUpdater

Lua-PlayerBossScav

Lua-SpawnRework

ServerValueModifier

Valens-Progression_1.2.3

Client modlist:

CWX-WeatherPatcher.dll

Faupi-MunitionsExpert.dll

Kobrakon-TakeABreak.dll

Kobrakon-UltimateClearNVGs.dll

Have a nice day,
//Devourer