Planetside

Planetside Dev Tracker




14 Mar

Comment

Looking into this now.


13 Mar

Comment

Originally posted by Arashmickey

However, for this morning's update, in order to keep downtime to a minimum, we did not restart one of the necessary central services. We felt that it was not required - we were wrong.

So... did you try turning it off and on again?

Technically speaking? Yes.

Then took the cartridge out, blew on the connectors and put it back in.

We also included a client change to fix the crash that I mentioned.

Comment

Adding to Andy's note: we setup an open thread on the forums for players/Outfits to report lost crafting progress (and associated resources):

https://forums.daybreakgames.com/ps2/index.php?threads/march-13-2020-escalation-hotfix-2-pc.253628/

We're particularly looking at the window between the two Hotfixes - the first at 6AM PDT, the second at 130PM PDT - as one of our worries was that resetting the service Andy referenced might cause Outfits who tried to re-craft Assets they had lost after the first Hotfix to lose progre...

Read more
Post

Hey everyone,

First, I want to apologize to our EU community, since this took place right in the middle of their prime-time. Please know that we try to avoid this at all costs, unless the severity warrants it. We will continue to avoid this going forward.

Changes included in the 130pm (Pacific) hotfix:

  • After the 6am hotfix this morning, all Bastion component progress prior to the servers coming down was lost, along with the associated resources. Expedition progress was also lost. More details below.
  • A medium-frequency client crash was fixed.

Of the two changes, the Bastion component crafting and Expedition progress loss were the reason we decided to perform an emergency hotfix at this time.

So how the hell did we miss such an obvious bug?

The way our live infrastructure is configured, each region utilizes dedicated hardware for the game servers. However, we have several "central" services that essentially st...

Read more External link β†’
Comment
    /u/Wrel on Reddit - Thread - Direct

Originally posted by Taltharius

If you happen to know of any footage we can look at, could you post a link?

Do you want me to record and post a video showing both the 'bugged' and 'unbugged' states that I described?

Just the method of getting into the bugged state that you described, and feel free to message me with it. We were able to repro the infinite critical chain bug, but it was done in a way that's very different from what's described here, so we want to make sure we catch all the edge cases.

Comment

I know - incredibly sh*tty timing. But its to address the issue that happened with the update this morning where Bastion components that were in progress were lost, along with the resources. This should be a relatively quick downtime.

Comment

Originally posted by SlightBlue

Your team is awesome, thanks for all the great work. Escalation is the most fun I've had in a videogame in years.

Thank you for the kind words!! That you’re enjoying the update is all we can ask for :)))

Post
    jgolenbo on Forums - Thread - Direct
[:content_encoded, :content, :description, :dc_description]
Comment
    /u/Wrel on Reddit - Thread - Direct

Originally posted by Taltharius

I've noticed that you can 'prevent' the Critical Chain duration bug by resupplying at an infantry terminal (somehow, it forces the duration to function normally).

Β 

However, the bug will still occur if you use the 'redeploy method' of class switching; redeploy, respawn as a different class, then redeploy again and respawn as an Infiltrator with a bolt-action and the implant equipped. If one remembers to never use infantry terminals, the duration is literally endless.

Β 

Would suggest that the devs check to see what exactly changes when you resupply at an infantry terminal, versus just using redeploy to respawn as a different class.

If you happen to know of any footage we can look at, could you post a link?

Comment
    /u/Wrel on Reddit - Thread - Direct

Originally posted by Strategyofthemind

Worth noting that most of these bugs aren't Escalation specific.

Should I bold the ones that are or separate the Escalation specific ones from the rest?.

While it's alright to keep up the reminders that these bugs exist, they're not what we're targeting when it comes to hotfixing.Hotfixes post update are about getting back to stability by remedying anything that was actually introduced with the update.

Game updates and interim updates are where we get the time to start working on some of these longer standing issues.

I'm just trying to keep track of all the bugs that people on reddit are mentioning and are talking about. So sometimes it's hard to tell if they think the bug was caused by Escalation or they are just finding it now because of looking for bugs related to Escalation or because they see a thread about bugs they post about any bugs they know regardless if it's relevant to the current upd...

We're prioritizing them internally, so it's not a huge issue either way. Mostly trying to set expectations for everyone about how this process works. The thread is much appreciated.

Comment
    /u/Wrel on Reddit - Thread - Direct

Originally posted by Strategyofthemind

/u/a_sites /u/jgolenbo /u/Wrel

Providing an updated list of all the bugs remaining and any new ones found. If there is anything else I can to do to help related to this, let me know.

Worth noting that most of these bugs aren't Escalation specific. While it's alright to keep up the reminders that these bugs exist, they're not what we're targeting when it comes to hotfixing.

Hotfixes post update are about getting back to stability by remedying anything that was actually introduced with the update.

Game updates and interim updates are where we get the time to start working on some of these longer standing issues.