S77th-GOYA Posted February 16, 2006 Posted February 16, 2006 This mission: BARCAP_SEAD_CAS_maikop_vs_anapa in the (504) has an example of a bug that I've seen once before. There is a SAM very near the Novo runway that can't be locked by a Mav-D. Not only can't it be locked, the Mav-D will not ground stabilize anywhere near it. If you move the Mav seeker away and ground stabilize, it won't move to the SAM's area. It treats it the same way as if you try to move a ground lock to the sky. The other time I've seen this was also near Novo. edit: The same problem exists with the Mav-K. The range reads 0.0 and no lock.
DarkSoul Posted February 16, 2006 Posted February 16, 2006 This mission: BARCAP_SEAD_CAS_maikop_vs_anapa in the (504) has an example of a bug that I've seen once before. There is a SAM very near the Novo runway that can't be locked by a Mav-D. Not only can't it be locked, the Mav-D will not ground stabilize anywhere near it. If you move the Mav seeker away and ground stabilize, it won't move to the SAM's area. It treats it the same way as if you try to move a ground lock to the sky. The other time I've seen this was also near Novo. edit: The same problem exists with the Mav-K. The range reads 0.0 and no lock. i have noticed that too...mavs dont lock if there are targets near runways
Shepski Posted February 17, 2006 Posted February 17, 2006 Hi Goya, I looked at this and when I flew the track file myself I also couldn't lock(ground stablize) the Mav pipper on the airportand it indicated "0.0" When I approached from the water side I was able to ground stabilize the pipper on the airfield indicating the proper slant range and lock up the Strela and kill it. Same results in a newly created offline mission too. Testing in the same mission down the coaost at Glendzihk I did not see this same problem so it might only be related to Novo. Thanks for the report.
Gazehound Posted February 17, 2006 Posted February 17, 2006 I saw that when I was actually making the mission and testing it....then i came in from another angle (from the west I think) and I could lock near the AB. So I forgot about it and put it down to a temporary quirk. VVS504 Red Hammers
S77th-GOYA Posted February 17, 2006 Author Posted February 17, 2006 Thanks for looking, Shep. The other mission where I noticed this also had a certain direction where a lock was possible. The unlockable area in that one was on the hill to the southwest of the runway. It was lockable from the east.
Quirkitized Posted February 17, 2006 Posted February 17, 2006 This isn't fixed yet? It has been there since the game has been out. I haven't flown at that airport in a long time (haven't flown in a long time period) so I figured it would have been fixed atleast two or three patches ago... I gave up making missions for A10 at that airport 2yrs ago...good to see it's finally getting looked at...
Prophet_169th Posted February 17, 2006 Posted February 17, 2006 This isn't fixed yet? It has been there since the game has been out. I haven't flown at that airport in a long time (haven't flown in a long time period) so I figured it would have been fixed atleast two or three patches ago... I gave up making missions for A10 at that airport 2yrs ago...good to see it's finally getting looked at... Things dont get fixed if people dont report them. And since you knew about it 2 years ago........? Thanks for the input GOYA, I will check to see if its this way for Su25T also.
Gazehound Posted February 19, 2006 Posted February 19, 2006 Found my shots I took at the time VVS504 Red Hammers
Recommended Posts