Jugginator

Sometimes if a host or server doesn't have port forwarding, some users may be able to connect and others can't. The best thing you can do on your end is to add the game install folder and the saves folder in appdata/roaming to windows security scan exclusions (and if you use any 3rd party security that too).

There's no requirement for always online for single player, IIRC you have to make one connection to Steam/EOS servers initially and then you can go offline/online all you'd like. I've taken a live game on the Steam deck offline in the car/airplanes and it's worked just fine. Just select Play Offline when you get to that point. If you mean in SP the game always is listening online, you're right there, there's no "single player" so to speak, you're hosting and joining a server when you do that, but like Gamida said there, just choose Not Listed.

Moving this around, please do respond back if you're still having issues, see my previous comment about using DX 11 rather than Vulkan @mandarine

Moving this around since this seems like it's Intel's fault here. Thanks for the info Sylen. If you do need further help with this, do open up a post in General Support and feel free to copy/paste or link this report there. Or respond here, either way that's easiest for you (you may get more coverage from users with this CPU in General Support though). Hopefully, Intel gets squared away on this as well as some Unity updates that will come with A22 will help this out.

An SSD as a boot drive will improve the computer a lot in general, but Quadro cards aren't meant for gaming at all and you will run into issues trying to game on those, which imo is likely the issue. You can snag older cards like an amd rx 480/580/similar pretty cheap now a days, which would perform way better and be more stable. Those Quadro cards are workstation purpose hardware.

Numpad 0, for future reference

The link you provided was for Phasmophobia, we'd need a whole log file. https://community.7daystodie.com/a21-bugs-main/bug-pool/how-to-report-bugs-found-in-a21-r4/

If you have any information that could help reproduce it, that will be great. We've spotted similar stuff internally and have been looking at it a bit, though. Definitely a log file

Will need a log file, the cause will be in there (from the server or host).

Hmm, have recent driver updates from Intel helped you at all? I know they've been working a lot on their drivers, and I'm also hoping an update to Unity for A22 will also help. if you're still crashing, please provide a new log file of it, and ensure Windows and your GPU are fully up to date.

This should have been resolved with Steam updates, from light research. If it's still doing this, please report the crash/Distro you're using here though, with a mention to me

Have you tried setting a larger swapfile? I honestly can't reproduce this

Lots of changes have happened recently; currently, I don't have any issues with Ubuntu or the Steam Deck, but I'll go over some Linux stuff using Mint/others mentioned here, if they're distros that are known to be stable with gaming.

Yeah this is a crazy bug. I'd like to revisit it at some point to see if changes for A22 helped this or not. Besides a working video and maybe screenshots of you setup, a save file may be informational to tinker with. Please mention me if you do respond back!

Making backups of your game save and world (if it's RWG, Navezgane or Pregen just the save folder) and getting a battery backup is about the best thing you can do. Sorry about that, we've done some work to improve save robust to help with this, though. You can check your log file and see if the vehicles are loading in, and then you can teleport to them. Sometimes they can load up in a previous spot in the world and you may not see them.

Making backups of your game save and world (if it's RWG, Navezgane or Pregen just the save folder) and getting a battery backup is about the best thing you can do. Sorry about that, we've done some work to improve save robust to help with this, though.

I'm going to move this to Not a Bug, but feel free to respond here or open a post in General Support (if you respond here, please Quote me) if you need more help getting this squared away

Hey @Kiyoshiye has it been working yet? Honestly, I'm running out of solutions here, but there have been a number of Windows updates and Nvidia drivers, I'm hoping one of those resolves it. Are you having crashes in other games? I'd be willing to have a chat on Discord or something and do some troubleshooting with you live, maybe spot something.

We need more information to help you here, but Tuesdays is Steam's maintenance day, which can cause this issue.

@JonSpider take a look at this, https://www.techspot.com/news/102555-intel-finally-investigating-reports-high-end-13th-14th.html

Unfortunately, your integrated GPU uses your system ram, which somehow is only 6092 MB? It may be 2 already allocated, but even if that's the case, you need 8GB of ram available. Make sure Windows Page Filing is set to automatic (if you haven't changed it, don't worry it's set to that by default), exclude the game folder and save folder on your antivirus, shut down as many applications as you can (you can also End the Explorer Process which can save a little bit, just load the game first). You should be able to play well with an extra 8GB of ram.

Confirmed for A22 b237, thanks for the information/reporting!

Vulkan on Windows has a lot of issues, use Direct X 11

2024-03-11T14:39:15 37.978 INF NET: LiteNetLib trying to connect to: 167.114.174.220:25566 2024-03-11T14:39:21 43.811 INF NET: LiteNetLib: Connection failed: ConnectionFailed 2024-03-11T14:39:21 43.812 INF NET: Steam NW trying to connect to: 167.114.174.220:25566 This is the main issue. Port forwarding needs to be done on the server/host. If port 25566 is used, then TCP 25566 and UDP 25566 - 25568 is needed to be forwarded.

Full log file please. In short: make sure (you and your friend) the main game folder and the saves folder in %appdata%/7daystodie (Roaming) is set to excluded in your antivirus, and you can try the Network Workaround option.