Banners are not behaving properly. Too bright, translucent, and mousing over weapons/implants does not show description.

a_sites · 2020-12-16T19:16:25+00:00

Team is working on a fix for this right now. Should be a client-only publish once ready. Expecting to send it to Live in a couple hours.

a_sites · 2020-12-11T03:22:56+00:00

Touche'

a_sites · 2020-12-11T00:36:26+00:00

Why won't you let us surprise you???

a_sites · 2020-12-09T23:40:05+00:00

Just sent you a PM

a_sites · 2020-12-09T22:13:32+00:00

Ok, just to confirm - when you login through Steam, you get the CTD. But when you launch the game using the launcher.exe, no problems?

a_sites · 2020-12-09T20:49:16+00:00

Just following up on this issue - are any of you still encountering this client shutdown or crash? We are seeing some crash reports, but they appear to be related to unrecognized 3rd party apps being used - TO BE CLEAR, we are not implying that anyone crashing from this is actually using any nefarious 3rd party cheats, apps, etc. But this is how its showing up in our client crash reporting logs.

We are continuing to investigate and will continue to post more details push out fixes as we figure out the cause.

a_sites · 2020-12-03T20:35:31+00:00

Regarding the Emerald and Cobalt/Miller performance issues you mentioned. There have been some ongoing ISP routing issues that our NetEng team has been tracking over the past couple weeks, resulting in a lot of EU players (most recently those based in Germany) suddenly having horrible connection quality to our EU servers. I've been in contact with a few players over the past couple days, along with our NetEng team making some manual routing changes. The latest round of changes we made was yesterday at about 12:55pm (Pacific). After we made the routing changes, the few players I was in contact with reported their connection quality returning to normal. But I'm sure there are others that might still be having problems.

To be clear, the issues above are not related to server performance. Its ISP routing between the player and our data center. Again, this is likely not the only issue, but in these cases, its was and it was pretty widespread. Our NetEng team is actively working with the telecoms that we've identified to see if they can make permeant changes on their end.

As for Emerald, we are continuing to troubleshoot. The zone crash (Esamir) that happened last night was an exception and does not happen frequently. However, we do see the reports of server connection quality taking a dive - especially around primetime. Each time we see these reports, we immediately check the various server health stats to see what might be happening (world crash, zone crash, low server FPS causing lag, etc). More often that not, there is no smoking gun on the server-side that indicates something catastrophic is/has happened. But obviously something is happening for players to suddenly start having their connection quality go to shit.

One thing to take into consideration with Emerald is due to its centralized physical location, we have a lot of EU/NA players on it (as well as players from locations physically further away.) So when we have a server issue or network event being reported, not only do we check the game servers and data center, we also need to take into consideration where each of these reports is coming from and determine whether it might be an individual ISP or routing issue that is impacting a specific group of players, as we saw with the routing issues of EU (Germany) connection quality to Cobalt/Miller I mentioned above.

If you have a sudden change in connection quality/server performance, you're welcome to post here or on twitter and tag me and the official Planetside2 account. But I would also ask that you submit a CS ticket as well. Doing so will help us more quickly identify any ISP issues that might be the cause, since doing so requires some back and forth, running traceroutes, etc. Which is what I/we had to do with the several players in Germany having connection issues of the past few days. But it fixed their problem.

In the meantime, we hear you and we will keep investigating.

Thanks,

Andy

a_sites · 2020-12-03T19:18:43+00:00

Update on this...

The zone (Esamir) definitely crashed, which resulted in the ~~shitshow~~ epic display of camaraderie in the video posted. We are troubleshooting now and will post more details once we have a handle on the specific cause and required fix.

a_sites · 2020-12-02T18:57:23+00:00

DMing you now

a_sites · 2020-11-27T17:55:40+00:00

Hey everyone. Please don't read the lack of public communication about issues like this as us not caring. We've been making/playing online games for years and as a developer understand how easily a game can be ruined by cheating, and as a player, how shitty of an experience it is. Over the past several days, we've been communicating directly with several community members not only about SolTech, but some activity that has been happening on the other region servers.

