Forum Settings
       
« Previous 1 2
Reply To Thread

Maintenance (25th)Follow

#1 Aug 25 2013 at 9:15 AM Rating: Excellent
**
310 posts
At the following time, we will be performing emergency maintenance. During this period, the Worlds listed below will be unavailable.

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

[Date & Time]
Aug. 25, 2013 from 8:30 a.m. to 10:30 a.m. (PDT)

* The completion time may be subject to change.

[Affected Worlds]
North American/European Data Center Worlds
- Adamantoise
- Balmung
- Behemoth
- Cactuar
- Cerberus
- Coeurl
- Diabolos
- Excalibur
- Exodus
- Faerie
- Gilgamesh
- Goblin
- Hyperion
- Lamia
- Leviathan
- Malboro
- Midgardsormr
- Moogle
- Odin
- Phoenix
- Ragnarok
- Sargatanas
- Shiva
- Siren
- Ultros

Edited, Aug 25th 2013 11:15am by MitArgento
#2 Aug 25 2013 at 9:16 AM Rating: Good
**
424 posts
http://youtu.be/VDqIXbdlpa4
#3 Aug 25 2013 at 9:17 AM Rating: Excellent
Thanks for the update, maybe I'll be able to log in after maintenance.
#4 Aug 25 2013 at 9:18 AM Rating: Good
Scholar
**
525 posts
It would be comical if it was funny in any way, shape, or form.
____________________________
I used to care about my sig. Then I got mocked and butt-hurt. I shall commence with the self-pity now.
#5 Aug 25 2013 at 9:19 AM Rating: Decent
25 posts
IDK why but this just made me laugh during the beta:

http://www.youtube.com/watch?v=ZmUsdDOyhBM
#6 Aug 25 2013 at 9:19 AM Rating: Good
*
190 posts
One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.
#7 Aug 25 2013 at 9:21 AM Rating: Decent
20 posts
supermegazeke wrote:
http://youtu.be/VDqIXbdlpa4

http://www.youtube.com/watch?v=zfbK_dbsCu0
#9 Aug 25 2013 at 9:23 AM Rating: Decent
*
190 posts
omghotcawk wrote:
Phasmoto wrote:
One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.


except the maintenances haven't fixed anything so maybe they shouldn't be ending early.



We don't know that. They may be fixing things you are unaware of. Just because they didnt fix what you wanted fixed, doesnt mean they didnt fix anything.
#10 Aug 25 2013 at 9:24 AM Rating: Decent
26 posts
Too bad they don't actually fix the problem the first time.

I'd rather see an entire maintenance window used to fix the issue instead of multiple instances plus extremely unplayable conditions afterwards (the error codes as of today)
#11 Aug 25 2013 at 9:24 AM Rating: Good
Maybe they need to do maintenance on their maintenance so everything they do maintenance they don't have to do maintenance again.. Am I right?
#12 Aug 25 2013 at 9:25 AM Rating: Decent
Scholar
**
525 posts
It's like the 22 hour update from ffxi in 2004. It doesn't actually end, it just promises to end.
____________________________
I used to care about my sig. Then I got mocked and butt-hurt. I shall commence with the self-pity now.
#14 Aug 25 2013 at 9:41 AM Rating: Excellent
**
728 posts
Buffylvr wrote:
It's like the 22 hour update from ffxi in 2004. It doesn't actually end, it just promises to end.


I remember that.. Only I was on dialup and it never did actually end.. I'm still waiting on it to finish.
#15 Aug 25 2013 at 10:01 AM Rating: Decent
***
1,824 posts
omghotcawk wrote:
Phasmoto wrote:
omghotcawk wrote:
Phasmoto wrote:
One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.


except the maintenances haven't fixed anything so maybe they shouldn't be ending early.



We don't know that. They may be fixing things you are unaware of. Just because they didnt fix what you wanted fixed, doesnt mean they didnt fix anything.


Except, we do know that, as they stated the exact problem they "fixed" after each maintenance, which are not fixed.

The problem was too many people were trying to get in to the instanced battlezones at once. Boot everyone off the server for an hour, problem solved for a little bit.
#16 Aug 25 2013 at 10:04 AM Rating: Good
Scholar
Avatar
***
1,519 posts
omghotcawk wrote:
Phasmoto wrote:
omghotcawk wrote:
Phasmoto wrote:
One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.


except the maintenances haven't fixed anything so maybe they shouldn't be ending early.



We don't know that. They may be fixing things you are unaware of. Just because they didnt fix what you wanted fixed, doesnt mean they didnt fix anything.


Except, we do know that, as they stated the exact problem they "fixed" after each maintenance, which are not fixed.


