Flight Time Update

"We are proceeding with a full global server re-deploy as part of this fix, which will take time. As soon as we get USWest online we can start prelim testing there in parallel. Team is working nonstop, as fast as they can. Our “afternoon” PT target is pushing into “evening.”
via Brian Jerrard twitter

Well there goes my chance to play it lmao

Well, maybe they’ll extend into when they close it.

> 2533274870039325;3:
> Well, maybe they’ll extend into when they close it.

That will probably depend on whether they are able to get all of the data they need. If they don’t get enough data they will surely extend it, but if they have everything that they need, it makes more sense for them to close it at the scheduled time so they can focus on analyzing and getting ready for the next flight.

> 2533274961385664;1:
> "We are proceeding with a full global server re-deploy as part of this fix, which will take time. As soon as we get USWest online we can start prelim testing there in parallel. Team is working nonstop, as fast as they can. Our “afternoon” PT target is pushing into “evening.”
> via Brian Jerrard twitter

Is it too late to write a script… sending info to and fro between servers… in a continuous loop… with a time cut off

T = current time
If current time + 1 min < current time
(Send 120 fps + op system background noise) × number of clients on server × 120%

Stress test example…
Step 2 - clear server 1
Step 3 - clear additional servers

Just crossed 4pm here in Washington state in the PST. Whenever it happens those bots have no chance!!!

Its understandable, I’m sure its no easy feat to push something out like this.