LastRifleRound

The part I don't understand is you say NAV sets the range, but also where you're looking sets the range. These both can't be true.

It's a bug. The only dumb bombs that will work consistently without work-arounds is AUTO with Mk82. Everything else has some issue you will need to know the bug and therefore workaround.

Does the real gunsight stutter this much? It's extremely choppy. AA gunnery in the Mirage is next to impossible for me using the gunsight. I Kentucky windage it using the gun cross and tracers just like before the past two updates. Anyone having better luck with this? I'm: 1. Making sure I'm nose to tail 2. Making sure I fire slightly before the reticle crosses the target 3. Of course, I have radar lock Supposedly you're supposed to get a double box showing it's ok to shoot, but it never appears for me

This happens with non-jamming contacts. It was acknowleged in the bug section then fixed for the most part, but AIM7 launches still trigger it sometimes. Remember in ACM you had to attempt lock 3 or 4 times as the radar would lock the "ghost"?

It does happen to me, and there are usually two culprits: 1. Your radar briefly tracked your own Sparrow instead of your target, then lost track of the Sparrow and now it tracks nothing 2. There is a "Ghost" your radar will often lock at 99nm. No one knows why. It will briefly track this then dump lock Both bugs are months old now. The Viper doesn't share them. Then again, the Viper doesn't arbitrarily show missile tracks. Maybe that will change. Supposedly an SU27 pilot said they should.

I was

By that logic so is this post. There was an acknowledged bug cited in this thread. People are having a conversation about being upset about it as a reaction. We're not trying to extract meaning or monetary value out of the conversation, we're just reacting. I thought that was allowed in forums. Were this the bug forum (where I posted the actual bug cited here) I'd be inclined to agree with you and would expect the conversation limited to the scope of the bug itself, but this particular sub-forum is for general discussion, which is what you are seeing here.

So many paper tigers. "For years" does not equal 3+. It means more than one. I said two things separated by a comma. "Every method of iron bombing has been bugged". This is a true statement. ", some for years". Also true. I provided evidence (mk83 bug is from 2 years ago, A10 bug is over 5 years. Radar designation bug is over 1 year almost 2 now, HUD TDC bug is from the beginning). What you did is in your mind was delete "..., some..." and then accused me of saying the resultant summation. I did not say what you said I said, and everyone can read that. Maybe English isn't your first language. That's cool, but don't put words in my mouth or in this case, selectively choose them and give them alternate meanings.

You can set the increment to .1 degrees, but the ME will only give it in 1 degree, that's what I meant. I used your method of delta lat/long with great results before, and now RAZ has added that handy shortcut for the ME that lets you skip a step on the ramp. They're really killing it with the Mirage lately.

Please re-read what I wrote, because you seem to think it was "all methods of bombing have always been bugged since the beginning", which is not what I said. Look into my history and you will see me actively engaging amd contributing on this topic for years. Also, I never claimed anything was "game breaking" as that's a nebulous throw-away term. Bottom line, these things are bugged, some of them for years, and I don't like it, and many others don't either. You're free to ignore it if you want, but that doesn't mean I'm not telling the truth.

Yeah it's still bugged exactly the same way. FRZ mode has been fixed but now exhibits the same issues as EXP/DBS

That's because using a pod with AUTO is the ONLY thing that works and ONLY with MK82 and ONLY below a certain speed. Every method of iron bombing has been bugged in the Hornet, some for years. HUD designations are misaligned and if you don't have a TDC axis too coarse. The radar designations are bugged from aircraft motion. Mk83's are bugged no matter what you do. Ccip is bugged as described here. If you don't have GPS, sone mysterious bug will make all bombing impossible. And no one seems to think it's a priority deserving a fix anytime within the span of years. Seeing as the A10 STILL has iron bomb bugs it had 5 years ago, there's a very real possibilty much of this is never fixed. It's wrong.

Rho/Theta is a pretty inaccurate way to do this. Zoom in on the ME and just look at how much of a difference 1 degree makes. You cannot get more accurate angles than 1 degree increments in the ME. I recommend using delta lat/long if you have to do this in the jet. Even better, in the ME place a waypoint over the IP, and one over the target. In the Name field for the target one, type in "#CONVERT_TO_BAD". That will automatically become a precisely offset to the preceding (IP) waypoint. I'm seeing great results at 40 degrees, but ONLY if I keep that pipper dead still for a bit before designating, just as you say. However, I find that turning RS off might be necessary. It could be in my head, so I'm going to do many more runs to confirm it. It could also be in my head and I just hold the aircraft steadier with it off due to some subconscious confirmation bias. Hard to say, as I'm really pushing the limits of accuracy with the system to obtain an ideal to work backwards from. It's fun doing it. It's very challenging but entirely possible to nail a small house-sized target when using another house-sized target as an IP. Really tests your ability to hold her steady and wings level in the dive.

