The Issue With Convergence And Leading A Target
#1
Posted 30 June 2013 - 01:45 AM
#2
Posted 30 June 2013 - 01:55 AM
But it's not unpredictable or random. Shots don't go left or right for any other reason other than that you didn't lead the target the correct amount the weapon being fired.
Edited by Appogee, 30 June 2013 - 02:01 AM.
#3
Posted 30 June 2013 - 02:09 AM
Appogee, on 30 June 2013 - 01:55 AM, said:
But it's not unpredictable or random. Shots don't go left or right for any other reason other than that you didn't lead the target the correct amount the weapon being fired.
I believe he is talking about when you have a projectile weapon in the arm, and have your arm recticle infront of a moving mech. The game adjusts your arms aim for the range to the "terrain" the recticle is pointing at, not the range of the mech you have targetted / are firing at.
So this causes arm ballistics to not be so predictable in terms of lead amount. (The range of the terrain your aiming at will constantly change, sometimes drasticaly from 1200m to 500m back to 1200m) That coupled with the old firing delay and lag causing convergance to be delayed was why I never used to take PPCS or AC's on a dragons arm.
The torso slots never suffered from it, so I could always hit with them, but never the arms.
This , from what I remember was somewhat fixed when they removed the time to converge ??? At least, its less of a problem now anyway.
I haven't really noticed any problems with my flames arm PPCS for a while until recently. However thats caused by whatever is causing the major lag / sync issues atm.
Edited by Fooooo, 30 June 2013 - 02:15 AM.
#4
Posted 30 June 2013 - 02:16 AM
At 500 meters
Found your problem
#5
Posted 30 June 2013 - 02:49 AM
trollocaustic, on 30 June 2013 - 02:16 AM, said:
At 500 meters
Found your problem
even @ 300 i've watched twin 20's sail either side of a hunchback. it's not a huge issue when there's just 1 as you get used to it, but trying to get both arms on target is a pain.
Edit: mind you #ac/40problems
Edited by Ralgas, 30 June 2013 - 02:50 AM.
#6
Posted 30 June 2013 - 02:52 AM
Edited by XSerjo, 30 June 2013 - 02:52 AM.
#7
Posted 30 June 2013 - 03:47 AM
Fooooo, on 30 June 2013 - 02:09 AM, said:
Ah, makes sense, thanks. Perhaps this is why I sometimes miss with Gauss. (I thought it was just poor aiming on my part LOL.)
#8
Posted 30 June 2013 - 10:48 AM
#9
Posted 30 June 2013 - 11:20 AM
Quote
PPC's don't require leading?
Have you ever actually fired PPC's yourself, or are you basing your opinion on the fact that other people shoot you with them?
Because they do in fact require you to lead a target if it's moving.
#10
Posted 30 June 2013 - 11:42 AM
#11
Posted 30 June 2013 - 11:46 AM
JimboFBX, on 30 June 2013 - 11:42 AM, said:
1) There is no longer a firing delay at all, so you are mistaken there. This would suggest that you have not used PPCs since HSR was put in. The firing delay was an artifact of the netcode requiring a server side authentication to fire, which was effectively removed once HSR was introduced.
2) At 2km/sec, this requires a lead of multiple body lengths against fast moving mechs at 1k. This is easily enough to result in the issue that you bring up, which is that the weapons will converge on the location of the reticle, rather than the location of the mech. That is, you can't put your reticle on a mech that is moving, fire, and expect to hit it.
#12
Posted 01 July 2013 - 11:02 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users