Funny isn't it, that the console scrubs defending the lolcrusader are only able to hit things which are...
a) standing still
staggered
Console players aim REALLY SLOWLY, and probably don't really know how frustrating it is to have a gun that fires 0.2 seconds behind where you're aiming quickly. The crusader is great if you want to play like a console player and take 0.5 seconds (or more) to line up each shot. Not so great if you like to switch quickly between targets or hit things which are moving.
Twitch shot? MISS
Tracking a moving target? MISS
The problem is, having a gun shoot at the spot your crosshair was 0.02 seconds ago is stupidlly frustrating. There's no projectile, so you can't predict a trajectory, you just have to be blindly lucky to hit something moving perpendicular to you.
It's like the reverse of a projectile weapon; no visual queue, and instead of predicting a trajectory, you have to be targeting 0.2 seconds "ahead" when you pull the trigger....
Cyonan wrote...
MaxShine wrote...
UnknownMercenary wrote...
MaxShine wrote...
Without
the delay it would be overpowered... Sniper rifle range, great ROF,
innate piercing. Playing with it is like classic online FPS gaming was
in Q3A or UT, you have some lag on your shot... So what? Consider
yourself happy to get a taste of these classics
I can't think of any gun in those games that purposely had a 0.2 second delay
MAYBE the railgun?
actually I don't think that had it
I
meant that if you played Q3A online, you would have to lead your
railgun shot because there was no lag compensation in these games. In
today's shooters you can aim right at the target. The Crusader firing
delay feels like playing with a bit of lag in these classis games.
So we should be happy that the Crusader includes the worst part of old school FPS gaming?
Seems legit.
Maxshine misunderstands the bug regarding the crusader.
Old school projectile weapon:
Press fire
Signal is sent to host / server
Gun fires
Projectile paths
Projectile then hits anything which it passes through
The crusader, is a different kettle of fish.
Press Fire
Shot fires instantly
Shot does not fire where your crosshair is indicating
There's a huge difference between a 60ms delay on your RG / SR in Q3 / UT (in which case if you twitched to the right location it would still hit) and having the gun purposefully fire 0.02 second behind, and NOT hit where your crosshair currently is.
That'd be like firing your flak cannon and having it shoot 0.02 seconds back from when you pressed the trigger... latency doesn't factor into it.
Old school shooters used aiming by visual; a key concept for projectile weapons. If you can't SEE the projectile, you can't really guage speed, distance, time, elevation, gravity, etc. The crusader cannot be aimed visually as it's a hit scan weapon, except it hit scans to the location your trigger was 0.2 seconds ago.
If my crosshair is at point A in unreal tournament and I fire my flak cannon, then after 60ms (latency) the flak fires, but it still hits the spot that I fired at... the crusader, regardless of latency fires 2 seconds back the way.
Modifié par Annomander, 25 mai 2013 - 10:32 .
Retour en haut
