2 réponses à ce sujet

[Cyonan]

I posted this in the threat about the Crusader being hit scan, but I'll give it its' own thread so that more people see it. Hopefully Bioware can add it to the list =P

We've known for a while that the Crusader's aiming is really weird, and a lot of people seem to think that it's firing blanks like the Falcon used to. Only the Crusader is a hitscan weapon and doesn't use projectiles. It can't fire blanks.

The Crusader has a weird mechanic(or bug) where the bullet it fires doesn't hit where the crosshair is, but rather it hits where it used to be(hard to get accurate readings, but it's where you were aiming roughly 0.15-0.2 seconds before firing), which leads to every shot where you're moving the crosshair around being slightly off. You can have your crosshairs clearly over a target's head and completely miss it because it wasn't there 0.2 seconds ago. You can also get headshots on a target you aren't aiming at anymore because you were aiming at it 0.2 seconds ago.

Nothing seems to affect how much or how little the bullet is off. I've tried using accuracy, stability, and hipfiring vs zooming in, and it's always off by the same amount. Hosting does nothing to prevent this from happening, either. The only way to get a 100% accurate shot is to not move your crosshair for half a second.

The Crusader itself is actually very good when it works, but it isn't going to matter how powerful it is if the bullets aren't landing where you're aiming, unless you're shooting at an Atlas sized enemy where it just doesn't matter because you'll hit it anyway.

[Kristen Schanche]

Hey folks,

I had a look at this issue, and here's what is happening with the Crusader. This gun does have a very small delay between when the trigger is pulled, and when the shot is fired, however, the shot goes to the point that the crosshair was on when the trigger was pulled.

Basically, crosshair is at point X, the player pulls the trigger and simultaneously begins moving the crosshair to point Y, reaching it approximately 0.02 seconds later. The shot now goes off, even though the user is now pointing at point Y, the shot still hits the point it was aiming at when the trigger is pulled, point X.

The long and short of this however is, while this does slightly change the presentation feel of the gun, the bullet for the crusader still hits the point you were aimed at when you pull the trigger, meaning it remains as accurate and without delay in actual ability to hit targets as any pistol, sniper rifle, etc.

As long is the trigger is pulled when your crosshair is on the target, regardless of the delay you will hit a still target.

This does mean that yes, a small bit of lead should be considered if trying to hit a rapidly moving target, but the delay is small enough that most enemies outside of a few like the Nemesis will not be able to get out of the impact point in time.

Let me know if you have any more questions on this issue, but hopefully this clears up the way the gun is acting a bit.

Modifié par Chris Schanche, 26 septembre 2012 - 05:17 .

[Kristen Schanche]

No problem. In response to the questions that have come up, this behavior is fairly unique the the Crusader. Other shotguns do have a minor though less noticeable delay, but the Crusader is the most visible of the guns with a behavior like this.

I will have a look at your concern Najarati, and see what I can turn up.