Distance to Target (A10)

During missions, I set the waypoint to the target waypoint and then switch to A-G mode. This seemed like an easy way to orient myself to the target as the HSI always points to the target waypoint. But I noticed that the distance to waypoint number... both on the HSI and HUD freezes at the point I switched to A-G mode. Doesn't get updated in A-G mode. Is this normal?

Also with Mavericks... why is it so difficult to lock the target I want? If multiple vehicles are in a cluster, it always locks onto one of the target and keeps doing it until I'm within 4~3nm. Am I doing something wrong? I am following the procedure in the manual.

I've noticed the HUD nav info doesn't update when in AG mode too. Strange, I think.

When the Maverick is locked on / stabilised, you can still slew it around - or do you mean against targets that are very close together?

Cheers!

Yes I mean when they are close together but not THAT close together. I slew it onto the target I want but it always snaps back to the other one. As I've said, this is from distance of about 5nm and I finally can get the lock on the target I want when I'm in about 3.5nm but this basically reduces the range for Maverick.

I slew it onto the target I want but it always snaps back to the other one.

Maybe but in that case the pilot locked onto the tactical bushes himself, in this case the "simulation" decides to break your lock and put it onto a tactical bush itself, and even when you see it being done and you can clearly identify the target, you can't do anything about it. I can't imagine that it works that way in real life... There should be an overide over the autolock if one can cleary see the target.

During missions, I set the waypoint to the target waypoint and then switch to A-G mode. This seemed like an easy way to orient myself to the target as the HSI always points to the target waypoint. But I noticed that the distance to waypoint number... both on the HSI and HUD freezes at the point I switched to A-G mode. Doesn't get updated in A-G mode. Is this normal?

No, it works fine on 1.12b, but not FC2.0 I have reported on Bug Thread.

No, it works fine on 1.12b, but not FC2.0 I have reported on Bug Thread.

Thanks for confirming it and reporting it as well. While I'm at it I'd like to ask another question too simple to open another thread for. Avenger can't kill T80? I emptied all cannons on one T80 and it's still alive. If not, what can kill T80? Only Mav's? Mk82? 20?

Avenger can't kill T80? I emptied all cannons on one T80 and it's still alive.

I just tested it and while I admit that it'll take a lot of rounds if you're attacking the tank's front armor, it takes considerably less by attacking from behind or from the a higher angle/top. And you have to consider that the cannon is now a much more inaccurate compared to FC 1.1.

In that case you certainly didn't hit him.

I just tested it and while I admit that it'll take a lot of rounds if you're attacking the tank's front armor, it takes considerably less by attacking from behind or from the a higher angle/top. And you have to consider that the cannon is now a much more inaccurate compared to FC 1.1.

Yea, I did just manage to kill one too but took about 300 rounds.

It can be done in bout 25 rounds NotiA10 could do it all the time I could do it most of the time just practice and get close from the rear is much easier remember trigger control short burst just a touch will do. Good sight picture and a steady hand on the stick

I'm not that good a Hog driver and it took me about 100rounds for the first kills. Now I'm at smth like 75. And I'm sure someone else could even use less.

During missions, I set the waypoint to the target waypoint and then switch to A-G mode. This seemed like an easy way to orient myself to the target as the HSI always points to the target waypoint. But I noticed that the distance to waypoint number... both on the HSI and HUD freezes at the point I switched to A-G mode. Doesn't get updated in A-G mode.

This bug is really annoying and i hope there will be a fixing patch soon.

It does take a few more button presses to switch back to NAV mode to check the distance to the target zone and then switch back to A2G mode and choose the right weapon.

A little stressfull if you are closer to the target area than expected. :D

By the way .. are there any ED people working on bugfixing for FC2 ?

Or are you guys only working on DCS: A-10C right now ?

Wags ? An answer would be great here.

Unfortunate but understandable. Can't wait for A10c. I anxiously await being able to drop a GBU-12 onto a T80.

Wow , thank you for that quick answer Wags !

Ok, we have to live with that little A-10 bug then.

Also waiting for DCS : A-10C

Christmas time 2010 would be great for a release :music_whistling: :D Need the equivalent Software for the TM Hardware coming soon

Thanks for confirming it and reporting it as well. While I'm at it I'd like to ask another question too simple to open another thread for. Avenger can't kill T80? I emptied all cannons on one T80 and it's still alive. If not, what can kill T80? Only Mav's? Mk82? 20?

Hi Ven ...I too had trouble killing some T55 I setup in a test miz until I moved them out of a slight depression they were in. Then no problems.

Have seen this behavior in Black Shark, numerous Vikhr at a single tank with out effect. Could be hight map problem until the vehicle starts to move. Vikhr thinks its hitting the ground ??

Cheers