LastRifleRound

I think all it will be is external model, MWS and Igla. Nothing else has been promised. If this is the final list, I don't plan on buying it, it's just not compelling enough of an offer to me. I think INS drift ought to finally be simulated and the shkval needs a major update.

Got crossed up with the Hornet, you're right, MAV video won't come up in the Harrier unless you've uncaged. I'll test this out but if I recall I was getting tracking on the MAV.

Did you hit uncage while still in TPOD HOTAS mode?

If it drops off the second you unsafe, either or both 1.) You waited too long to unsafe 2.) You're too far off the altitude to get there on time Provided you have a good designation you should immediately trigger depress. You may be able to use the steering order, but if that's too far off you're better off flying as straight and level as you can, bombs will still hit. Don't chase the cues, they're not needed to be accurate and the CK37 doesn't do well with pitch moments during release. As long as your horizontal positioning is good and you're above frag you should be good. If you're so low you'll be in frag pattern, abort. The closer you already are to the altitude you're supposed to be at when you unsafe the easier it will be. You don't need to worry about what the cue means, as it's a flight director. Pitch the nose to put it on the target and keep it there until you can no longer see the target or the bar flashes. You are correct that if the pipper is not coincident with the target and it's low, you need to pitch up. However, if the pipper is coincident and the target and thus pipper falls off, this is sometimes normal, particularly for the higher safety altitudes. Trigger depress and use the steering order.

I actually saw in Silver_Dragons roadmap thread they're working on IR signatures for ground objects, so maybe this is the sort of thing they were talking about.

For ANF/PLAN, when you unsafe the trigger you are designating the spot under the pipper as the target. Your job at that point is to fly to keep the pipper on the target. When the timer bar flashes, or the target slides out of view, whichever happens first, pull and hold the trigger. A steering circle will appear. Now fly to keep the pipper in the steering circle while keeping the trigger held. This is a consent to release mode, so the bombs won't fall until the computer decides it's right. As for the altitude, that guidance is ignorant of AGL, if your QFE is right that will be your barometric altitude over the target. You may want to set your altimeter readout to barometric for this reason so you won't have to pitch dramatically when you designate. The actual altitude it will guide you to depends on 1.) Type of ordinance and 2.) The safety altitude as set as a waypoint property in the mission editor (low, medium, high, default medium). For example slick mk82's safety height for PLAN/ANF is 200m, 400m, and 600m (low, med, high respectively). So, if you have the QFE correctly set, have slick Mk82's and medium safety altitude, and have designated a target with trigger unsafe, the pipper when placed on the target (and later the steering circle when trigger depressed) will guide to an altitude of 400m at the time of release. Hope this helps

Also some aitcraft every few flights are flown decoupled so natural INS error correction algos aren't thrown off by errors being masked by the GPS being on all the time. Not sure if true for JF17, but true for the Harrier.

I think it's really important to stress that if you have a GMTT and switch to the FLIR, the FLIR isn't tracking anything. It's just slaved to the system designation. This isn't a PTRK and does not count as the pod successfully tracking anything. Until you explicitly activate PTRK (captain's bars), the FLIR isn't tracking a moving target.

I thought I was going crazy! Kept losing tracks but wasn't paying attention to AZ/EL, usually when I go to AUTO I take my eyes off of that screen!

This is definitely a thing. To see how much difference it makes, equip your jet with ATFLIR instead and initiate AUTO track. You'll get the expected result with that pod, but not with LITENING. I will upload a track later on of a mission at 12:00 hours, cloud preset 1 with winter conditions. LITENING is unable to PTRK even within 3nm, possibly ever (I'm not that good slewing the pod that close in)

Very cool. Is the altitude guidance only available with PI mode active as is in the video? Am I correct that the staple represents the recommended altitude, with the down arrow appearing when the FPM is at the top and vice versa? If I'm correct, he was a little low when he released. Is the break in the CCIP line the end of the string? I've played chicken with terra firma one too many times with snakeyes! The ground always seems to win no matter what I do...

I saw this but I don't understand what's different aside from the staple on the HUD

Just wanted to show my appreciation to RAZBAM for their work on the Mirage. It's in an excellent state right now and I think it's one of the best modules in DCS right now. Well done on sticking with it and fixing many of the long-standing issues and adding new features.

This might be a bug. Currently, the second you leave TPOD HOTAS mode it goes into INR and stops tracking. It's not your fault, it's just doing that now.

To recreate: 1. Designate a waypoint as TGT 2. Angle off to sufficiently draw an EXP map 3. EXP3 works best 4. Designate a known point on the map. The INS designation marker briefly appears over the point (less than half a second), then jumps to the middle of the screen. 5. The next sweep does not initiate any faster than it would have otherwise. Expected result: EXP map should instantly re-scan. Angle-off bug is separate issue and documented here, and is still in effect. Track attached. hornet_ag_cursor.trk

To recreate: 1. Lock IIRMV on to a target, make sure in range 2. Make sure HARM OVRD unboxed 3. While target locked, have SAM lock up aircraft 4. Press weapon release Result: Both HARM AND MAV launch simultaneously. Selecting the next IRMAV will now be impossible Expected result: On step 4, ONLY HARM launches. IRMAV will not launch until all HARM expended, HARM OVRD is boxed, or SAM drops lock Track is attached. HARM_OVER_BUG.trk

Note that you're going to get a bit of a curveball with a moving target. I reported it in bugs though truly it may not be, but as soon as you leave TPOD HOTAS the TPOD will revert to INR. This is fine for a stationary target, but if you had a PTRK going, the second you SSS down twice, the reticle will fall behind a moving target. When you SSS forward to take control of your IRMV, you may have to reposition the mav to re-obtain the target, which can be be pretty tricky with they way the Harrier handles direct Maverick control.

Is that box user controlled or just a visual representatiom of what the system is doing?

ATFLIR AUTO track is far superior, with better visual feedback and a larger tracking zone. Litening PTRK appears bugged. 12:00hrs, -2c, weather preset 1, FLIR active, Litening unable to aquire PTRK at less than 4nm. Same conditions ATFLIR is capable of tracking all placeable objects, moving and stationary out to 10nm. Tracking gates move with the object so you get good visual feedback that a track was successful.

Makes employment of IIR mavericks difficult, as the TPOD will stop PTRK immediately as soon as you focus on IRMAV. Not sure if this is intentional. Track attached. harrier_TPOD_track_loss.trk

Strongly recommend making one bug report per bug and always attaching a track. Some of these bugs get pretty expansive.

Finished my testing on the PI bombing accuracy, working great. Not sure if something changed with TAS, but it seems like you just need to be a bit more careful with the designation than I used to be. +20 deg dive and about 2500ft AGL gets great results when designating the IP. You get the symbology without having to overfly and you don't need to hit VAL. Good stuff! I use #CONVERT_TO_BAD to get around the delta Lat/Long issue.

Not precision, accuracy. Always off the same amount the same direction. I need to do more testing and open a new thread when I have more information.

Are both the input being rejected and the bombing solution being off confirmed or just the input?

When setting up a PI profile, before if there was no wind, PI bombing with good designation was accurate enough. Now, the delta Lat/Long option rejects any input to the west, and the bombing solution is always off to the west. Attached is a track of the PCN rejecting valid input. I tried this same mission with the waypoint name making it BAD and got the exact same bombing results. Target is to the east, but bombing is off to the west. Testing if the input is inverse, I noticed I couldn't enter values to the west. Will make another post showing the results of the bombing run. One for using waypoint name to make BAD, and another to use delta Lat/Long to make BAD. Both are the same. mirage_PI.trk