It just seems to me that half the time my rounds are firing too far off my crosshairs. Is there a camera or attachment issue? The problem is really exacerbated when I'm standing next to geometry. I'm also noticing this when perfectly still.
1
Ballistic Aiming Seems To Be Off
Started by vifoxe, Nov 16 2012 07:52 PM
5 replies to this topic
#2
-
-
- Veteran Founder
- 2,235 posts
Member
- LocationOrlando
Posted 17 November 2012 - 12:39 AM
Sometimes the convergence can get a little messed up if your shooting at something really close or if your standing next to a wall or something, though this is only for arm mounted ballistics I think. I don't think torso mounted weapons have convergence...
#3
-
-
- Bridesmaid
- 3,395 posts
Snowflake
- Location輝針城
Posted 17 November 2012 - 01:35 AM
Torso mounted weapons also have convergence, how much depends on where the barrel is. Gausscats are accurate as they are because the side torsos are very close together - the Hunchback, on the other hand, faces convergence issues.
The weapon fires such as to hit the distance the crosshair is aiming at. This has three problems. Firstly, you often need to lead the target so that the slow moving projectile can hit. This is impaired by the fact that your reticle is aiming at the floor, and tries to converge at the floor, not at your target distance. So if the floor is 400m away, your AC/20 is on the left side and you're aiming to the right of a user, the AC/20 will fire more to the left than you would expect.
Secondly, the polygons aren't properly programmed for convergence detection. A cliff or tree NEAR your reticle, even if it's not ON the reticle itself, may cause the weapon to fire at its distance, causing it to miss towards the object.
Lastly, the weapons fire is determined not by where you think you are, but by where the server thinks you are. If you run a Cicada with AC/2 at very high speeds, but have a latency of 280ms, then your shots will all fire towards where you would have fired if you aimed at that spot 0.56 seconds ago, which may lead to some rather exaggerated misses.
The weapon fires such as to hit the distance the crosshair is aiming at. This has three problems. Firstly, you often need to lead the target so that the slow moving projectile can hit. This is impaired by the fact that your reticle is aiming at the floor, and tries to converge at the floor, not at your target distance. So if the floor is 400m away, your AC/20 is on the left side and you're aiming to the right of a user, the AC/20 will fire more to the left than you would expect.
Secondly, the polygons aren't properly programmed for convergence detection. A cliff or tree NEAR your reticle, even if it's not ON the reticle itself, may cause the weapon to fire at its distance, causing it to miss towards the object.
Lastly, the weapons fire is determined not by where you think you are, but by where the server thinks you are. If you run a Cicada with AC/2 at very high speeds, but have a latency of 280ms, then your shots will all fire towards where you would have fired if you aimed at that spot 0.56 seconds ago, which may lead to some rather exaggerated misses.
#4
-
-
- 101 posts
Member
Posted 17 November 2012 - 08:24 AM
That might have been it. I was having trouble leading targets with my HBK-4H. I normally don't have trouble leading my shots, the rounds just kept going off my crosshair.
#6
-
-
- Knight Errant
- 37 posts
Member
- LocationCanis Major
Posted 18 November 2012 - 03:45 PM
I ve had this same problem.I have an AC5 mounted on the torso of a catapult.When I fire,the slug dosent go where Im pointing the target reticle,and the shot usually misses the target by about 5 ft.(Even if the target is not moving).I didnt have this problem before, and it seems to be recent.
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users
