Jugginator

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

Woo! Glad you've got a machine that enables you to enjoy 7 Days to a fuller extent. I know you were struggling with the old one you had. Also good to know the game runs okay on M2s, thanks for sharing.

Your Event Viewer logs will show more of what happened, but two things: Both your cpu/gpu hitting 95c is a sign that there's a severe lack of cooling, you shouldn't be hitting temps that high, and with that system, an unknown brand of PSU is sketch and I would gander that may be the issue. Generally, I wouldn't use a PSU that came with a case, unless the PSU was a common/major brand. I did that exactly once and it fried my motherboard and everything connected to it in less than a year - not saying yours will do that, but those included PSU's are the bare minimal quality (the gold rating is not an indicator of quality) Oh, another thing I noticed, you're likely at the max draw of the power supply, that system alone not including any fans/storage devices/rgb or anything is about 700 on heavy load, which generally you don't want to go near the max the PSU can do, nevermind a no-named included in the case PSU.

Hi, sorry this is going on -- we are definitely aware and have been working on solutions. It would help a lot if you all could describe events leading up to the failed quest, things such as: Is this usually in a group, or sometimes solo (if solo, is this an MP game where you were the only one on, or always MP?)? Were these POI's that were previously quested that you know of -- and is it possible someone in your group did the POI as a quest that you don't know of? Were the POI's looted/raided before the quest was started? Mostly asking for such cases because just doing the quests doesn't reproduce those bugs easily, so it's looking like a certain set of circumstances and could use some help narrowing it down faster. Thanks!

I had a friend that had this issue, she needed better glasses + reduce the FOV. It may work better for you to increase it, not sure, but the "fishbowl" effect you get by increasing the FOV may be causing it. I don't get motion sickness but even increasing the FOV to 85 gets to my eyes a bit, so maybe try the other way.

Yeah if the game is fully supporting SLI and you've got the Nvidia profile for it, you can get an increase of performance. But, without heavy tinkering, you've still got the micro stuttering (frametime increases) caused by both of the GPU's preparing parts of frames to display (IIRC, been a while since I read up on a detailed report) because of the hand-offs between both of them. It's pretty much dead tech at this point, it never got adopted.

You said you have two 1080ti's? Are they in SLI? From what I gather, SLI will generally hurt your performance more than it will help. Don't forget driver updates, anti virus exceptions, moving the game to an SSD, and verifying your game files through Steam.

Thank you very much for the information and testing, perfect info.

Ah drat, was a wild shot. That error is known, needs to be fixed up yet. Can you generate a world without adjusting the Preview Quality? Maybe to a normal generation?

Try this: Power down your network -- the modem/router/any hubs or anything else -- remove the main cable going into the modem (fiber, coaxial, etc) as well In the meantime, go back to your computer and load up a command prompt under admin and enter these in one after another: ipconfig /flushdns netsh int ip reset Then, reboot your computer then hook your network all back up and power it on.

@MONOTREEME @Seclorum. Could you two please try turning SS Reflections off and see if that helps? You can find that in the Graphics setting

@bionictulipHi! Could you test to see if turning SS Reflections off in the graphics settings helps?

Hey, @Tonzza95, could you do a test to see if this happens with SS Reflections off? You'll find that in the graphics settings

Ah hah! Thanks for trying and reporting that. I honestly have no clue why it's doing it to you, but it's likely an incompatibility (as in, maybe AMD hasn't included support for this implement of SS reflections) with this series of GPUs. I'll wait to hear back from you, but that confirms that part. I'll make a ticket on it in the meantime.