Re: [PS5] Franchise won’t load out of game

@fizzmon 

Did clearing the cache fix it for you?

Over the past few weeks, I tried out a whole bunch of things to get around this bug and figured some stuff out:

- I'm playing on a ps5 and I have the ps5 disc version

- as I wrote in a previous post; deleting my cache doesn't do it for me

- I also noticed the same things as cmx-07 did: replays getting stuck, no halftime cutscenes, players frozen on the field, etc.

- The bug always occurs when I play as an owner

- If I play offline the bug also occurs pretty much always

- The bug doesn't seem to occur as much if I import the default roster for each team, but only if I play as coach and online

- if I use custom-made rosters, or if I'm making too many changes to the roster in franchise mode (trades, number changes, etc.) the bug starts happening again

- the only fix for me that works, is to completely close madden when there's less than 1 minute left in the 4th quarter, restarting madden, then continuing the game and playing or simulating the rest of it, works every time but gets annoying pretty quickly

I don't want to sound like I'm complaining too much, but this (full-priced) game is out for a month now and there's still no patch... smh

@EA_Blueberry

Well rather than fixing it they made it worse. After the latest patch the cache clearing workaround is not working anymore. Screen loop happened upon trying to exit an offline franchise game upon completion.

It is beyond me that after months nothing has been done to address this and that a patch would actually make it worse.

Hard not to get upset and try to remain positive when such a low quality product is released and failed to fix in a timely manner. Really disappointed as some said in previous post perhaps the worst madden in years.

Downloaded the latest patch two days ago for the PS5. Tried another offline franchise mode game tonight, and it's currently stuck in the continuous loading screen bug after finishing the game. I waited about five minutes before coming to the forums to type this. We're two months into this. This is ridiculous. Is there any update to this situation other than "the team is aware..."?