LastRifleRound

Ok I think I get it. We'll have to wait and see what Zeus has up his sleeves I suppose.

I think you're right, even for radar correction we know there is a CCRP method that is choosing a location at the end of the day, which gets plotted on your HUD. I think the problem might be deeper than this. What if they're not modeling drift at all, rather just shifting the waypoints around to make it look like drift? This would explain why it's not done and why the waypoints resolve to the correct position. Would also explain why waypoint positioning in general in the Mirage is screwy. Pure speculation of course. If they are actually modeling drift, I have no idea why they wouldn't finish the INS, because all of the hard parts are done already (designating positions, modeling actual drift, VAL function). However, if drift is being "faked", this would explain it a bit better. Still, 3 years for this is way too long. It's core systems functionality in the Mirage, not some edge case procedure.

I think the reason you can't use the radar (or VIP bombing mode) is they use AGR, which isn't implemented yet. However, you should be able to use the TPOD to do this. Then again, maybe the real jet will only use AGR for this operation and that is why we don't see it.

This! Though I have to say I don't find the LD10's too accurate, I find HARM's randomly miss on active emitters that are tracking me for no reason. Several shots at tracking radars at 25k feet within 20nm and the HARM just lands 10 feet to the side of the radar. Weird. I do agree, GB6 should be able to be shot down as easy as a JSOW. To be fair, I won't use them until I've knocked out the search and track radars, as it is a bit cheesy to just chuck a couple grid erasers in there and call it a night.

This looks like a mistake. If one mode is supposed to be 1.2 seconds after release, and the other at a set height, it could be they use the same method to detonate, and the 1.2 seconds is stored in there without any conditional. I.e., let's say there's a method "detonate" that tells the bomb to go off after 1.2sec. When in PRI mode, we call bomb.detonate() right away. When we use VT, we call bomb.detonate() at 1500ft. bomb.detonate() Probably a simple fix, detonate should check mode to apply or not apply the 1.2 second delay. Pure speculation, of course, but it would be an easy mistake to make.

Have you tried SEAD in this thing? 4xLD10's and 2 GB6 with SFW. I'm wiping entire BATTERIES off the map. Knock out the radars with LD10, mop up the launchers with GB6. :joystick:

I never noticed any drift, so I'm not sure. I'll be watching this one. Also seems like there should be a "designate" option for PU like there is for MARK instead of just "OFLY"

I don't think that"s quite it. Nseq appears to be more involved than this with ingree/egress options, color coding, etc

Could anyone shed more light on NSEQ navigation? I read the NATOPS, and it briefly mentions the setting when discussing EHSD nav functions, but refers to another document for more information that doesn't appear to be online. I saw Zeus's post about what it looks like, and I don't get what it's for. It shows ingress and egress points that look to be a linear (sequential) series of points. Does anyone know how this works and what it's used for?

No way. The doppleganger thing is definitely the right answer here. What were we talking about again? :lol:

Ny guess is that it puts realistic limitations on performance. Brings the min range further out, shortens the launch window so it's not like carrying 16 LMAVs.

Whereas I do agree that lofting is pretty edge case and therefore not that useful, I think auto modes handling of multiple qty release on pre planned targets is very useful, particularly if terminal parameters are involved. MAN mode treats every bomb as an individual, whereas AUTO treats every selected bomb as one pass.

Not implemented yet. This was just a preview.

Very cool! Is this set by the CAS page? Are there course deviation indications now?

