On 2012-12-19 23:10, Pantheon wrote:
There's always going to be latency involved.

Missiles travel at something like 40 gu/s, meaning if you have a seconds worth of lag, it's going to travel 40 gu before it shows up on your client, then another second for PD to react, etc...

99% of the time its an issue with latency, which is not something we can fix.

A scanner will make them show up like christmas tree lights though.

On 2012-12-22 17:27, Jim Starluck wrote:

Quote:

On 2012-12-19 23:10, Pantheon wrote: There's always going to be latency involved. Missiles travel at something like 40 gu/s, meaning if you have a seconds worth of lag, it's going to travel 40 gu before it shows up on your client, then another second for PD to react, etc... 99% of the time its an issue with latency, which is not something we can fix. A scanner will make them show up like christmas tree lights though.

Missiles are closer to an average of 100 gu/sec, actually. 120-ish for the fastest ones, 80-ish for the slowest. So 2-3 seconds of lag are long enough for a missile to scream right through your PD envelope.

On 2012-12-22 09:21, rykros1987 wrote:
If what pantheon I think said can be done... about removing the strength of the signal being based off of distance....and making it a flat amount. This might actually fix the problem. I noticed that a lot of the time the shrouds get detected right before they slam into your side and usually its too late by then. If the signal was made to be 100% at any distance it would probably reveal the shrouds earlier resulting in the shrouds still requiring escorts BUT it might fix the flakyness of the shrouds.

>.>

On 2012-12-21 11:41, Pantheon wrote:
If the damage isn't dealt on the server, the client will ultimately not receive any damage, but we have to interp for latency with everything, so if the client doesn't PD them for whatever reason due to their latency or a mixture of things - they will take damage on their client. However, the server controls when a ship is destroyed, not your client.

You could, in theory, hack the client to make everyone's hull read 0 hp or 0%, but only the server sends out the ship destroyed command. This is why it can sometimes seem like a ship is at 0% hull but won't die. Your client is interpreting what's going on, but due to the latency an entire salvo may have hit a new armor arc or one of many other scenarios.

On 2012-12-22 20:31, *Two Face* wrote:

Quote:

On 2012-12-22 17:27, Jim Starluck wrote: Quote: On 2012-12-19 23:10, Pantheon wrote: There's always going to be latency involved. Missiles travel at something like 40 gu/s, meaning if you have a seconds worth of lag, it's going to travel 40 gu before it shows up on your client, then another second for PD to react, etc... 99% of the time its an issue with latency, which is not something we can fix. A scanner will make them show up like christmas tree lights though. Missiles are closer to an average of 100 gu/sec, actually. 120-ish for the fastest ones, 80-ish for the slowest. So 2-3 seconds of lag are long enough for a missile to scream right through your PD envelope.

So the question everyone faction apart from Kluth wants to know is will it be fixed and if so please add it to the Development Log so its official.

On 2012-12-23 05:48, Mike Paradox wrote:
increase the signature of shroud missiles to -1.0. problem solved.

On 2012-12-23 06:59, Ubawaus wrote:
make shooting the missles a graphical effect only and let client decide that once missles are withing a pd range, they get shot in random order, in other words the client lets u render laser fire and renders the missle disappearing, with lag may not always go right, but on the dmg side the client alrdy decided they are shot, so therefor only the graphical effect on shooting the missles may go wrong

On 2012-12-22 21:47, Kenny_Naboo[+R] wrote:

Quote:

On 2012-12-22 09:21, rykros1987 wrote: If what pantheon I think said can be done... about removing the strength of the signal being based off of distance....and making it a flat amount. This might actually fix the problem. I noticed that a lot of the time the shrouds get detected right before they slam into your side and usually its too late by then. If the signal was made to be 100% at any distance it would probably reveal the shrouds earlier resulting in the shrouds still requiring escorts BUT it might fix the flakyness of the shrouds. >.>

You realize that this will affect your little bomber frigates and ECM scouts too? With this, Kluth dreads can simply choose the right moment to decloak next to those ships and instagib them just like snap.