Jugginator

Well, not sure what's going on here but I can't confirm this. It might be due to the server mods, likely mixed/bad data between updates.

Moving this to confirmed, there are certain behaviors and this doesn't reproduce by doing x/y/z, but we have a lot of data and hopefully can get a fix for this soon. There's a General Support post with a lot of information related to this, refer to here if you want

Thanks for the information everyone. If you have crashes but don't think it's related to this, please make a new ticket. If you have similar errors in your log file (look for d3d11 related errors) then do post here with a log file please. Moving this over to Work in Progress

Haha, you're welcome - glad that got it resolved. Steam is supposed to install those for you, not sure why it did. Time to have fun welcome back to the game.

Somehow you're missing VS redistributable packages, try verifying the file integrity twice in a row. If that doesn't work, download this: Latest supported Visual C++ Redistributable downloads | Microsoft Learn

Just wanted to update for anyone reading, I found a rather strange way to "fix" some of the switches that are broken: if there's a generator nearby the switch that in restore power cases you need to turn the generator on to activate, try destroying that generator. We've got a ton of evidence and test cases, hopefully we can get this worked out asap.

Post a log file onto pastebin.com for us to take a look at

Question for anyone that reads this and had an issue: can you think of a time where a switch was broken that wasn't tied to any generators? No need for digging, just try to recall the POI name and/or if there were any generators nearby

Yup, was just going to come here and say that. I loaded into the game in your character and it doesn't work, this was the confirmation I needed there, thanks for giving me this save. This opened a couple of doors (pun intended) of science that will help with debugging.

What's crazy about this bug is on both of those saves the switch is active and works. Did a few quests on the god one, will do some more. I have other hunches anyway too; still useful to have

I would try without any of the mods (including the Alloc's fix one, that one threw an error that I saw).

Nah definitely not against the rules, thanks. I will need the world file however, unless this was on navezgane or one of the pregens (if so, which one?)

Thanks! Normally I'd say it may not help, but in this weird case it can't hurt to have something like that to work off of -- that'd be nice to have. Version doesn't matter.

Just to let yall know since this is a serious and elusive bug, I think I made a breakthrough in reproduction, will bring it up in a meeting today and work on it more to get it solid. All this information is much appreciated, it really does help.

Hey there, she has old mods that don't work for this version. Remove the Mods folder, which should be in %appdata%/7daystodie but it could be in the main game directory too.

Yeah about the best thing I can think of to try to fix it is see if you can put mods in newly-acquired items. But it may be busted, sorry

Yeah you just need the game save and the world, which are both located in %appdata%/7daystodie (just copy and paste that into the run box). You'll find the game save in saves under the world's name, then the world in the generatedworlds folder.

If you remove the quest manually, it doesn't show up in the log And quite possibly it might be an issue with old saves continuing on, but I certainly wouldn't want to put it to chance. Good point though, if reproduction is still fruitless I may make a build on an older version of experimental and continue it on the latest stable.

This is something that we know of, fix incoming

Glad you solved it, and a reason why I always suggest people keep old/replaced parts that are known good for cases like this. I would recycle that PSU and never put it in a system lol. The cheap PSU's like that aren't built for quality, and hope that whoever uses them doesn't use anything but 50 - 60 percent of the total power capacity, since higher usage will be unstable. High quality PSU's can handle being near or at max load, lesser ones cannot.

What makes it weird is simply doing the quests multiple times doesn't seem to be a trigger (pun mildly intended) for the bug, I just spent the last 6/8 hours doing T6 infested quests over and over (just today, not including other days lol). I started doing things like pre-looting and sometimes destroying some switches/doors that are tied to trigger volumes and whatnot (including blowing up most of some of them) and then doing more quests there. No worries, we'll get it figured out, just wanted to share some test cases I did today. I did do only two at red mesa, I'll do some more shortly. And no, there's no command that I know of that will do that, maybe there's a gameevent command for it, check shift + f6 Actually, since the quest isn't completable, if you want to get around that just log out and back in since that will reset the quest, then abandon or retry it or just say you did complete it and use a ticket to get rewarded. There is a command that draws sleeper volumes in boxes, enter sleepers draw in the console. Might help in screenshots. Green - normal Red - quest exclude Gray - volume that is triggered Blue - trigger volume Blue Added - has entities spawned (green becomes cyan, red is purple, gray is blue and so on) Dark Tint - is completed

Sorry what was the issue?

Thank you all for the information, that certainly helps a lot. This is definitely a top-priority bug investigation/solution so hang tight. In the meantime though, if you get a bugged quest that you know you've completed, there are dev item tickets in the cm menu that you can read to get a completed quest to turn in to at least be compensated. A bummer thing to happen, but those can be used for it in the meantime.

Confirmed, that cleared up a little confusion on what I saw, didn't come across checking if it was due to party members or not. Thanks

Actually I spotted something weird with bleeding, I'll have a look