Intermittent freezing during using mog locker, porter moogle, and loading new areas.

[Keeley]

I am now having the following problems I did not have before the new update today on April 2nd, 2013:

1. 5-8 sec screen freeze when trading slips to porter moogle
2. 2-5 sec freeze when accessing mog locker.
3. 40 sec+ screen freeze when entering a new area.

I can not move my character or access the menu during this time. It is not a one time problem, but continuous. I play on the xbox 360. I have been asking around and it seems others are having the same problems. Please fix this! Something obviously went wrong during the update on SE's part and now I am unable to play this game. Again, I never had this problem until I was forced to download the new update today.

[Tureer]

I am having very similar issues on 360 since the update. In addition to similar problems Keeley is having, I am also experiencing various inventory issues where items are not loading in a timely fashion. My experience also includes issues with mog safe, storage, mog locker, mog satchel, and mog sack. Sometimes when waiting for a 20 second freeze while accessing any of these inventories, the items do not appear for another 10 seconds, and the descriptions of the items do not load for a longer period after that. I am also noticing items taking a very long time to load while I am checking bazaars.
Before the update, I found it unfortunately common among 360 users for the game to freeze for 2-5 seconds between zones, and just wrote it off as a design flaw that wasn't a big deal. Currently though, it feels like my game has broken every time I change zones or need to get an item out of my inventory.
I've asked other 360 users, and it seems the effects of the update are varied. Some are not seeing any issues at all, while I seem to have an extreme case, but most friends of mine that play on 360 are having some noticeable slowdown since this update.
Just wanted to give some extra support to show Keeley's was not a unique situation. Hopefully we'll get some support soon...

[Keeley]

I have also noticed the same issue with items taking longer to load, particularly in my mog house, and especially the locker. I have asked around in game and it looks like others are having the same problem, not just on the xbox360 but also on the PS2. This is clearly a problem, and most likely a bug that needs to be fixed.

[Vih]

Having same problem game will lock for 30 seconds on zone also equip list in mh loading very slow, auction house is even worse. Also playing on Xbox 360 and checked all connection troubleshoots as well as ran a full file check no problems found.

[Kaisha]

http://forum.square-enix.com/ffxi/threads/243-Known-Issues?p=411899&viewfull=1#post411899

Known issue.

[Vih]

Those are issues yes but the mh delays ah delays and much longer freeze load is new as of april 2 update

[Keeley]

Nope. This is a new issue that was caused because of their patch. It still does not explain the porter moogle issue. It is something that they need to address and fix.

[Keeley]

I know that this is not an internet, modem or router issue because my other two characters on my account do not have this problem. I think that it may be an item conflict issue.

[Vih]

Has this issue even been addressed? At the moment I can't even play. AH is futile would take me 20 minutes to see a full equip list. I can create a red disconnect ball icon just by trying to look at my mog house items and any zone will create a red disconnect icon. Does anyone else have problem this bad? I'am debating a full re-intsall but that takes the better part of a day.

[Keeley]

As far as I know, no. I submitted a bug report for the moogle slip issue, which a GM is currently investigating. The more people that bring this issue up to SE and complain the more likely they are to fix it. The major problem that it is not happening to 100% of the community. If this continues, I will cancel my subscription as it makes it very difficult to play the game.

[Tureer]

I have also submitted a bug report for the situation. Not trying to badger them, but just wanted to provide additional information for the cause to try and help hurry along the repair. Hopefully they pay some attention to the issue so we can get back to not playing like savages.
@Vih - Yes, it sounds just as bad as what I am experiencing. Even though it seems not everyone got as screwed as we did, I'm surprised there are not more posts about it, since it is pretty crippling to playing the game.

[Altayr]

play an xbox and I have the same problem ....... I have problems with loading areas and inventory, but only with the main character and not with the other two ....

[Keeley]

When is this problem going to be fixed? This is horrible customer service.

[Drakox]

Same problem with xbox and waiting SE fix but of course they still earn our money

[Keeley]

I believe I may have found a solution to fix this problem for most of us on the Xbox360. Completely uninstall FFXI and the viewer. Clear your cache. Do an entire full, clean install (this means getting rid of macro's, etc; the game will ask you if you want to do this, twice). Download all the updates again. Entire process should take between 6-12 hours. This has fixed the problem for some, as well as most of my problems. Instead of a 50 second freeze, I only get about 1-2 seconds and that is only in my mog house and in crowded areas such as Jueno.

[Vih]

Many thanks Keeley. Did exactly as you suggested problem solved. Pain in the arse but mush less frustrating then the lockups.

[Altayr]

is complicated to uninstall and reinstall everything ?I think the only solution

[Tureer]

Uninstalling and installing the entire game did in fact fix my freezing issues. Unfortunately, after uninstalling the game, I found out that all original FFXI discs discs are not recognized by 360s ever since the dashboard update a couple years ago. Took awhile to find one of the newer ultimate collection discs, but I'm set up again and everything is back to normal. Overall a frustrating month for this game, but thank you Keeley for the suggestion that fixed this for me.