55 réponses à ce sujet

[Alfonsedode]

Heldarion wrote...
Crusader shoots where your reticle was 0.2s ago. Basically, you cannot switch between targets too quickly.

Ohh, it s not just a delay then... so you anticipate a bit where the head will be and don't move your aim for few tens of sec.

[Dabal Hayat]

Heldarion wrote...

Dabal Hayat wrote...

 Crusader X.

It's like the finger of a mean ol' drunk god: sometimes you can't hit a pretorian in front of you, sometimes you're achieving headshots from the other side of the map, outside the reticule's reach.
What can I say? I like the chaotic nature of the slug thrower.

Crusader shoots where your reticle was 0.2s ago. Basically, you cannot switch between targets too quickly.

I know, but I believe there is some kind of twisted romance when using the Crusader. I dunno really: husks autododge the slug while in my close proximity, while I'm behading everything that is outside the reach of the reticule with sniper precision: logic wise, it should be the damn opposite. But it isn't. It never is.
It's like when phantoms carthwheel the Claymores shoots, finding the exact frame where the bullets will not be... and in the meantime, you're killing the guardians behind her.


I love the Crusader... now if only it could shoot Thresher Maws, instead of slugs... A krogan can dream.

[LemurFromTheId]

Heldarion wrote...

Dabal Hayat wrote...

 Crusader X.

It's like the finger of a mean ol' drunk god: sometimes you can't hit a pretorian in front of you, sometimes you're achieving headshots from the other side of the map, outside the reticule's reach.{smilie}
What can I say? I like the chaotic nature of the slug thrower.

Crusader shoots where your reticle was 0.2s ago. Basically, you cannot switch between targets too quickly.

This is outdated information.

Crusader fires exactly where you point it, but there's a delay before the shot is processed by the game. Here's Dunvi's explanation:

Dunvi wrote...

Okay.

So most of the non-shotgun non-projectile (read: normal) weapons in the game are true hitscan. When the game registers a "fire" action, it immediately extrapolates the impact location, and then calls the appropriate bullet impact functionality at that location. Cool. Fun.

Shotguns are weird. Instead of doing the impact logic immediately and inline, it has it all factored out into a separate function. Where it would be in the other weapons, shotguns save your current aim values, and then set a timer, for a future time of the maximum of 0.001, and LatentFireDelay/#pellets.

Why it does this? We're not entirely sure. Seems to me that they're trying to simulate a slower projectile speed without using actual projectiles. But for all I know, maybe it's actually an optimization by introducing asynchronicity. I don't know, I was drunk last night, I didn't look quite closely enough to see if there was a reason for it. The important part is that value, LatentFireDelay. It's defined in the base shotgun class as 0.1.

At 60 fps with 8 pellets, 0.1/8 is still less than a single frame. At 30 fps, it's not even half a frame. And besides, since the pellets spread, the effects of the firing delay is mitigated obvious.

With the Crusader, they forgot about this weird, pellet-count based math. So you don't get your shot until at least 0.1 seconds later.

[soulriss]

I love scorpion

[Kirrahe Airlines CEO]

For the most part. Venom. Funny rag doll effects is always fun. When an enemy gets affected, they're flying coach on Kirrahe Airlines. *wink*

[Catastrophy]

My favourite weapons are still the characters, not the guns.