Issue Description:
At the beginning of the mission, everything is fine, but gradually small lags begin, and then the whole picture freezes and throws it into the main menu
Could not remember wich specific time period but it happened several times throughout the night and we did restart a few times because were all pretty sure were getting a rather large memory leak on the regular so Iām just throwing up all the logs for the night. Iām sorry if that means extra work
After an almost perfectly smooth gaming evening we experienced a curious disconnection.
It happened during gameplay after a lot of lag (being teleported around the same room and enemies skating).
We soon after both disconnected simultaneously but my error was 2001 and my gfās was 2003 instead. I think it could be interesting to understand why this difference. See hour 20:46.
My log console-2022-12-01-18.16.35-040a01a8-5258-457e-985b-c5a3230c9337.log (990.8 KB)
These are my specs:
CPU: 11th Gen Intel(R) Coreā¢ i7-11700F @ 2.50GHz 2.50 GHz
GPU: RTX 3070. Nvidia drivers up to date, installed with clean install mode.
RAM: 32 Gb
drive: SSD
OS: W11
Cabled to router
My gfās log: console-2022-12-01-19.07.22-b3e792c4-a86f-4fcd-bf86-c11855be22bf.log (553.5 KB)
Her specs:
CPU: Intel(R) Coreā¢ i7-10750H @ 2.60GHz 2.59 GHz
GPU: RTX 2060. Nvidia drivers up to date, installed with clean install mode.
RAM: 16 Gb
drive: SSD
OS: W10
WiFi to router
We kindly ask that you complete the questions below. With this information, we can add it to our database for investigation.
All day on the 22nd Iāve experienced routine disconnects from active missions, and all seem to happen sometime after the halfway point (closer to 3/4 of the way through), and itās been very consistent, and itās become routine today. Iād experience them prior, but much less often, maybe one mission out of 5. The mission type, difficulty, and modifiers seem to play no role in the disconnections, and I only disconnect once. The error code Iāve been getting is internal_error 2003 each time, and Iāve had no issue reconnecting to the session to finish the mission.
Error 2007 got fixed for me, now playable but still geting error 2003 sometimes and also crashes
GUID: 28dc1423-337d-4245-9ae2-25f115884bc5
Log File:
Info Type:
Also getting this error 2003. I played a solid 3 days with no issues, ran perfect then the day the most recent update dropped began I started getting the error 2003. Iām really sorry fatshark but youāve given me a lot to think about for day one or early access for new games. Its rough releasing a game but whatever pressure you guys are under via publisher or any other corporate struggles, ignore them. Get this fixed, and a bit of a gift for those who have been suffering (namely everyone) would go a long way to restore faith. Right now I just want to play. Iāve had 4 days off (in 3 weeks) and so far Iāve only beenable to play one day of those days off of just uninterupted play.
This is happening constantly for me and makes the game unplayable - generally occurs within two minutes of loading into the Mourningstar, regardless of whether Iāve joined a game or when Iām still hanging around the ship. But sometimes it also happens on the loading screen.
Doesnāt matter which character Iām on.
I didnāt have this problem at all in pre-order beta or just after release, so it might be something to do with the recent patch?
Also did Going Out with a Bang penance in this mission but havenāt received it in-game because of the error. I do have the achievement on Steam now though.
2022.12.09 - 19.27.25.10 CET
As with other reports, I pretty much canāt get past character selection with this issue and Error 2001. I can login to the hub, but my character is frozen and soon afterward Iām booted back to character selection. Iāve tried resetting my router to no avail.