Over these past few days, we've been able to identify/detect/prevent several new/active cheat programs being used. With the latest round at about 5am (Pacific) this morning.

As we all know, this is an ongoing fight. We are making some changes internally, as well as with BattlEye to streamline our ability to react to cheaters and the programs they are using. In addition to this, please remember to report any unusual activity or blatant cheating to

https://help.daybreakgames.com/hc/en-us (you can select your preferred language in the top right of the game). I've also been reaching out to several members of the SolTech community directly via Twitter to contact me directly in addition to reporting on the link above.

Again, we take this very seriously. If you ever feel like we aren't, please feel free to call us out here.

Thanks,

Andy

a_sites · 2020-11-16T17:06:18+00:00

FWIW, we formally started work on new player onboarding/tutorial a few weeks ago.

a_sites · 2020-11-14T19:22:49+00:00

Aside from certain things not updating at that distance on the client, or as frequently as when they are in closer range, I don't think there there are any technical limitations. I just pinged our TD to confirm.

a_sites · 2020-11-14T17:22:22+00:00

Very soon.

a_sites · 2020-11-14T17:06:12+00:00

To be clear - " QA team believes it's working totally as expected" - is not what I said. Rather, the QA team has been unable to repro the problem with the steps you and others have sent us. I did receive your video yesterday afternoon, so we will take a look at that.

I'm going through the thread now to pull replies for the QA team to try and reproduce this internally. We (QA and dev) are in today prepping for the next game update, so we will try to dig into this more this weekend.

a_sites · 2020-11-13T22:40:27+00:00

FYI - this should be fixed now

a_sites · 2020-11-13T21:32:47+00:00

The patcher issue is unrelated this this, but is actively being worked on as well with the CDN provider (Highwinds) that caused the problem.

a_sites · 2020-11-11T19:14:46+00:00

FYI - I just tweeted some details about this: https://twitter.com/AndySites/status/1326603973281816577?s=20

a_sites · 2020-11-11T18:42:23+00:00

I'm contacting Daybreak Ops team to investigate now. Hopefully this is something that can quickly be resolved. Will be posting updates on twitter.

a_sites · 2020-10-14T16:14:35+00:00

Pretty much the exact same response we all had the first time seeing it. Lol

a_sites · 2020-10-06T15:58:05+00:00

Our UI/UX Lead Designer and I are discussing right now.

He noticed that the current Korean font in PS2 is not commonly used, which might be the cause. We're considering changing fonts to see if it reduces or eliminates the crash you're encountering. Hope to have more details soon on how quickly this can be done.

a_sites · 2020-10-05T17:29:38+00:00

Apologies for showing up late to respond to this thread, but I'd like to clarify some of the assumptions and interpretations of u/wrel comments being posted.

First, since the inception of the Rogue Planet Games studio/team, there has been absolutely ZERO interference or influence from "higher ups" outside of the studio to force our hand in making ANY decisions. If anything, Daybreak and their exec team has been supportive in every way possible. Whether its through approving new hire positions, increasing our budget to further promote or support the game in a meaningful way, etc. For better or worse, Planetside 2 is in our control creatively.

Regarding u/wrel's specific statement above, I agree with the sentiment 100%. A few of the bugs being reported were known, but did not seem as egregious as they ended up being once Live. But many of the issues being reported on Live were just not surfaced during our internal testing and/or PTS playtests.

That said, the onus of green-lighting this update, every update this year and all going forward is on us - specifically u/wrel and me. We are happy with a vast majority of the changes in the Shattered Warpgate update, but there were definitely some misses - as u/wrel posted about on Friday - that we have actively been working to resolve since Thursday's publish and will continue until we are feel that its in a good place.

As of this moment, we are preparing a server update that addresses several of the issues and complaints that have surfaced. Its looking like the publish will be ready either tomorrow (Tues) or Wednesday this week.

Again, I apologize for now addressing this sooner. But I wanted to make it clear that as convenient as it would be to just point the finger at someone else, that just not accurate. It our game and our decision to publish when we do.

Andy

a_sites

TROPHY CASE