At 60 fps, we have this:
http://asecretsnotas....imgur.com/all/
Go to the album, click on the first image (bottom) and flip through the images to see the frame by frame analysis.
By our reckoning, the bullet hits where the cursor was approximately 6-7 frames before firing. Flip through the pictures to see what you think.
This delay was actually inconsistent. On other shots, we found the delay to be between 6-12 frames (between 100 and 200 ms) These are not all documented, as Lord_Sirian is not willing to take hundreds of screenshots (and really, can you blame him?)
At 30 fps, we have this:
Frame 1
Frame 2
Frame 3
Frame 1 is 2 frames before the trigger pull, frame 2 is the trigger pull frame, and frame 3 is where the bullet actually hits.
The delay in these tests ranged for 1-2 frames, or 33.333 to 66.666 ms. This is consistent with MaxShine's test.
In conclusion, the Crusader aim delay is highly dependent on frame rate, and inconsistent. It is significantly worse at 60 fps. It ranges from 100 to 200 ms at 60 fps, and between 33.333 and 66.666 ms at 30 fps.
MaxShine did some testing here, which was very valuable
Also, note that none of this matches the reported .02 second delay reported by Bioware. Biower pls
Addendum:
The hit delay does also happen on other hitscan weapons, though inconsistently. So far, we've seen a similar 1 frame delay between the Talon firing and the bullets registering. However, the ammo counter didn't update until well after the bullets hit (6 frames after the shot), whereas the Crusader ammo counter updated before the shot. The Wraith seemed to register hits instantly.
Modifié par tyhw, 27 mai 2013 - 10:40 .
Retour en haut
