Firefall Post Update 6.0

by **GettinCocky** Sun Mar 24, 2013 11:08 am

For any of you whom have not updated Firefall and tried to play it since the new patch has come out, you'll be glad to know that you really haven't missed much. There were some glitches on the first day after the patch, but you were ultimately able to play for a few hours. Although, Firefall has had several massive server-wide issues ("Awaiting connection" screen lockups, unable to exit the new tutorial, laggy gameplay, etc). Currently Red5 has said that they are having issues with their character database, and have not given a timeline. Red5 has been working on this problem since 1 pm PST yesterday (3/23) and there still is no solution available.

Here's some posts from Red5:

Thundercleese said:

↑

Hey guys, just a quick note. We're still working on the problem, we've not gone home yet.

If you could please *DO NOT TRY TO LOG IN*.
It is hampering our ability to necessary database work. I'll ask
Grummz, if I can, to modify his earlier post to reflect our current
repair needs.

Thank you for your understanding and we'll have the game back up as soon as we can.

Phobos said:

↑

Hey guys,

As many of you know, the majority of the community team is at PAX right
now. I have seen a lot of people concerned that there is a lack of
communication about the specifics of the issues that are currently
affecting the game. First, I want to clarify a few of things...

1) Not a single person from Red 5 who could help fix this problem faster
is at PAX right now. We are community, marketing, along with Scott and
Mark. If I could hop in and help program or manage the database, I'd be
back on a plane in a heart beat.

2) Everyone that can work on this issue, is working on this issue. The team has been working countless hours since the patch was released to get everything working.

3) The patch did come out right before PAX, but this was not some sort
of conspiracy or any drama or pressure. We wanted to show off new stuff
to press. Guess what? Didn't work out so well. Things happen that you
can not plan for and we pushed it right to the wire. If we could have
stabilized the build earlier, we would have, but this is a massive
undertaking and things came in very hot. Lessons learned and I assure
you that it will take a LOT for that decision to be made again.

Now. The concerns about communication are valid, but the requests are a
bit extreme. At this point in the troubleshooting timeline, there are no
ETAs or details that I can share. Even if I were right next to the guys
as they worked, I would not want to be bugging them for updates as they
need to focus on their tasks and actually push things forward.

I think we've already proven time and time again that we are more than
happy to communicate about our failures, why they happened, and what
we're doing to fix them. At this point in time, everyone just needs to
sit back and relax for a bit and let the people that know what they're
doing fix the problem because I guarantee you that no one at Red 5 is
relaxing right now. There is a lot of work to be done, let's all put our
support behind the guys that are forgoing food, sleep, and their
families to get this resolved all so we can play a game.

Forum Posts dealing with this issue: