LastRifleRound

This is actually implemented in DCS. The A10C has CCRP for FFARs. Think I tried it once in the training missions and never really tried it again. Going to have to try it out on some large targets.

I expected dynamic launch zones to come out a few months after the initial JDAMS release, but it looks like a whole slew of things came first, including Viper development. Is this still on the roadmap? It was supposed to be before TGP so I'm not sure if it fell off or is now in phase 2, or is coming sooner. I believe they'd have to get the bomb heading and impact angle sorted to implement this, so I realize it's a pretty big task.

Known issue. The wind correction is backwards. Enter the mission's wind into the CK37 while airborne and your BK90's will land on target. Here's a good video showing what's going on:

Agree. Would like to see things like this and the dive-toss mode implemented before the fancier stuff like JDAMS, but I'll take any excuse to try something new out in the Harrier.

Same here. Can't exit mission without crashing DCS.

Some bugs unfinished I see: 1. Bomb wind correction not modeled 2. Wind correction backwards for bk90 3. No full campaign 4. Spa mode has several bugs (can't select m points for display for instance) However, the Viggen can perform all its missions. I can't speak for the warbirds, but aside from the ka50 and a10 it's probably the most complete module in my opinion. I'm sure there's way more that needs to be done that people can add, but those are my hot list

https://www.2ndmaw.marines.mil/News/Article-View/Article/522816/avengers-unleash-wrath-with-historic-jdam-strike/ 6th paragraph from the bottom Actually looks like it depends more on the JDAM modeled than the aircraft

Just note that the guide says TWS follows the tracked target altitude. This is how it's SUPPOSED to work, but currently doesn't. Zeus already said the fix will be in the next update, but I wanted to point out in the meantime, TWS will drop the tracked target if it changes altitude out of the 1-bar TWS scan

I felt the same way. I was really disappointed with the Mirage and delayed flying the Harrier. Harrier is one of my favorite modules. I think it's in relatively great shape. Some days I do nothing but circuits on the Tarawa it's such a joy to fly.

Love it. Can't wait to get my hands on that. The JDAMS are just a cherry on top. However, I don't see anything about being able to drop JDAMS in TOO with the TGP. There was an article I posted to this forum indicating the Harrier was unique in being able to hand off accurate target coordinates to JDAMS from the TGP. And the Marines conducted several strikes using this method.

Whoa, what is the CAS page? That looks cool.

I want to be perfectly clear. I did not have a great deal of problems using the old system. It was easy to use and I had no trouble at all hitting what I was aiming at. I simply believed the implementation was inaccurate. I hope you get what you want. I think a TAKT input for that is an excellent compromise.

The sight still jumps. That's expected behavior if you're not at the safety altitude. If you had an option where the steering order is switched to altitude along with the pipper, this would probably work even better for you. The problem before wasn't really that pitch or altitude was used, it's that the pipper used one logic and the steering order used another set of logic, so the transition could be sloppy.

Sounds like at the moment of release you had some slight negative g to hold the pipper on target or started your pull up too late. It is pretty cool watching 16 500lb bombs land on an area the size of a postage stamp! I will try starting my dive much later and lower. Chuck's guide shows a dive at 700m with the pop up starting about 7km from the target. Doesn't show the resulting angle but it's probably around 25-30 degrees. That profile worked before the sight change updates.

When I say put the target at the top of the HUD, I mean when you are diving, the sight will disappear entirely. Keep the target towards the top of the HUD anyway. As you get closer, the sight will appear from the bottom and creep up the HUD. Maneuver the sight on target, hold the trigger, and make sure to keep the pipper at the beginning of the desired string (this is a bug, it should be the center, but the pipper in DYK indicates the beginning of the string). When the wings appear, pull up 4G. You'll roughly follow the steering order if you do this and you should get the interval you selected. Again, not sure if this is how it's supposed to be done. I'm not sure how you're achieving a 30 degree dive angle at only 500m AGL. Seems like you'd have a half-second before you were in the frag pattern diving that steep that low.

I am talking about that, too. Before it would appear above or below the target and respond to altitude. Now it responds to pitch. Either way, it was giving altitude direction, the method by which it occurs is what changed. The old sight, if you were at 300m with low drag bombs with medium safety altitude and designated a target, the sight would jump below the target, commanding climb. As you climb, the nearer to 400m you got, the more the sight crept up to the target. When you were within about 25m of the safety altitude, the sight would "stick" to the target. In this way, the sight before was still giving steering correction, just by altitude instead of pitch. I'm not against putting a TAKT option in for this, but the sight was indeed providing correction before, just in a different way.

You never go above 500m to dive on a target? Is that normal? Seems like that would be a very shallow dive. What distance do you typically pop up and what dive angle do you use?

You're not supposed to MOVE UNRESOLVED BUGS TO THIS SECTION!!!! :megalol:

The "finger checks" are a series of checks initiated by raising the appropriate number of fingers to the plane captain/ground crew for the check you are going to do. For instance, if I hold up 5 fingers, that signals we will be performing the wet acceleration check.

The old style DID give steering commands if you weren't already within 50m of the commanded altitude, it would be above or below your target, commanding a dive or climb respectively.

I can confirm I don't have this issue in Open Beta, so I doubt it's in stable, either. When you look at your Akt Pos output, what does the last digit read? If it isn't 0, you have some drift. However, I am curious as to what you mean by this: "I mean while I'm arriving the zone, the ring moves to the the target, but when I fly over it!" Are you saying the target ring is in the correct position before you arrive, but wrong when you as you near it, or the other way around?

You're right, that ring should disappear. It's just the waypoint marker. The steering order doesn't appear until 2:38, which is when I pull and hold the weapon release trigger.

Right, but it's either CR or it isn't. The whole point of CR is you don't time your trigger pull once your target is set. Before the PLAN sight changes, it worked as consent to release, and the sight would appear as long as you were about 3 deg or more nose down. Now the sight won't appear at all unless very specific parameters are met. I can still hit what I'm aiming at, I find if I get to at least 1300m AGL and keep my target at the top of the HUD, the sight will creep from the bottom and some slight pitch adjustments will get you on target. I'm not saying it's right or wrong, but it was changed when the PLAN sight was changed, and it wasn't documented anywhere how it's supposed to work now and what the changes were. It leads me to believe that the changes may be unintentional. Also, because of this behavior, the moving target method no longer works then turned on via TAKT input. I know it isn't oft used, but it was functioning before.

When the PLAN sight changed, DYK sight changed as well. DYK is no longer consent to release, and the sight doesn't appear until very late in the attack. With high dive angle attacks, the sight often doesn't appear from the bottom of the HUD until too close to the target for release. Does anyone know how it's supposed to be used now? Used to be able to see the site in much wider array of altitudes and attitudes.

Same exact thing happened to me. Interestingly, firing cue also appears to be occurring WAYYYY later than it ought to. Also on open beta here.