Still unable to play Wild Hearts (PS5)
I originally purchased Wild Hearts 3 weeks ago on PS5 (digitally) and at this time I'm still unable to play the game due to it crashing on the second loading screen or if I'm lucky within a couple of...
Forum Discussion
EA_Illium
EA Staff (Retired)
EA Staff (Retired)Hi @PulsingRain Has this continued after the update that came out today?
If so to confirm have you tried the following steps?
- Clear the systems cache (Close the game completely > Turn off the console > Wait 30-60 seconds > Restart and Relaunch)
- Verify you signed into your PSN account
- Check for updates
- Restore Licence
- Try the steps in our Connection and Advance Connection Guides
- Open your PS5 NAT Type
- Change DNS settings (You can use the public google DNS primary: 8.8.8.8, secondary: 8.8.4.4, unless there is a different DNS you would rather use)
- Entering Safe Mode and Rebuild your PS database
Hello EA_Illium,
Thank you for taking the time to reach out to me with your recommend solutions, I truly appreciate it.
I went back and checked/tried each of your recommendations and at this time I am still having the game crash on me during the second loading screen after making sure of having the most recent update for the game that came out today as well.
Thank you again for assisting me with this and looking into the matter.
Update: Game sort of runs now
Hello @EA_Illium, as of today I wanted to provide you with an update in hopes this information is helpful to you.
This morning I tried playing wild hearts and was continuing to get the same loading crash issue as mentioned before. I decided to play a different game instead with no issues for it crashing on my PS5 (the game is also digital). I ended up have to take care of a few things and left my PS5 running with the other game I was playing on idle for about 40 minutes. I came back and decided to try one last time to launch and play Wild Hearts and for whatever reason, I was able to get through the loading screens and get into the game without it crashing for at least an hour or two.
The game did still crash here and there; notably at times for a cut scene (mainly when encountering a monster for the first time), if I fast traveled to another camp on the same map, or if i was idle for more than a few minutes. However, after the crashes I was able to load up the game and continue to play without any issues until the next crash another hour or two apart.
I wanted to give you an update in the hopes that this new information could possibly help as well. I can't say for certain at this time that it is or will be a consistent work around as I haven't turned off my PS5 since that point I got the game to work. I will provide a second update to this one if there are any issues with the game trying to launch it tomorrow or if this current work around works again.
- EA_Illium
HI @PulsingRain Thanks for this update, I would be happy to pass this on to the team.
To check the account you are playing with, is it the same account that purchased the game?
Also, I wanted to confirm if you participate in Sony's beta program.
Thank you very much for passing this information on to the team to look into.
I do still have varying issues of the game successfully loading and crashing, however, now it does seem most of the time the crash comes once I get loaded into the game or shortly after, instead of just at the second launch loading screen as previously mentioned. This is still using the method of launching another game first and letting it run for a little then closing out and opening up wild hearts. Without doing that method it does still seem to crash on the second loading screen after a few trials of doing this.
To answer your question, yes, to my knowledge my account is the same one in which I purchased the game with. The way in which I signed into this EA account is through my PSN where I purchased the game and downloaded it digitally.
As of right now I am not currently a part of the Sony beta program. I did receive an email to join the program, however, I have yet to redeem and activate it in the event it could cause further issues.
