Final Fantasy XIV: A Realm Reborn |OT2| Use a security token. Seriously.

Status
Not open for further replies.
30 ACN, 15 THM. The quest itself to become a Summoner is level 30 and appears after completing the level 30 class quest.

Cool. I'll start using guides etc. Sorry for all the questions.

You guys have been extremely helpful. On a more negative note, I just completed the mission where you kill the Rock giant thing (It's a level 10 story mission). During the cut scene where the masked Mage shows up - my computer crashed. The screen froze, and I had to turn off my PC.

I highly doubt I'll be able to log in now. I logged in very early this morning before the servers were swamped. So I'm probably out for tonight.

EDIT: It says I'm still logged into the game after I reboot my PC. =/ Yet I can't get back in. Now I have to wait for it to auto log me out. And I'm sure I won't be able to get in because the server traffic. I wish it would just let me back in, since I'm technically still logged in.

Double EDIT: Oh god. I just read that some people have been locked out for 20 + hours after they D/C from the game.
 
They're adding worlds. It's probably not going to affect your ability to log in on the one you're already on.

They're supposed to be addressing the duty finder though, right? I thought that was the reason they scaled back server slots to begin with.

If I can't access the NA/EU world is, is the problem on my side (and can be fixed by retrying) or theirs?

That's you, reboot the client.
 
Is it just me or are people staying logged in to the game?

Some people who are on my PSN list have been logged on for days and I refuse to believe that they've been playing for 40-60 hours straight.
 
Is it just me or are people staying logged in to the game?

Some people who are on my PSN list have been logged on for days and I refuse to believe that they've been playing for 40-60 hours straight.

Loads of people are staying logged in afk, to avoid the 1017 error.
 
Is it just me or are people staying logged in to the game?

Some people who are on my PSN list have been logged on for days and I refuse to believe that they've been playing for 40-60 hours straight.

There is no AFK kick so when people manage to get in, they stay in. Unlike idiots like me who log out on habit most of the time. =/
 
They're adding worlds. It's probably not going to affect your ability to log in on the one you're already on.

They're supposed to be addressing the duty finder though, right? I thought that was the reason they scaled back server slots to begin with.



That's you, reboot the client.

- Addition of new Worlds
- Implementation of countermeasures to handle the influx of concurrent user counts as a result of split processing the duty finder
- Address several known issues


It seems like whatever measures they used to run the duty finder, messed with the login servers and capacity in general.
 
That's so lame as Leviathan is constantly full and all of my friends are on there.

Certainly explains why I see so many people are just standing there doing nothing.

S-E needs to implement an AFK kick system, because it's unfair for people who want to play in my opinion.
 
Who else wants to bet that even if the server issues are fixed, they won't offer free server transfers and will charge a fee to transfer your toon(s)?
 
SE better prepare for the shit storm if tomorrows update does nothing to fix these problems. ffxiv 1.0 reborn.

For myself, this is SE's last chance. If the problems still persist by tomorrow, I'm requesting a chargeback on my card.

Pretty sure they've already set it up as a failure as IIRC they said they're going to be significantly limiting logins post update to observe behavior and then only slowing raising the cap from there. They've given themselves an excuse for a few days of 1017's.
 
- Addition of new Worlds
- Implementation of countermeasures to handle the influx of concurrent user counts as a result of split processing the duty finder
- Address several known issues


It seems like whatever measures they used to run the duty finder, messed with the login servers and capacity in general.

Alot of the game is instanced and there was only one duty finder server. The reason for the login cap now is to stabilize the instance server. What they are going to do is implement multiple instance servers similar to the WoW battlegroup setup.
 
There is no AFK kick so when people manage to get in, they stay in. Unlike idiots like me who log out on habit most of the time. =/

But there is a benefit if you actually log out in an inn, but most people probably don't want to do that at this time and just idle on the server so they don't have to try to log in.
 
But there is a benefit if you actually log out in an inn, but most people probably don't want to do that at this time and just idle on the server so they don't have to try to log in.

Same benefit as standing afk in an inn or sanctuary...don't have to be logged out.
 
I was getting that same issue but upgraded to the latest Nvidia beta drivers and it hasn't happened since. If you haven't tried the beta drivers yet I would give that a go.

Did, it and it's the same if not worse. Realized I had been running in Full Screen again for some reason, gonna kick it to FS windowed and see if that helps.

Also has anyone running the Nvidia audio through HDMI had problems where the sound screws up and pretty much makes it so the entire driver is toast for any audio at all? I've had that a bunch too.
 
- Addition of new Worlds
- Implementation of countermeasures to handle the influx of concurrent user counts as a result of split processing the duty finder
- Address several known issues


It seems like whatever measures they used to run the duty finder, messed with the login servers and capacity in general.

The measure they used to fix the duty finder was to limit logins. Hence the 1017 errors. The first day or so you could log in fine but the duty finder/instances weren't working.
 
Alot of the game is instanced and there was only one duty finder server. The reason for the login cap now is to stabilize the instance server. What they are going to do is implement multiple instance servers similar to the WoW battlegroup setup.

The measure they used to fix the duty finder was to limit logins. Hence the 1017 errors. The first day or so you could log in fine but the duty finder/instances weren't working.

Oh well in that case, everything should be good then.
 
Got there yesterday. 2 hours of fate farming can make one hate anything.

Yeah no kidding, FATE farming is a chore. I used to love that area until it felt like a grind. I'm glad I can move on to another area that I will get sick of.
 
I have such a MP problem with the Aiatar fight on my WHM :(
If the tank and dps are not on their A game I am running out of MP and even if they are it's hell trying not to run out with all the cures and spam heals..

I am guessing SCH has a much easier time during this fight? It's not so much the burst healing that is needed but a lot of MP if the group keeps dragging him through the poison pools.

Or maybe I just suck :(
There is not that much different one can do than cure cure cure and cure II if freecure procs and Esuna in between to cleanse the poison..right?

Late reply, but I suggest you don't cast Esuna in the fight unless the tank (or someone else) has the poison at 3 stacks (1 cure on someone that's just been target by a poison spit is enough to keep them safe, the poison won't kill them), stick to cure and only cast cure 2 from Freecure procs or if the tank likes to eat poison breath and is low on HP while a poison breath is coming.
Esuna will drain you for little return, since poison at 1 or 2 stacks isn't much damage and a Cure, which is less mana than Esuna, will keep the person safe and alive.
 
the story of our lives~
Xz6gie1.jpg
 
I'll bet your avatar transferring to the new worlds will be free.

I hope so. Ultros is cool and all but I'd rather play on server I can actually log in to whenever I feel like it. Even after these fixes I'm almost positive that Ultros will still have it's issues.
 
The measure they used to fix the duty finder was to limit logins. Hence the 1017 errors. The first day or so you could log in fine but the duty finder/instances weren't working.
Huh, that makes sense and is totally consistent with my experience at launch. Hope you're right.
 
You know truthfully I wish SQEX went the route to block IP access with the newer regional servers. Thats one thing that would have prevented the idiotic overpopulation.

Make region protected servers and have "international" ones for those who want to mix everything up countrywise.
 
You know truthfully I wish SQEX went the route to block IP access with the newer regional servers. Thats one thing that would have prevented the idiotic overpopulation.

Make region protected servers and have "international" ones for those who want to mix everything up countrywise.

I wish they had devoted more servers to each world servers, more servers for the duty finder, more world servers for the EU/NA people and split Data Centers for NA and EU.
 
in an unfortunate turn of events, I wasn't able to log in at all today. even after trying several hours, multiple times. a big sigh for now and i'll wake up early tomorrow to see if I can some game time in before they do any maintenance.
 
Status
Not open for further replies.
Top Bottom