The Viper bug appears to be less dramatic and different. If you are banked aggressively away from the target (say, 30 deg or more of bank) the cursor placement will be accurate. It's a lot harder to pin down, so I haven't made a bug report about it yet, but that's what I've seen so far. The Hornet bug is far more dramatic and is definitely tied to aircraft motion.

CCIP is bugged, the aiming cross is mis-placed. Additionally, if you are using Mk83's, those are bugged for all but a very specific speed and altitude pairing. Confirmed Pipper bug below. Mk83 bug also confirmed but it's old (though never fixed) so I'd have to dig it up. If you want to use CCIP, you need to drop late, past the target. You can use the FLIR as well, which does accurately place the impact point.

The above describes entering into FTT. This works fine currently because the radar map coordinates are not used for this. The problem is with INS designations. FTT is only feasible on isolated ground targets.

I know this exists in azimuth when it comes to DBS calcs, but the inaccuracy of the calculation running in reverse doesn't change over time assuming the aircraft has done a good job keeping its own position. The only thing I could guess is the documentation assumes an unassisted INS.

Good find. Seeing the same thing.

This is definitely an issue, but I'm seeing a more subtle issue as well in my testing. Designation accuracy seems to decrease once angle off exceeds 20 degrees. I can't find anything in the MLU docs saying this ought to be the case (though the MLU doc does say to slew as soon as possible after the image appears, though it doesn't say why. With the "snapback" this certainly shouldn't be done in DCS right now). I'm still testing this and will come up with a track if I can repeat it and nail it down.

This is still having the same issue. I'll cut another track but have another observation. Another easy way to demonstrate this issue is to designate point on the ground with the radar. Get within 12nm or so and 30-45 degree offset. Open up the FLIR image. Now, without slewing, keep designating the same spot in rapid succession. Watch as the designation in the FLIR slides along the opposite direction of the axis of travel, and watch as the "skip" gets larger the more angular velocity to that point increases. Not sure if that helps or not. I can also confirm that the JF17 and Viper do not share this issue.

I love the simulation of the radar ranging function for air to ground work. @myHelljumper, what are the ideal parameters for a designation, both for CCRP (low drag default mode) and PI designations? I'm getting mixed results from 20 degree dives (IP is on flat ground). What is the idealized set up one should practice when doing this (dive angle, altitude, etc)? I want to be doing this as "by-the-book" as possible.

That would be a problem of accuracy, not precision. The cursor is always above the designation exactly the same way every time, so the system as currently implemented is precise, meaning it is exactly inaccurate the same way every time. This almost always indicates a bug. Also, TACMAN indicates using the HUD to refine the point in almost all cases, and never once mentions it for areal use. I think that's how DCS players use it, but that's because with the current slewing implementation that's all it's good for. According to documentation and users like @IvanK, this is not correct and the HUD should be uses to refine the aim point all the way to release.

Track attached. The TD box itself is sometimes offset low. CCIP is working as expected, so it is likely either a designation point error or release point calculation error. Could be related to this bug: F16_mk82_short.trk

Track attached. I slew the HUD TDC cursor, ensuring the radar is in AGR. I look back and forth from the HUD cursor and the FLIR which is slaved to the designation. You can see that the designation is always below the actual cursor dot, and if the cursor is off the nose to the left, the cursor is to the right of the designation and vice versa. I also try inside and outside of active pause, and try different perspectives and zoom levels with my TRACKIR and slow zoom and the results repeat every time. I would expect, especially in active pause, that the cursor and the designation point are co-located. This holds true (shown in track_2) when designation is done the other way around, i.e. you designate with FLIR and inspect the diamond location in AUTO and find the diamond is offset in the same way. Hud_cursor_bug.trk Hud_cursor_bug_2.trk

You can do this same thing in EXP and not worry about vertical stacking and you won't have to slew the cursor to bug a target, you can use the NWS button to step as normal, though the update speed will not be as fast.