My issue is a popular one. Our game kicks us to the dashboard a couple times an hour (on xbox 1 S & X also different hosts and consoles)... at random times, these crashes delete EVERYTHING we spent hours on. When are you going to give us the respect that we paid just like PC gamers do, so why is this issue not being fixed before anything else!? PC can wait. I feel that a game that is meant to be for building and collecting, when the game deletes your stuff, it's doing the opposite of the purpose of the game. This is ridiculous. I've never seen makers care so little! Why is this glitch getting fixed and why is it not important? Why is PC getting all the focus when we can not even play!? This should be and needs to be a priority before any other fixing and updating. Console should be caught up more to PC as well. This is ridiculous. Everyone I have played with have been patient and tried waiting it out but we are about done! Your ratings are dropping fast because you dont want to fix a MAJOR issue. You have dropped to a 2.7 out of 5 I saw today. You were almost a 5 when i bought it. Shows you how much people are getting fed up. I hope to hear some good news soon. I want a date of an update for this issue. Thank you for your time.
PC CONSTANT CRASHING and/deleting
- Thread starter jonwhsjes
- Start date
Clare
Awesome Incarnate
Hi Jonwhsjes,
I am sorry to hear that you are also effected by the regular crashes that lead to the MD5 errors. I will post information below that may help you avoid them while the team work on this issue.
To clarify a few things, there are two teams working on the games. The PC team, which is The Fun Pimps who work on the PC version and overall game development and the Console team which consists of TellTale Games (Publishing) and Iron Galaxy Studios (Porting), who work on the PS4 and XB1 version of the game - this includes bug fixes and porting new features to the console version.
The Console team focus solely on the console version of the game, the work being done by the PC team does not delay any work on console. However sometimes they do collaborate if there is a common issue and if IGS are porting a new feature over.
The MD5 error is an issue that has multiple triggers. Since it's discovery almost every patch released there after has contained fixes for these triggers. The team also added in analytics to the game to track the number of MD5 errors so they can confirm their fixes for triggers are working. While I understand this may not be of great comfort to those like yourself that still experience the MD5 error, these analytics have shown a great reduction in the MD5 error with each fix.
The triggers have now been reduced to just a few more difficult to fix issues. The most common being the one that occurs after a crash as you have experienced. Currently the Console team are working on upgrading the game engine to Unity 2017, this upgrade should help with a lot of the more persistent issues in the game. We do not know yet what effect this will have on the MD5 errors as the team has not shared this info yet. When information on the issues it'll help is released it will be posted in Console News and Announcements with the other information about the upgrade and newest patch - https://7daystodie.com/forums/forumdisplay.php?87-News-amp-Announcements
I completely understand your frustration with this issue and I am sorry that you feel the Console team does not care about players and the issues at hand. Because of the separate teams working on each version of the game, different levels of information are shared. PC is still in Alpha and the creators are noticeably more open about what they are working on. The information about the console version however is released at the discretion of the Publisher, however their infrequent updates does not mean they are not working hard. Even though the remaining MD5 errors are more difficult to fix, the team have assured they are not giving up on this issue.
In the mean time, while I understand they are not always ideal for players, there are some workaround / things you can keep an eye on to help avoid crashes / predict them and for a lot of players they have managed to avoid MD5 errors also.
To help avoid crashes which can lead to MD5 errors:
- Crash indicators: There are a number of indicators your might spot that a crash is coming. A menu flickering / not displaying (you may have noticed this in your inventory before a crash?) Animals not spawning correctly. A sudden extreme change in weather. - Shutting down immediately and clearing the cache of the console by unplugging for 5 mins and rebooting may help prevent crashes that lead to MD5 errors, however if not done once you see an indicator, you may still experience a crash.
- Timing: If you know how long it takes for a crash to build up, some players time and reset without a crash trigger occurring. (You mentioned you crash often, but is it after roughly the same amount of time for each crash?)
- Crash Factors: Some things may cause whatever is generating the crashes to build up faster. This can include large amounts of the map explored in a single session, or large modifications made. While I'm not saying to avoid these, as they are at the core of Gameplay, it is worth noting it make have an effect when watching for crashes. Player Ignoringmywife1 mentioned a friend of theirs has avoided MD5 errors by not digging within a few blocks of their chosen base too.
- Storage and Crafting clusters: Separating out crafting stations and storage has worked for some. It is also worth noting that players find that stations that are currently crafting / cooking when a crash occurs may be more likely to be hit. - This seems to be the most common form of MD5 error at the moment. If you believe something else could have been the focal point please let me know.
MD5 errors themselves:
While I understand it is not the most ideal method, players have discovered a way to workaround MD5s after a crash. This is an unofficial workaround, so caution is advised but players have found it to be quiet successful if done immediately after a crash - https://7daystodie.com/forums/showthread.php?69218-Possible-work-around-and-or-solution-to-md5-crashes(base-wipes-resets)
It should be noted that once you see the results of an MD5 error it is already too late. The above workaround must be performed as soon as the crash occurs - checking to see if that crash resulted in an MD5 error will cause the game to auto-save and the workaround wont work as the XB1 save feature uploads exceptionally quickly to the cloud.
I hope that information can help, if you have any further questions about the MD5 errors I will do my best to answer them.
Clare
I am sorry to hear that you are also effected by the regular crashes that lead to the MD5 errors. I will post information below that may help you avoid them while the team work on this issue.
To clarify a few things, there are two teams working on the games. The PC team, which is The Fun Pimps who work on the PC version and overall game development and the Console team which consists of TellTale Games (Publishing) and Iron Galaxy Studios (Porting), who work on the PS4 and XB1 version of the game - this includes bug fixes and porting new features to the console version.
The Console team focus solely on the console version of the game, the work being done by the PC team does not delay any work on console. However sometimes they do collaborate if there is a common issue and if IGS are porting a new feature over.
The MD5 error is an issue that has multiple triggers. Since it's discovery almost every patch released there after has contained fixes for these triggers. The team also added in analytics to the game to track the number of MD5 errors so they can confirm their fixes for triggers are working. While I understand this may not be of great comfort to those like yourself that still experience the MD5 error, these analytics have shown a great reduction in the MD5 error with each fix.
The triggers have now been reduced to just a few more difficult to fix issues. The most common being the one that occurs after a crash as you have experienced. Currently the Console team are working on upgrading the game engine to Unity 2017, this upgrade should help with a lot of the more persistent issues in the game. We do not know yet what effect this will have on the MD5 errors as the team has not shared this info yet. When information on the issues it'll help is released it will be posted in Console News and Announcements with the other information about the upgrade and newest patch - https://7daystodie.com/forums/forumdisplay.php?87-News-amp-Announcements
I completely understand your frustration with this issue and I am sorry that you feel the Console team does not care about players and the issues at hand. Because of the separate teams working on each version of the game, different levels of information are shared. PC is still in Alpha and the creators are noticeably more open about what they are working on. The information about the console version however is released at the discretion of the Publisher, however their infrequent updates does not mean they are not working hard. Even though the remaining MD5 errors are more difficult to fix, the team have assured they are not giving up on this issue.
In the mean time, while I understand they are not always ideal for players, there are some workaround / things you can keep an eye on to help avoid crashes / predict them and for a lot of players they have managed to avoid MD5 errors also.
To help avoid crashes which can lead to MD5 errors:
- Crash indicators: There are a number of indicators your might spot that a crash is coming. A menu flickering / not displaying (you may have noticed this in your inventory before a crash?) Animals not spawning correctly. A sudden extreme change in weather. - Shutting down immediately and clearing the cache of the console by unplugging for 5 mins and rebooting may help prevent crashes that lead to MD5 errors, however if not done once you see an indicator, you may still experience a crash.
- Timing: If you know how long it takes for a crash to build up, some players time and reset without a crash trigger occurring. (You mentioned you crash often, but is it after roughly the same amount of time for each crash?)
- Crash Factors: Some things may cause whatever is generating the crashes to build up faster. This can include large amounts of the map explored in a single session, or large modifications made. While I'm not saying to avoid these, as they are at the core of Gameplay, it is worth noting it make have an effect when watching for crashes. Player Ignoringmywife1 mentioned a friend of theirs has avoided MD5 errors by not digging within a few blocks of their chosen base too.
- Storage and Crafting clusters: Separating out crafting stations and storage has worked for some. It is also worth noting that players find that stations that are currently crafting / cooking when a crash occurs may be more likely to be hit. - This seems to be the most common form of MD5 error at the moment. If you believe something else could have been the focal point please let me know.
MD5 errors themselves:
While I understand it is not the most ideal method, players have discovered a way to workaround MD5s after a crash. This is an unofficial workaround, so caution is advised but players have found it to be quiet successful if done immediately after a crash - https://7daystodie.com/forums/showthread.php?69218-Possible-work-around-and-or-solution-to-md5-crashes(base-wipes-resets)
It should be noted that once you see the results of an MD5 error it is already too late. The above workaround must be performed as soon as the crash occurs - checking to see if that crash resulted in an MD5 error will cause the game to auto-save and the workaround wont work as the XB1 save feature uploads exceptionally quickly to the cloud.
I hope that information can help, if you have any further questions about the MD5 errors I will do my best to answer them.
Clare