Oneback,
I just posted this on EA's forums. I've since had another guy follow up and say that he's seeing something similar. It might be worth a try. If you need to bump someone from the dynasty, go ahead and bump me.
One upside is that when you create the second dynasty under a different PSN name, you shouldn't have to retire the original dynasty. That way you can sanity check the "new" dynasty before retiring Powerhouse3. Like check for saved results and the like.Quote:
UTVOL54, I hope you see this ...
You said that you used your brother's name as the second commisioner when you retired the dynasty and reloaded. Was your brother previously a member of the dynasty? I am beginning to think that may be the difference between your experience (the reload succeeded) and mine.
I just tried two different tests. In both cases the dynasty was working before I retired and reloaded.
Test 1:
1. Simmed my Week 1 game and did some light recruiting.
2. Exited the dynasty, re-opened, chose to Save File (in theory, this would save a copy of the dynasty with my results preserved).
3. Exited, retired the dynasty.
4. As UTVOL said, go to File Management, Load & Delete, and load the dynasty.
5. The new dynasty failed to create, failing during "Finalizing Dynasty Update" and returing "Transfer Failed". That's consistent with the problem everyone's having.
Test 2:
1. Created another test dynasty, this time saving the file as soon as I advanced to Week 1.
2. Did not play any games or do any recruiting.
3. Exited, retired the dynasty.
4. Loaded the dynasty from File Management.
5. This new dynasty succeeded and I was able to advance on to Week 2 after creation.
Right now I'm thinking that UTVOL's success may have been because his brother's PSN didn't have any recruiting or game results, and that's why it was able to reload. Unfortunately, beyond what I've already done it's nearly impossible for me to test it because I only have so many PSN accounts.