Just because they fixed one cause of an issue doesn't mean they fixed all causes of an issue. It isn't as simple as "fixed error 101, will never happen again". The same issue for the end user could have many different causes. This is one of the most annoying things about working in software. Your users don't have a clue about how the software is working, but they know everything about the software. If you fix an issue that was causing slowdowns for 5 of your users and have that in your patch notes, 20 others will come forward and say that you didn't fix it because it is still slow for them.

With that said, this is still on SquareEnix and reflects poorly on their management. For whatever reason, they were unable to properly configure their NA/EU datacenter (or, the traffic on the NA/EU datacenter has exposed issues that weren't present under lighter loads, as evidenced by the fact that the JP datacenter doesn't seem to experience). If, however, there is enough traffic on the NA/EU servers to causes these issues, I question why both datacenters have the same number of servers. Capacity planning is hugely important for any system, but it doesn't seem like the managers took the time to do it properly. The company also boxed themselves into a corner with a release date, so they were unable to extend the open-beta period in the event of issues occurring. I know that, where I work, there wouldn't be an engineer who didn't complain about having the release date so close to our largest beta test.
#17 Aug 25 2013 at 10:07 AM Rating: Excellent
Scholar
**
525 posts
http://forum.square-enix.com/ffxiv/threads/67198-EU-Several-Worlds-Emergency-Maintenance-%28Aug.-25%29?p=1060024#post1060024

Quote:
At the following time, we will be performing emergency maintenance. During this period, the Worlds listed below will be unavailable.

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

[Date & Time]
Aug. 25, 2013 from 15:30 to 17:30 a.m. (GMT)


Based on that note, maintenance will never end, because 17:30 a.m. doesn't exist.

Close it down! We're all going home!
____________________________
I used to care about my sig. Then I got mocked and butt-hurt. I shall commence with the self-pity now.
#18 Aug 25 2013 at 10:09 AM Rating: Good
*
190 posts
omghotcawk wrote:
Phasmoto wrote:
omghotcawk wrote:
Phasmoto wrote:
One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.


except the maintenances haven't fixed anything so maybe they shouldn't be ending early.



We don't know that. They may be fixing things you are unaware of. Just because they didnt fix what you wanted fixed, doesnt mean they didnt fix anything.


Except, we do know that, as they stated the exact problem they "fixed" after each maintenance, which are not fixed.



Clearly you've never debugged a something.
#19 Aug 25 2013 at 10:12 AM Rating: Excellent
*
180 posts
And to be honest SE could be telling the truth...I have to debug a bunch of my projects and while I fix the error I was looking for...THAT fix sometimes brings other errors with it or now that the big error is no longer there I can finally see the other smaller errors that it was hiding.
#20 Aug 25 2013 at 10:12 AM Rating: Decent
Phasmoto wrote:
omghotcawk wrote:
Phasmoto wrote:
One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.


except the maintenances haven't fixed anything so maybe they shouldn't be ending early.



We don't know that. They may be fixing things you are unaware of. Just because they didnt fix what you wanted fixed, doesnt mean they didnt fix anything.


Maybe they will fix something really basic.............like letting me log in while I have time to play for once.
#21 Aug 25 2013 at 10:15 AM Rating: Decent
*
190 posts
crazy0taku wrote:
And to be honest SE could be telling the truth...I have to debug a bunch of my projects and while I fix the error I was looking for...THAT fix sometimes brings other errors with it or now that the big error is no longer there I can finally see the other smaller errors that it was hiding.



Exactly.


Imagine trying to debug something that thousands of people want it to be done NOW NOW NOW IN LESS THAN 2 SECONDS!

The pressure they must be feeling. Ugh.
#22 Aug 25 2013 at 10:19 AM Rating: Good
Phasmoto wrote:
crazy0taku wrote:
And to be honest SE could be telling the truth...I have to debug a bunch of my projects and while I fix the error I was looking for...THAT fix sometimes brings other errors with it or now that the big error is no longer there I can finally see the other smaller errors that it was hiding.



Exactly.


Imagine trying to debug something that thousands of people want it to be done NOW NOW NOW IN LESS THAN 2 SECONDS!

The pressure they must be feeling. Ugh.


Man if only they could have a period of time to test out the software and network in advance. That would surely be helpful and allow more time for debugging. A time for example where players logged in and played and reported bugs. A time when network traffic issues could be caught, fixed and planned for on release. A time when error 3102 could be caught and fixed, or at least the time to change the code name to 10102. If only........
#23 Aug 25 2013 at 10:23 AM Rating: Excellent
Scholar
**
525 posts
In their defense, and after nine years of ffxi, I'm not too interested in defending them: 3102 hasn't been much of an issue this first 30 hours.

It DOES appear they fixed that.
____________________________
I used to care about my sig. Then I got mocked and butt-hurt. I shall commence with the self-pity now.
#24 Aug 25 2013 at 10:27 AM Rating: Good
crazy0taku wrote:
And to be honest SE could be telling the truth...I have to debug a bunch of my projects and while I fix the error I was looking for...THAT fix sometimes brings other errors with it or now that the big error is no longer there I can finally see the other smaller errors that it was hiding.