They are not implemented, but knowing how the Hornet's system works, I can answer some of these (with a small amount of conjecture.) 1. This is because the system needs to center the scan around something. If it is in SP, it is ambiguous as to where you want the scan to be centered. It is likely there will be a designation "patch" if you are in SP and pick one of these modes in the future, where you can select where the scan should be, but this is pure speculation on my part. 2. I don't know what you mean by this. You can hit the designate button and designate an area of the map to recenter on. Pressing again on that same spot enters FTT. In the Hornet, FTT is entered only if there is a radar-discernible feature at that location (building, vehicle, landmark that stands out). Since this is the only way a radar could lock on to a ground feature, I'm assuming it works the same in the JF17. Since this feature is not complete yet, it always enters FTT. Having FTT gives you a much more accurate bombing solution than just designating a spot on the radar without it, as the latter is INS interpretation of the ground map whereas FTT is like laser ranging that point. 3. Press it twice to go back to the waypoint. Not sure if this is a bug. Again, until the actual radar API is available I wouldn't expect small quality of life stuff like this to be changed 4. This is a bug. Again, won't be fixed until the modes are actually implemented. I want it to be known that I do not have any advanced or inside knowledge of how the JF17 radar works, but there are things that are common among all radars that are logical. This post is speculative in nature and until the features are actually implemented there really shouldn't be any bug reports.

Do you mean GMTI or GMTT? GMTT is ground moving target tracking. It's analogous to STT in the air, all the radar energy is directed at one contact and all others are dropped.

I know for sure RCAF uses the cheek station.

It's not implemented yet. AUTO/LOFT does not literally program the JDAM to loft, that would actually reduce the weapon's impact range. It does provide a loft line, that will only increase range from the mid-low atltitude regime. Lofting a Jdam above a certain altitude is actually counter-productive. AUTO mode provides guidance to the center of a release point on the HUD. If a QTY of > 1 is selected, then you will be guided to a point where release is possible for all selected bombs and their terminal parameters. If such a point does not exist for the selected QTY (no overlapping release point for all selected bombs), then no guidance is provided. On the HSI, an LAR is displayed when aircraft heading is within +/- 15 deg of all QTY impact points and the aircraft is within +/-15 deg of LOS for all terminal headings (should any be selected). This LAR is a space where all selected bombs can be successfully released. Again, if such parameters are impossible, then the LAR will not be displayed. It's a very involved system and very cool. I posted a while ago asking when terminal parameters would be made active, and the reply from ED was when AUTO/LOFT was implemented. I hope it's finished after the TGP pointing modes are done. They did say it's in their "phase 1" (if they're still adhering to that) of the Hornet roll-out, whereas things like the AG Radar are in phase 2.

It'a possible there's some time zone difference I'm not aware of, so I can't say this is a bug, but yhe correct times to use on the HUD are 0605 and 0615

Ok I pulled this mission off, landed, but my score was 0 and results was 50. Is this from incorrect ID of some of the targets? It's almost impossible to make out what I'm looking at. I pop up to 25k (I wasn't doing this before, so the SA8 near WP10 was getting me), but can barely make out many of the objects. I can make out the HAWK site and the attack Helos pretty easily, but as far as the rest of the questions, I was just guessing. The train yard, in particular was impossible to identify if was a CP, fuel transfer, etc. Any more tips on this one? PS, to beat the Mirages you simply need to get in right at 6:15 (time in the HUD) recon all the targets then turn tail on full burner to WP12 > 13. They are on a timer. By the time they launched on me the BRA call-outs had them at over 60nm, way too far to attack me. Once you get in your own SAM net near WP 14 you're good.

Right, ground vehicles do show up rather easily. However structures do not show up at all. I've attached two pictures here. In the first, the WP has a very large metal hangar in the middle of it. The return does NOT show on the radar at all. In the second picture, I added a small CP vehicle in the hangar's place. You can clearly make out the return of this vehicle, even while not in LOG mode. Pic 1 Pic 2

Just tried RR, NAV and PLAN modes again. ALL are falling short. This is a big problem. Viggen cannot accurately drop LD bombs in anything but DYK, probably because the pull-up cue is always too far up so it compensates for the issue (plus you're in a dive). HB you really need to look into this. I can attach more tracks if necessary, but the ones I've already posted should suffice. Ran another try just to be sure. Here's a track of a run in NAV. Used to hit this all the time no problem. Now, bombs short. bomb_short7.trk

What is overlay 1?

Thanks for the advice guys. In summary: 1. Keep elevation higher than desired scan zone 2. Unreliable over 40nm in all modes 3. D/L still ok

Those are good ideas also