NoJoy Posted Wednesday at 12:30 PM Posted Wednesday at 12:30 PM I don't know when this has changed as I really was tied to the Hornet for quite a while... I'm really having such a hard time getting a lock with the Mavericks. I don't consider this as a bug - more as a 'it is what it is now'. Tried everything out like changing contrast, brightness, different types of the Mav, different terrain like Caucasus or PG, etc. Thing is it does work sometimes but really only sometimes. It's not like it was, spot a target, get your seeker on it and splash. This may have been too easy compared to real life but as it is right now I'm really struggling with the use of Mavericks. Espacially when you have to be quick taking down a SAM or something that is angry at you. I know the question for a track will come up and I don't have one. I don't bring this up as bug yet. And it will be a lot of tracks as there are many different conditions to take into account... Maybe you guys share some experiences and procedures that can help? Brrrrrrrrrrrt I'd rather call in a Strike Eagle... I7 6700K, MSI Z270 Gaming Pro Carbon, 32GB G.Skill Ripjaw V 3200, Inno3D GTX 1080, Samsung 970 Evo, Thrustmaster 1.6000M, TrackIr 5
Yurgon Posted Wednesday at 12:59 PM Posted Wednesday at 12:59 PM (edited) 3 hours ago, NoJoy said: I know the question for a track will come up Haha yes 100% Well I've been flying the Hog in my squad for 9 years (and in single player since it came out) and can't say I see any major difference in the way Mavericks do or don't track objects, and also haven't heard questions or complaints from the squad mates who also have extensive experience in the A-10C and A-10C II modules, nor am I aware of other Hog-communities facing such issues. In fact I'd say that somewhere down the line the CCD seeker H and K model Mavs started tracking at much better ranges. They used to track reliably at maybe 4 or 5 miles, sometimes as low as 3, and nowadays I see no noticeable difference between the IR and CCD seekers. They track pretty reliably at 7 miles and often times as far out as 9 miles. So if your experience differs from that significantly, a fixed set of parameters would be needed to pinpoint the issue - and the easiest way to achieve that is a track. Edited Wednesday at 04:04 PM by Yurgon Typo 1
Ivandrov Posted Wednesday at 03:31 PM Posted Wednesday at 03:31 PM Yeah, can't really say I am having any problems with them. Point the seeker at the bad guy, TMS up, shoot.
NoJoy Posted 17 hours ago Author Posted 17 hours ago Well yes thats why I didn't take this as a bug as there are no issues reported elsewhere. Still I'm wondering whats going on as I drive the Hog for over ten years now and never had issues getting a lock on. So I will keep diving deep into whats going on and will eventually make some tracks. Thanks for your feedback anyways and thanks especially to the Godfather of the Hog Yurgon who is always willing to give advise and a hand! 1 Brrrrrrrrrrrt I'd rather call in a Strike Eagle... I7 6700K, MSI Z270 Gaming Pro Carbon, 32GB G.Skill Ripjaw V 3200, Inno3D GTX 1080, Samsung 970 Evo, Thrustmaster 1.6000M, TrackIr 5
Recommended Posts