Which is why it's a good idea to use the full maintenance window, and heck, maybe extend it, if they find other issues that are also causing people to not be able to play. Would you not think? I can't imagine any of my programming professors would have accepted a nonworking program on the excuse "Well i fixed one error! It just made more though."
#25 Aug 25 2013 at 10:32 AM Rating: Good
*
180 posts
zaarel wrote:
Phasmoto wrote:
crazy0taku wrote:
And to be honest SE could be telling the truth...I have to debug a bunch of my projects and while I fix the error I was looking for...THAT fix sometimes brings other errors with it or now that the big error is no longer there I can finally see the other smaller errors that it was hiding.



Exactly.


Imagine trying to debug something that thousands of people want it to be done NOW NOW NOW IN LESS THAN 2 SECONDS!

The pressure they must be feeling. Ugh.


Man if only they could have a period of time to test out the software and network in advance. That would surely be helpful and allow more time for debugging. A time for example where players logged in and played and reported bugs. A time when network traffic issues could be caught, fixed and planned for on release. A time when error 3102 could be caught and fixed, or at least the time to change the code name to 10102. If only........


The 3102 errors didn't happen in phase 3 only in phase 4 and it seems to have been fixed for EA. The duty finder problem wasn't there in phase 3 OR phase 4. You can only have so many beta tests and not everything is found in every beta. Why do you think so many MMO's still have so many maint and bug fixes AFTER launch. Please point me to the MMO that has never had a bug happen after launch.

Buffylvr wrote:
In their defense, and after nine years of ffxi, I'm not too interested in defending them: 3102 hasn't been much of an issue this first 30 hours.

It DOES appear they fixed that.


If they were running off the same engine as ffxi then there should be some concern but seeing how it is a completely different platform then anything they did prior can only be used in theory. Even when upgrading from previous versions of the same engine a lot of things can go wrong. I had a perfectly good program working and when I updated my IDE and engine to the newest version.....well lets say I had a lot of things that broke and had to do a multitude of fixes one after the other for all the new problems I kept finding.


I'm not trying to be a white knight or anything I just want to spread out some information. Just wish people would have a little bit more patience right now since everything that is happening is common for any MMO.

Edited, Aug 25th 2013 12:34pm by crazy0taku
#26 Aug 25 2013 at 5:18 PM Rating: Good
crazy0taku wrote:
zaarel wrote:
Phasmoto wrote:
crazy0taku wrote:
And to be honest SE could be telling the truth...I have to debug a bunch of my projects and while I fix the error I was looking for...THAT fix sometimes brings other errors with it or now that the big error is no longer there I can finally see the other smaller errors that it was hiding.



Exactly.


Imagine trying to debug something that thousands of people want it to be done NOW NOW NOW IN LESS THAN 2 SECONDS!

The pressure they must be feeling. Ugh.


Man if only they could have a period of time to test out the software and network in advance. That would surely be helpful and allow more time for debugging. A time for example where players logged in and played and reported bugs. A time when network traffic issues could be caught, fixed and planned for on release. A time when error 3102 could be caught and fixed, or at least the time to change the code name to 10102. If only........


The 3102 errors didn't happen in phase 3 only in phase 4 and it seems to have been fixed for EA. The duty finder problem wasn't there in phase 3 OR phase 4. You can only have so many beta tests and not everything is found in every beta. Why do you think so many MMO's still have so many maint and bug fixes AFTER launch. Please point me to the MMO that has never had a bug happen after launch.

Buffylvr wrote:
In their defense, and after nine years of ffxi, I'm not too interested in defending them: 3102 hasn't been much of an issue this first 30 hours.

It DOES appear they fixed that.


If they were running off the same engine as ffxi then there should be some concern but seeing how it is a completely different platform then anything they did prior can only be used in theory. Even when upgrading from previous versions of the same engine a lot of things can go wrong. I had a perfectly good program working and when I updated my IDE and engine to the newest version.....well lets say I had a lot of things that broke and had to do a multitude of fixes one after the other for all the new problems I kept finding.


I'm not trying to be a white knight or anything I just want to spread out some information. Just wish people would have a little bit more patience right now since everything that is happening is common for any MMO.

Edited, Aug 25th 2013 12:34pm by crazy0taku


You make some valid points. The fact most MMO's launch with bugs is 100% fact you speak. Having said that most of them launch with more than a few hours of uptime in the first two days. (there is your opening early access defenders). I really like the game. I would expect bugs for a month at least but NOT the complete inability to play 90% of the time.
« Previous 1 2
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 167 All times are in CST
Anonymous Guests (167)