Anonymous
8 years agoRe: [solved] Unravel2 crashes constantly on level7 (PS4)
replying to myself with a solution:
after contacting EA help, they sent me instructions to delete the game data and download it again, or delete my saved game and start a new game, but i didn't want to do that and lose all progress (it's the last stage!)
so i tried to mess around with the options inside the game and i think i found a combination that works:
1- disable Game Assists completely (slow mo mode never worked for me anyway??)
2- Disable usage information reports inside the game (i forget what it's called exactly, it's an option to send the developer information on your gameplay, i think it's labeled "network connection" or something)
3- i don't know if it contributed to resolving the bug but i played as a single player. player 2 only logged on and took control of the other character only after the next check point.
i hope this helps whoever stumbles on this bug like i did, and if anyone finds another solution please post it here for future reference, as it seems there are no conversations or solutions on the internet about this exact bug!
after contacting EA help, they sent me instructions to delete the game data and download it again, or delete my saved game and start a new game, but i didn't want to do that and lose all progress (it's the last stage!)
so i tried to mess around with the options inside the game and i think i found a combination that works:
1- disable Game Assists completely (slow mo mode never worked for me anyway??)
2- Disable usage information reports inside the game (i forget what it's called exactly, it's an option to send the developer information on your gameplay, i think it's labeled "network connection" or something)
3- i don't know if it contributed to resolving the bug but i played as a single player. player 2 only logged on and took control of the other character only after the next check point.
i hope this helps whoever stumbles on this bug like i did, and if anyone finds another solution please post it here for future reference, as it seems there are no conversations or solutions on the internet about this exact bug!