17 replies to this topic

[DeadlyNerd]

Honestly, I'm so ******* happy I'm actually going to commend PGI on their work this patch.

But I digress, when's ECM gettin fixed?

[XSive Death]

Or the chat bug...how hard is it to make backspace work?

[Shumabot]

You're thanking them for unbreaking something they broke? Beaten housewife much?

[DeadlyNerd]

With how many things they broke and how long they've been broken, they can only unbreak things and frankly I was waiting for this fix a long time.

It could'v been a lot worse, they could'v left it and the whole state rewind for ballistics would've been pointless.

[Shumabot]

DeadlyNerd, on 16 April 2013 - 01:19 PM, said:

With how many things they broke and how long they've been broken, they can only unbreak things and frankly I was waiting for this fix a long time.

It could'v been a lot worse, they could'v left it and the whole state rewind for ballistics would've been pointless.

They could have fixed it alongside every AMD card causing the screen to explode into polygons. I'm wary of their "fixes".

[FrDrake]

Shumabot, on 16 April 2013 - 01:23 PM, said:

They could have fixed it alongside every AMD card causing the screen to explode into polygons. I'm wary of their "fixes".

I run an Nvidia and the last patch I ONLY had the polygon bug, only a single hud bug out of around 50 games, but the polygon bug like 1 out of 4.

[Gristle]

Shumabot, on 16 April 2013 - 01:23 PM, said:

They could have fixed it alongside every AMD card causing the screen to explode into polygons. I'm wary of their "fixes".

I have an AMD card and have yet to see the polygon bug.. Granted I haven't been playing very much over the last 2 weeks though.

[Tie Ma]

havent noticed too much guess i got used to the old delay

[Ranek Blackstone]

DeadlyNerd, on 16 April 2013 - 01:19 PM, said:

With how many things they broke and how long they've been broken, they can only unbreak things and frankly I was waiting for this fix a long time.

It could'v been a lot worse, they could'v left it and the whole state rewind for ballistics would've been pointless.

AC fire delay was always lag induced. Server had to verify you could legally fire an AC (weapon had properly cycled on the server's internal timer) before you actually shot the darn thing.

Edited by Ranek Blackstone, 16 April 2013 - 01:28 PM.

[Scromboid]

Is this fixed for the gauss, too? You mean I can fire my weapon faster than missiles with a closed bay door?

[OpCentar]

4x (or more) AC/2s are very formidable now.

Before I had random delays between firing, now it's just point and watch the beautiful dakka strip that CT armor in just a few seconds

[DeadlyNerd]

Ranek Blackstone, on 16 April 2013 - 01:28 PM, said:

AC fire delay was always lag induced. Server had to verify you could legally fire an AC (weapon had properly cycled on the server's internal timer) before you actually shot the darn thing.

Yes I know that, duh.

Another usually used term for fixing a bug is "removing" it.

Edited by DeadlyNerd, 16 April 2013 - 02:01 PM.

[TheGreatNoNo]

Might get a Pract 4X for giggles now.

[Bagheera]

XSive Death, on 16 April 2013 - 01:09 PM, said:

Or the chat bug...how hard is it to make backspace work?

Fun Fact. Backspace bug also affects the login text boxes.

[Hobietime]

DeadlyNerd, on 16 April 2013 - 01:19 PM, said:

With how many things they broke and how long they've been broken, they can only unbreak things and frankly I was waiting for this fix a long time.

It could've been a lot worse, they could've left it and the whole state rewind for ballistics would've been pointless.

HSR is the reason why there is no longer a delay. Previously, your client had to send the fire command to the server, then the server had to send back an acknowledgement. Ever notice how your reticle would turn red at the same time your weapon finally fired on your client? That's why even when it did fire it didn't match up with when it fired on the server.

Now, with HSR, your weapon can fire immediately and when the server does receive the fire command it rewind so that it can simulate the shot the same way it was simulated on your client.

Hobie

[DeadlyNerd]

Hobietime, on 16 April 2013 - 02:18 PM, said:

HSR is the reason why there is no longer a delay. Previously, your client had to send the fire command to the server, then the server had to send back an acknowledgement. Ever notice how your reticle would turn red at the same time your weapon finally fired on your client? That's why even when it did fire it didn't match up with when it fired on the server.

Now, with HSR, your weapon can fire immediately and when the server does receive the fire command it rewind so that it can simulate the shot the same way it was simulated on your client.

Hobie

Don't sign your forum posts, we can already see your name in the reply.

On a related note, no state rewind does not have to cover this delay. It can still simply use the moment the server authorized the shot as the moment the shot was made. You're not looking any smarter by attempting to assume, carry on.

[KingDerp]

"official" ??

LOL...

[Hobietime]

Quote

On a related note, no state rewind does not have to cover this delay. It can still simply use the moment the server authorized the shot as the moment the shot was made. You're not looking any smarter by attempting to assume, carry on.

I thought I read that the server authentication was the reason for the firing delay in post the developers made, but I have no proof.

Sorry I acted a bit condescending, it was misplaced. I was typing this right after I read a response from my boss who obviously didn't read my original email. He then proceeded to ask me the very same questions I answered in the email.

Either way, I'm just happy there isn't a delay any more.

I really can't help the signature thing though.

Old habits are hard to break.

Hobie

Edited by Hobietime, 16 April 2013 - 02:51 PM.