SE sort out your Updater ><

[Taru_TwoPointO]

756k UP. 10mb Down. done in 30min installed. i dunno. Might just be location. I'm in Eastern Pa.

[Dimo]

man their patcher is horrible. but the worst part is the fact we are downloading the same patch over and over...causing it to take even longer. Like someone else mentioned..when we get the huge 1.18 patch are we seriously gonna have to redownload that again with 1.18a/1.18b??! you gotta be kidding me.

[zaviermhigo]

Once I properly port forwarded and port triggered for ffxiv, my update time went from 3 hours to 30 mins, and then it was about 15 mins max.

And yeah my longest wait time for FFXI patch on computer was 1 hour, and that was an expansion I believe, average was 10-15 mins.

[viion]

I've had it port forwarded since release, made no difference. =(

XI patcher was different in that it had better direct support and didnt download previous patches, and was every 3-5 months.

[Vanguard319]

I had the dreaded 0.0 on dl speed for a little bit, about an hour in and at 44.5% (60~80 kb/s) and 40 minutes to go. It seems like shutting down my firewall for a moment helped, but yeah, this updater is in desperate need of improvement. I hope it's the next thing on SE's list of improvements.

[KaiKatzchen]

I had no issues, started it about 5:50 and it was done and installed by like 6:05... actually I've never had an issue with the patcher, though I know a lot do.

[Kilta_Firelotus]

ok it was in the maint info

At the following time, we will be performing maintenance on FINAL FANTASY XIV to implement patch 1.17c.
During this period, FINAL FANTASY XIV will be unavailable.

We apologize for any inconvenience this may cause and thank you for your understanding.

* Clients will update automatically upon launch after release of the patch.

* Patch download rates may vary depending on server congestion.

*Comprehensive patch notes will be posted on the Lodestone the day of the patch’s release.

[Date & Time]Jun. 15, 2011 2:00 p.m. to 4:00 p.m. (PDT)* The completion time may be subject to change.[Affected Service]- FINAL FANTASY XIV


and the link http://lodestone.finalfantasyxiv.com...2456e24faec166

[Delsus]

ok it was in the maint info

At the following time, we will be performing maintenance on FINAL FANTASY XIV to implement patch 1.17c.
During this period, FINAL FANTASY XIV will be unavailable.

We apologize for any inconvenience this may cause and thank you for your understanding.

* Clients will update automatically upon launch after release of the patch.

* Patch download rates may vary depending on server congestion.

*Comprehensive patch notes will be posted on the Lodestone the day of the patch’s release.

[Date & Time]Jun. 15, 2011 2:00 p.m. to 4:00 p.m. (PDT)* The completion time may be subject to change.[Affected Service]- FINAL FANTASY XIV


and the link http://lodestone.finalfantasyxiv.com...2456e24faec166

What you fail to realise is what P2P means, it is Peer to Peer, SE's servers host the update, which is then passed to the first clients to update, they then upload what they have recived and also begin to host the update.

With a P2P system if there is server congestion SE is doing somthing badly wrong with thier systems, most of the patch comes from other people uploading, when SE mentioned congestion it was to avoid people realising they truth which is that thier patcher sucks.

SE should have realised that the ports there using are blocked by 99% of firewalls, what they could have done is set the patcher to scan for open unused ports and use those. Or just use a port that is open.

Utorrent is designed to adapt to firewall ports and work around closed ones, which is what SE need to do with thier patcher, a well designed P2P system will never need an end user to configure port forwarding because it opens a direct unsecured connection right to your PC, any port scanner will find it for an intruder to access your PC with no problems. This is the reason Utorrent has an option to randomise the port it uses.

[Ilean]

What you fail to realise is what P2P means, it is Peer to Peer, SE's servers host the update, which is then passed to the first clients to update, they then upload what they have recived and also begin to host the update.

With a P2P system if there is server congestion SE is doing somthing badly wrong with thier systems, most of the patch comes from other people uploading, when SE mentioned congestion it was to avoid people realising they truth which is that thier patcher sucks.

SE should have realised that the ports there using are blocked by 99% of firewalls, what they could have done is set the patcher to scan for open unused ports and use those. Or just use a port that is open.

Utorrent is designed to adapt to firewall ports and work around closed ones, which is what SE need to do with thier patcher, a well designed P2P system will never need an end user to configure port forwarding because it opens a direct unsecured connection right to your PC, any port scanner will find it for an intruder to access your PC with no problems. This is the reason Utorrent has an option to randomise the port it uses.

- Many of us who are having the problem are knowledgeable people with proper port forwarding set up, so it has nothing to do with firewall configuration.
- Without you accepting incoming connections (e.g. forwarded ports) you can't receive data from people who can't accept incoming connections either, you can't reach them to ask for it, they can't reach you to offer it. Accepting incoming connections is integral for P2P networks.

Also having an open port won't automatically get you hacked, unless you are sony.