Whenever I start a match using TV Guided weapons the aimpoint starts fixated on the ground like its been locked and when I get to where I need it the aimpoint is down in either the bottom right or bottom left corner and I’m unable to get it back to center.
Any idea what the problem is? I’ve completely reset my controls and started over and it continues to do it.
It doesn’t do it on the TPOD, just the TV and the Mavs.
Any help would be apopreciated.
Gaijin made a change to the seeker eye stabilization of AGMs a few patches ago that made them permanently stick to the last sensor Point Of Interest (POI) while in the seeker scope. Even some of the targeting pods are affected by that change, and they have done little to fix it despite community response.
The best thing to do for now is either use the map designation to key the seeker eye to that point or direct the center pipper of your aircraft’s HUD to the point you want the AGM to look at and hit your sight stabilization key before switching to the AGM scope.
Thanks for the response.
Since posting this I discovered the site stabilization key. Some aircraft it works, some it doesn’t. The one I’m having the most trouble with is the F-5E.
That being said I didn’t know that the map designation existed. Does it give you anything visually in the cockpit? For example does it designate the target for CCIP/CCRP in older aircraft?
In other words will you see your target designated from the cockpit, in some of the older jets, say the F-4S for example??
It seems you just have to press the “Weapon lock (air-to-ground)” key while in your regular cockpit view pointing the crosshair (or nose of your aircraft) where you want to turn the TV camera. Then wait for a bit until it says “tracking” at the bottom and you’re all set - you can now switch to the TV view, adjust where it points to (you have to press the “Weapon lock” key once more to unlock and then again when set) and fire.
Tested on the F4-E and F5-E in the test flight and both works fine.
I actually hadn’t known all this either and thought the whole time since the aforementioned patch that the whole thing was broken, too. So big “thank you” to @White_Timberwolf for sharing this intel.