PTRS Client-side hit
- Thread starter MrHello
- Start date
This is just a wild guess, but maybe the issue reported here has something to do with it. It was reported shortly before GOTY release and I can imagine that it would be a no go for AT rifles. Mekh will probably know the ins and outs of the decision to not implement client-side hit detection for AT rifles.
The root problem is that the armor penetration system is built in such a way that it has no clean entry point. It needs a fairly significant restructuring before it'll work nicely with client shots. It's a somewhat convoluted chunk of code, so it's a non-negligible amount of work to rebuild it while taking care not to break anything.
I didn't want to delay the release of my mutator just because of AT rifles, because, let's face it, AT rifles are a pretty minor part of gameplay. So, I let it go out with a half-baked workaround. I was planning to do it properly at a later date.
TWI apparently came to the same decision when they did their version
...but we knew this already. Thus, this thread.
I didn't want to delay the release of my mutator just because of AT rifles, because, let's face it, AT rifles are a pretty minor part of gameplay. So, I let it go out with a half-baked workaround. I was planning to do it properly at a later date.
TWI apparently came to the same decision when they did their version
...but we knew this already. Thus, this thread.
Yeah, I've always known of this problem. But it's only really started to bother me because of the new "bridges" custom map. Where the germans rely on the AT rifle against the russian tank. Why not have it both server-side and client-side, client-side for the infantry and server side for the tanks. As the tanks move less often so the effects of the server-side lag will be minimal compared to the effects against infantry.
I do hope that when they tidy up the issues with the AT rifles, (which I have had significant enjoyment using in the past)- They also enable Engineers & SL's the capability to supply ammo to them- or at the very least allow the AT to get a full load of ammo when lugging the leviathan to an ammodump, 3 is not enough.
Last edited:
it would be nice to be able to re-supply them! it's hard to get in a good spot to take a shot at that tank. having to run back for ammo usually reults in death, followed by more deaths, trying to get back where you need to be. anyone should be able to re-supply an at if he calls for it.
Maybe it's just me, but when using an AT rifle I need to lead moving targets more and often times the lead distances are inconsistent. The problem with this is that I expect the AT rifle to have the largest muzzle velocity of any of the small arms in the game. Upon checking wikipedia I can verify that I'm correct as the two other most common in game cartridges with the highest muzzle velocities, 7.62x54r and 8mm Mauser, are both roughly 200m/s slower than 14.5x114mm (the AT rifle cartridge.)
This means that unless 14.5x114mm experiences some insane drag then the AT rifles should require the least lead distance of any other gun in the game. Even when shooting stationary targets there is a longer delay before the target gets hit.
This means that unless 14.5x114mm experiences some insane drag then the AT rifles should require the least lead distance of any other gun in the game. Even when shooting stationary targets there is a longer delay before the target gets hit.
Client-side calculation is disabled on the PTRS. This makes it more difficult to hit personnel targets.
Both the things I've stated are facts. By saying "it works fine for me" is totally unhelpful because it is a fact that it does not have client-side calculation. Therefore it cannot "work fine" for you as that would insinuate that the "bug" is not existent or prevalent. You may not find the bug problematic, but it is still there 100%, whether it is problematic for you or not. Having graphic artifacts of map icons show up on the screen after closing the map is another bug; again, you may not find it problematic, but it is still a bug, and recently it was addressed. The fact that it does not bother you doesn't mean that it shouldn't be addressed.
It should be addressed.
This is exactly the issue we are discussing
By calculating ballistics server-side, the creation of the projectile after the client has fired is delayed entirely based on their ping; the higher the ping, the longer it will take the server to be told to create the projectile and send the information regarding it to your screen. If the client was the one calculating it, it would produce the most rapid and realistic feel, as the projectile would be leaving the barrel when you click to fire, not some measurable time after.
Last edited:
That's one possible work-around. It's still not ideal, though, because, given the sensitivity of the kill zones for AT rifle hits, precision does matter a fair bit even on tanks, especially if you're trying to hit someone unbuttoned while it's moving, which is technically a component of the tank rather than an infantry target.
