Jugginator

The part of it not affecting the player's stealth isn't a bug, the stealth meter is a blend of noise the player is making and the current visibility (light value), but I'll make an improvement ticket for the horn attracting zombies. No promises though, since there are quite a few factors to consider, such as trolling or balance in cases like a player blaring the horn riding in a circle to get the attention of a bunch of zombies and the stealth away, but it's something worth discussing. Moving to Not a Bug since it's really not a bug, but I will do a ticket for that ^^

I'm not really sure if this is intended or not, but I'll make a ticket and see if this is intended or needs to be changed.

Hmm, maybe try deleting that quest before your friend gets on? I know i had a minor error related to a quest that was help (not shared) by a friend before the update in a long game. The error didn't pop up until after a 6/7 hour session after I logged out and never got it again, maybe something went wonky after the update. The main complaint I see in the log is the quest POI lock, so in theory deleting that quest and avoiding the POI (quest-wise) for a few in-game hours may help

Does running with SSAO, SS reflections off help? Also try turning off reflection quality. Just trying to narrow it down a little bit

Yeah a time to live (or time to die, rather) is set to all the biome spawned zombies.

"after updating the server to b323, the logs didnt appear anymore." This is what you said above, why I thought that. A log file would be helpful though (the one you posted is locked) And yeah in every version test I had a client with that version connected. Maybe i needed more, not sure.

Yeah, that's usually a go to. When you do it, do make sure to either have your internet off when you reboot (after using DDU to uninstall) or select the option in DDU to prevent windows from installing a basic driver from windows update.

I'm curious can either of you run the game launcher that's in your main folder? The one called 7dlauncher.exe. try running it as admin too

Something else might be going on here, especially since you said you don't get log files from the server anymore. Make sure the server is validated completely. Also, my b317/b321/b324 servers are all generating log files. I made some builds and tested the following: Server on b317 and connected with a b317 client then a b323 client Server on b317 and connected with a b317 client then a b324 client Server on b324 and connected with a b324 client then a b321 client Server on b324 and connected with a b324 client then a b317 client I also did a couple more of these using our internal non-public builds and didn't have anyone getting kicked out I will bring this up with others on the team though, to see if maybe there's something missing to trigger this.

I've been looking at this, and while I can't reproduce this I've found a weird thing where if a client gets killed while they're loading in (the player model actually spawns in the world before the client actually finishes loading, it's a small window but it's there and can be killed before the client is done loading), and THEN the client is disconnected/gets kicked or whatever while still in that load screen, the game hangs on load until that client is kicked again and relogs. From what I gather, you may have died while you were logging in by rare chance? Either way, although I can't reproduce this, I did find another oddity related to it... so perhaps a fix for that would fix this also. May have been one weird combination of things that caused this in particular to happen. Thanks for reporting it and all the information... I'll put this in Work in Progress, since I can't confirm this bug but something similar. Feel free to add to this ticket though in a comment if you think of something/see this again or anything. By the way, the server you're connected to doesn't have the proper ports forwarded, evident by you failing to connect via litenetlib and falling back to steam networking

This may be caused by one of your mods, I'm not sure. I can't reproduce this, my performance doesn't change at all with rain on/off. I also don't see the readOnly flag warning, but this is certainly something to keep an eye out for and make note of. Thanks for reporting it

Hmm, I'm not able to reproduce this, but there might be some underlying/hidden combination of things to reproduce it -- so I'll keep this open and an eye out for it. Thanks for bringing it up

This should be fixed now. I'll have a look at it again to be sure.

Kind of a rare case but this does happen, confirmed that. Thanks.

My main guess is the driver isn't able to handle some of the new reflections put in, may want to try using DDU to uninstall the driver and get a fresh one installed. We have some teammates with newer AMD cards that haven't had issues, but I had an older AMD card a while back that had frequent issues with drivers, I started installing the drivers without using the AMD radeon software and it was more stable. A PC reboot with the game crash is a worse version of a driver dying/timing out. A crash dump would be better to see what's going on if any of yall could snag one.

Given that information, I'm learning to it might be a networking issue. Firewall/antivirus exceptions for the folder (do the whole folder, both in the main game on and the 7days saves folder in appdata), and try the Network Workaround option in the General section

Don't forget the slugs have more range and further damage falloff range.

Do note that this is an English forum, but I will see how an AI translation goes (it looks proper to me, but I am far from a fluent speaker): Cuál es el mensaje de error? Obtener el mensaje de error del archivo de registro

Well there aren't any errors related to bad save files, you never actually made a connection in that log file so not sure.

Without seeing what's going on in the server log, it appears that the server is busted, you're losing connection in the middle of connecting (I suspect this as a conjecture from seeing your client attempting to keep sending messages to the server, so the server looks to be dropping the connection first). You may want to poke customer support and ask them to take a look at the box

Hi! So, we have a couple of issues here: one is your GPU driver is timing out/failing (the d3d11: failed to create buffer is evident of that) and you're failing to connect to EOS. You've also got mods in there and I'm not sure if they're old or buggy, but remove them for now. I suggest the easiest thing first: Add folder/executable exceptions in your firewall and antivirus; verify your file integrity through Steam twice to be sure. Now you also said your computer was crashing, well, with the d3d11 errors your driver may be bad too. Use DDU to uninstall the current driver and then install a fresh one.

I mean a log file from you and the server, this is a server you are running right? Or did I misread that (quite possible lol)? Your log files are in %appdata%/7daystodie/logs and the server log should be in the main directory. Upload those to pastebin or something similar

Next step would be to take a look at the log then, one from a client affected by it and the server

Give the server a rest, good minute or two shutdown and reverify the files on the server, may have gotten some things mixed up

You're welcome Laim, glad it helped you out a bit. I concur, my eyesight isn't terrible but not the greatest and I'd like a bit more of a happy medium + less transparent at 100% too. Certainly something to consider whenever the UI gets overhauled.