Posts by S-V_Specialist

Quote from darkDucky

I have a feeling its just a random bug that happens semi-rarely in-game. It has to be... Some days I get a crash every raid, others I never crash at all with 10+ raids

I always wait for the server to say its ready before opening the launcher but that's just normal practice. I have no OC, no ram cleaner, and its just inconsistent really, I also don't think I get crash reports either... or cant find them

Check your event viewer for when your game hangs, it'll show you more information about what's happening. sometimes the game isn't showing all logs, or only what's internal server or mod-wise

Quote from valetudin

Same here. Had not played since using 3.10 and when I played it randomly crashed, no error message just thrown to desktop. So I updated my tarkov install, downloaded the spt installer again and installed a new copy with 3.11. Still throws me to desktop.

The game just reloads as if I was not in a raid.

Do you guys now use a connection verification or something, it seems odd that an install I previously had no problems with and made no changes to now crashes, and still crashes the same way when I update the install.

Faulting application name: EscapeFromTarkov.exe, version: 0.16.1.35392, time stamp: 0x66bbda7f

Faulting module name: UnityPlayer.dll, version: 2022.3.43.18813, time stamp: 0x66bbdd84

Exception code: 0x80000003

And googling the error code it suggests a memory leak.

Display More

I got the same error thrown at me like 3 days ago apparently; verifying game files/ reinstalling doesn't change anything. Memory leak could be something but testing my material returned no particular issue. I strongly suspect this is a software issue; I might be wrong though.

Quote from darkDucky

I was wrong about ram, its 22-24/32 but still, plenty of free ram the whole time.

CPU is an i7-12700F

and a 3080

The peak usage was only at the moment it freezes. The game runs fine with maybe 1% variance then suddenly it freezes and spikes to 100% before the game stops responding

Even on PVE mode (official) hosting my own game I hit 60% CPU, 24GB ram, and 30-40% GPU. (and Im straining running the 100% killa event rn hitting 50 fps lmao) It is funny that FPS goes up with every kill, though, showing Bots take a lot of power to load

Display More

Yes, I noticed the game froze when generating bots as well, might be an error somewhere in the loadouts or the brain types probably

Anything new? did it work?

Quote from ucklefester

i reinstalled everything again and ive dont more than five 30 minute raids and it hasnt crashed. it could have been a mod issue but installed most of them back. try this and lmk if it works!

Alright so big news, I just deactivated the automatic RAM cleaner and enabled the "Use only physical cores" settings and I haven't had a single crash for the moment. Could be memory leak. My mods are working just fine

Quote from darkDucky

Same issue here. Looking at task manager when it happens I spike from about 60% usage on CPU to 100 then 0. Nothing ever goes above 60% usage though when running smoothly (15GB/32GB ram used)

It happened with and without mods too The driver downgrade didn't help either

What is your CPU? I have a Ryzen 5 5600X and for me I don't experience any sudden peak of usage, and the GPU as well. Either way it is not (or vaguely related) to some hardware issue.

What graphics do you use? I have the exact same problem

N.B: any map that you will choose, you will crash.

I believe that the issue is Unity there

Ok so update concerning the game crashes; it is not due to video drivers (I tried different versions and still didn't work; but I got a strange error message in the Event Viewer, here it is:)

Faulting application name: EscapeFromTarkov.exe, version: 0.16.1.35392, time stamp: 0x66bbda7f

Faulting module name: UnityPlayer.dll, version: 2022.3.43.18813, time stamp: 0x66bbdd84

Exception code: 0x80000003

Fault offset: 0x00000000010934c1

Faulting process id: 0xd2c

Faulting application start time: 0x01dbcd0bf361a9b8

Faulting application path: C:\Users\X\Desktop\SPT\EscapeFromTarkov.exe

Faulting module path: C:\Users\X\Desktop\SPT\UnityPlayer.dll

Report Id: 710d3e39-3860-4834-93e3-aeba0e02773e

Faulting package full name: -

Faulting package-relative application ID: -

It seems that Unity.dll is at fault here

I am encountering the same issue, and it happens when the console says

[Client Request] /client/game/keepalive

Quote from pitAlex

first set /pickups to at least 1, then set /recruit on. Now, you can ask the bots you find to follow you (if they are of the same faction). If you extract successfully with them, based on their level compared to yours, you will get a friend request from them.

In which file do I need to configure that? I looked practically everywhere but didn't find, unless I wasn't looking for the right ones

Oh I forgot to mention that I was able to run scavs raids before; just this time it popped an error; I don't get why.

Hmm, I am experiencing a critical error when trying to play as a scav; which didn't happen before.

I will place the list of the mods I am currently using:

- Late To The Party

- Drakia's XYZ Waypoints

- DynamicMaps

- friendlyPMC

- HeadshotDarkness

- Kobrakon Firearm Deafen

- Menu Overhaul

- MoreCheckmarks

- SAIN

- BetterBulletCracks

- UnityToolkit

-Amands Hitmarker

- Looting Bots

- shadow flicker fix

- Skeleton Key

- VCQL

- Munitions Expert

- inory-agony

If you need anything else I will provide it asap.

Update: alright so it doesn't change a thing; or it doesn't change what I was expecting to anyways. My guess is that it could probably be an issue in the database since there is a staticContainer.json in: >SPT_Data\database\locations\MAPNAME\staticContainers.json

There are also different stuff present in the file folder but since I am not a dev I didn't change any value or parameter there, I just checked if the solution was in there.

This is a wild guess it could be something else as well.

I think a workaround for this would be to install an older version and replace the files of the new by the old since I never experienced this issue on the previous release (I will tinker it a little bit and post a future update).

I have been confronted to this bug as well, I was trying to check the SPT_Data file folder and see the different values on the "loot.json" / "match.json" and "item.json" to see if there could be something that could make a change.

I just modified the values in match.json (i have little idea of what it could be but I have a backup of the file in case I mess something up). So far the value is set by default by "false".