LastRifleRound

This is the same bug AGM65F has with the AV8B, and can be observed functioning erratically with the Walleye. I believe there are "visibility modifiers" under the hood that are meant to give the appearance of a contrast lock. These modifiers determine how "lockable" an object is. Cloudier, darker, smaller, and size relative to tracking gate means lock range decreases from max, down to 0 ("unlockable"). Those values likely need some tweaking. EDIT: Just realized Nikola said the same thing.

Yeah the fake noise is impressive. Still good for cueing in on an area when given vague talk-on. Well done!

How many bars is SPOT? Is it just whatever you have the radar already set to or is it a set number of bars regardless of setting?

Have you tried with absolutely clear skies mid-day? Usually these tracking issues have to do with the functions that handle target visibility under the hood.

I don't know what "our" harrier has to do with the point I made. Again, not an expert here, just pointing out the two systems have been 100% identical so far.

I'll be happy if they just get ATFLIR right.

TACMAN for Harrier apg65 confirms this is a feature for that jet. So far the two implementations have been identical. Don't know if that helps, as the MC's are different. That pod feature would be really nice....

Fair enough. It gets in the way of engaging horizontally separated groups where repositioning is necessary between missile launches, but I understand the trade-off.

I'm guessing that it does stow, it just doesn't change the scan volume until you move the tdc back out of the gutter. This would make sense especially if you used the cursor to switch from RWS to TWS. In no other scenario does the scan volume react to a TDC outside the radar box except this one, pointing to it likely being incorrect behavior. Sim code seems to treat the cursor as active between where it was and the stowed position. Likely fix is cursor should disappear and reappear stowed, or be treated as inactive until reaching the stowed position.

Is stepping implemented properly? I have track priorities 1-4, and let's assume priority doesn't change during the engagement. Rapidly pressing undesignate will step 1 to 2 to 3 to 4 to 1. No problem. However, if I undesignate, then wait two seconds, it will always jump back to priority 1. So, 1 to 2, wait 2 seconds, 2 to 1. 1 to 2 to 3, wait 2 seconds, 3 to 1. Is this correct? Does timing matter when stepping or is it always sequential?

One thing I noticed in all bomb modes is if you are pitching at all, even if it's a nice stable consistent pitch, you will miss. This probably shouldn't be the case. I find the aircraft needs to be completely unloaded then I get great results.

Yes you're right about wind. Also effects the CCRP mode. I think it's opposite, i.e. the computer gives the correct offset but with the wind as opposed to into it.

Looks exactly the same as LITENING. Wags used it to 'slew' the auto track, though it looks like just like LITENING, all it does is designate the spot you put the cursor. I thought this was incorrect behavior for ATFLIR? I remember seeing videos of the offset actually moving camera FOV. This thing looks and behaves identically to the LITENING save for the grid readout (which I believe LITENING is supposed to have anyway) and that you can slew its 'area' mode. Am I missing something?

Great advice all! This seems to be a somewhat recent issue as I used to find the Mirage one of the easier aircraft to land. Looks like the key is to wait longer so you can more gradually raise the nose and drop the throttle. Will do many practice runs tonight.

I keep hitting like a ton of bricks or ballooning with the mirage on my landings. Velocity vector in ILS box, chevrons on brackets, velocity vector in brackets. All should be good. Any pointers?

INS bombing works perfectly for me on open beta. Drift is fast but not significant enough on distance between IP and TGT. Use polar difference instead of rho/theta and choose an ip small enough that you can make a precise designation (updates are no longer precise so if your designation is off your bombs will be off) but large enough that you can see it. Can post a track later to demonstrate.

After the last OB update where INS updates finally work, and offset waypoints can now be added with 1m accuracy, there's almost nothing the Mirage has billed that it can't do. It has rockets that actually damage things, all bombing modes (CCIP/CCRP/Offset) all work as they should, and Magics and 530's seem to operate normally. Ever since then it has been one of my favorite aircraft. RAZ did an awesome job updating it and the main campaign is excellent. I would definitely go for it. In the numbered list above, 1, 3 and 4 have already been fixed. Offset bombing is very accurate, just follow the procedure outlined by @Frederf here The only major gripe I have is the gun sight. It behaves like the old Hornet and Viper ones did if you remember those. It's not accurate in terms of ranging so it needs some tweaking. Definitely usable but if you're used to the Hornet's excellent gun sight the Mirage can be a kick in the pants.

Diving AUTO is the way to go with some caveats for the Hornet. If you're using Mk83's they are confirmed bugged and will fall short in a dive. If you want them to hit you need to aim long of the target, and I find this easier to guess in CCIP than AUTO at the moment. I haven't tested Mk82's or Mk84's as much but it seems the effect isn't as bad in those, with mk82's being least affected by this Mk83's will only hit their aimpoint at 7k ft at 370kts for some reason, and you're unlikely to hit those parameters in a dive. The higher you are the slower you need to be, the faster you are the lower you need to be. Too high/fast=bomb short. Too low/slow=bomb long. A 450kt diving delivery virtually gaurantees short bombs. Again, this is due to a bug in DCS and has nothing to do with any real world procedure. Confirmed bug report Here

JDAMs are kind of a mess. QTY doesn't work right either in AUTO. The only reliable way to use them is in MAN mode, no term parameters set, and heading to the target. This will almost always work.

On mission 1, DO NOT allow 2 to refuel first. He will finish before you, then make a right hand turn directly into your aircraft. Happened to me 3 times in a row.

I would try doing a full manual startup to rule out multiplayer as an issue, or try a single player autostart. Once autostart is isolated as the cause, we can see what's going on in the procedure that might be getting left out.

1. Have you given enough time for the WEAPON (not the jet!) to align? In the JF17, master arm has to be ON and the weapon selected and powered up. I think LS6/GB6 need about 1:30 or so but don't quote me on that. It is NOT instantaneous, I know that for sure. 2. Are you using PP or TOO mode? 3. The DLZ calculations in DCS are all somewhat wrong. They are only accurate if your current heading is towards the target. This goes for the A10, the Hornet, the Harrier, and the JF17. Often being within 20 deg is enough, but the closer to the outside of the DLZ you are, the more this is a problem and will cause a miss. 4. Are the targets near each other? I kept "missing" a target on a mission only to find the heading the mission planner gave me would cause one bomb to be caught in the other's frag pattern and result in the destruction of the second bomb, so the second, further target was never hit.

Fred you are the king of nav on these boards as far as I'm concerned. This works great after the latest update. With updates no longer being perfect there's a skill to it and it's very satisfying to get it right. Thanks for this.

I always wondered this. How do you do this mathematically? Is it just simple subtraction? That's pretty cool, but it gives direct distance as opposed to x and y offset

If you want the missile to follow RP's you must use MAN mode. WPT36 (PP1) will be ignored in this mode. The seeker will turn on 2nm from wpt31. DIRECT - Basically TOO mode. Missile flies to SPI (WPT40). Seeker activates 20nm (I think, forget exactly) before reaching. COO - Basically PP mode. You choose WPT 36, 37, 38, or 39. Missile flies there and activates seeker 20nm before reaching. WPT40 is ignored MAN - Missile will follow waypoints 30-35 to the last one set (31 in your case). Seeker activates 2nm before reaching the last waypoint in sequence. When using MAN, you don't want last waypoint on the target, as 2nm is too close. Instead, the last waypoint should further back and placed in such a way that the course it takes from the previous waypoint to the last one points the missile at the target. Hope this helps.