PS3 longer zoning time is normal. It has less power so it takes longer to load resources from the HDD.
I installed an SSD in my PS3 just for this game and I'm never the last to load. Almost always 2nd to load actually. Loads real fast compared to what I see on other players videos.
I play exclusively on the PS3 and my average ping to the JP Datacenters is roughly 99 - 102ms. Putting slow loading times and FATE/mob loading issues aside, I don't notice any slowdowns of animations or dungeon mechanics that affects me adversely. I.e in a fight such as Titan, I am able to dodge them although there will be several instances where I still get hit even though I have run out of the AOE.
It seems to be your connection speed I would say. Have you tried pinging your respective data centres (NA/JP)?
I know that is no solution for the Problem you have (lag) but you could try to stand very (very, very) close to the enemy and run
right into him when he attacks (Maybe behind him?). I dont know if it works but you could try.
Yeah i pretty much had to run to the center of the stage every time he targeted me, I would still get hit, but wouldnt fall off the stage. Until the stage got smaller about the 3rd or 4th geo crush. then the stage was too small to survive the push back even from the center, but luckily Titan was on his last leg and my team finished him off.
Also if it was my internet connection that was failing, then as the healer, my team and myself would have died in every single dungeon, but no, its only aoe attacks that i cant seem to avoid, everything else is fine, well apart from all the other problems, but everyone already knows about them
This is not just a PS3 issue, there are many PC players having this issue as well.
I can say that I have had this problem with Titan on PS3 as well. I would watch others appear to move out of the aoe AFTER the attack, and not get hit, whereas I would move before and usually get hit. I have noticed this in certain other places, but Titan magnifies the problem greatly. I have had the problem both in characters on JP and NA data centers. That said, you can usually avoid the problem just by continuing to move. There is a pattern to his attacks, and if you learn the pattern you can move prior to the landslide.
I could be wrong, but I actually think this is a drawing priority problem which is made worse on the PS3 (though can still happen on lower end PC's as well), not so much a latency to server issue. That is, the PS3 can only draw so many things at a time, but the drawing priority puts the AOE after other objects, so the PS3 doesn't draw it in time.
Similarly this priority problem has caused me issues with NPC, where the NPC doesn't appear until after it has drawn the other players and pets in the vicinity. Which obviously is backwards. For example when I summon a retainer around the market board, I don't get the retainer until after it draws everyone else around the bell, whereas if I summon in the inn, it is instant. This can take upwards of 10 seconds. Which is fine for a retainer. But anything more than 0.25 seconds is too much for an AOE.
Stopped reading there.
Stop coming across like a whiney brat. Kthx, was going to help with network settings advise on how I haulted 100% of my lag, especially aoe but... Nvm. I'll save it for someone who would appreciate it.
Tip- Google translate the Japanese forums. Some of those ps3 players have good tips. But you can find that on your own.
The issues that some PS3 users are seeing doesn't appear to be an issue that can be solved on the client end. I've done some testing on the network infrastructure that Square is using and it does appear that some users are being routed though overloaded nodes and bottlenecked fiber lines. This is part of the problem. The PS3 also has to route though another hop (the PS Servers) to get to the end client. Adding that extra hop can and will increase latency on an already overtaxed network making the latency issues much more apparent on the PS3. In my mind, the issue with the PS3 clients is one of two things (or a combination of the two):
1.) Network latency on the host end. As PS3's have to route through already burdened racks and nodes combined with the extra hop that the PS3 has to pass through is adding a crippling amount of packet loss and MD5 errors. This cannot be solved on the client end. Nothing anyone does either with their network will correct the issue. You may be successful with a VPN, but only for the fact you are tricking the host into changing your route path to hit less taxed nodes. This is a gamble and even with a VPN, your route path may not change.
2.) A hardware component defect. Though this is rare, This could be a cause of what PS3 users are seeing. It could be a faulty NIC that can be dropping packets due to bad translation and/or unable to translate the amount of data it receives. It could also be a faulty GPU/CPU/Fan. The GPU could be heating up to the point that it has a hard time rendering the display correctly. The same can apply for the CPU. The fan on the unit may not be able to properly cool the circuits causing rendering issues or dust build up in the system itself creating issues. Reapplying thermal paste to the CPU/GPU may increase the performance as well as blowing out the PS3 for any dust. Replacing the fan may also give some results. If the NIC is faulty, there isn't a whole lot one can do about that expect purchase a new PS3 (to modify would cost more money than a new unit).
The issue is more than likely the the first, but mileage varies for each user and some could be affected by second as well.
Hope this helps!
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.