AstonMartinDBS

When I replay your track on my MT setup, I see MAP, GMT and SEA modes working normally. Try to repair your DCS installation.

That's really weird. I did some testing based on the stock F/A-18C Mission "Weapons Qualification - AGM-88C HARM" on Caucasus. Initially I thought, the issue occurs only, when the HARM page is displayed on the Right DDI. But after some further testing I observed, that the appearance of the issue is exclusively related to the way, how the HARM page is called: When I call the HARM page via STORES (PB05)/HARM (PB06)/TOO (PB04) all works fine: the threats detected by the HARM sensor are displayed correctly, the different threats are selectable by the "RAID/FLIR FOV select button" and the hand-off works as expected using the "CAGE/UNCAGE button"; But when I call the HARM page via HARM DSPLY (PB09) directly and switch to TOO (PB04) none of the threats will be detected by the HARM sensor or displayed in the HARM page; in this case the label STEP next to PB13 is also missing; I've attached some tracks: CA FA-18C HARM 01 LDDI TOO working.trk CA FA-18C HARM 02 LDDI TOO working.trk CA FA-18C HARM 03 RDDI TOO working.trk CA FA-18C HARM 04 RDDI TOO issue.trk CA FA-18C HARM 07 LDDI TOO issue.trk CA FA-18C HARM 06 LDDI TOO issue.trk CA FA-18C HARM 08 RDDI TOO issue-and-working.trk

I watched/replayed your six tracks (current OB 2.8.2.35759 installed here). At the three tracks on Caucasus each JSOW reached the target area, but some missed the targets close. On all three Syria-tracks I observed the same issue: 1 of 4 JSOWs ran out of energy and dropped ~5 NM too early.

Thanks for your feedback. Check your PM.

Glad to see that you found the source of your issue. Thanks for your feedback!

Here's not the very simplest offline mission, but a working one for testing purposes (based on the SC template for Caucasus). Try this one @Chewmann: FA-18C SC ACLS3.miz

If you provide a track of your attempt, we can see exactly, what's goin' wrong.

Please let us know your solution. This may helps others with a similar issue.

As for all other MAV related functions, like FOV toggle for example, you have to set MAV as SOI to get space or ground stabilize working, of course.

I'm unable to watch the track (requires activation). Try to reproduce your issue with a custom mission on Caucasus. Take this one for example: A-10C II AGM-65H SpaceStabilizationTest.miz Space stabilization definitively works for me: A-10C-II MavSpaceStabilization 3.trk

Had the same problem with the mini-stick on my HOTAS Warthog Dual Throttle until I changed the input setup as follows: TDC slew is still on my analog mini-stick, but TDC depress went to a button on the (right handed) joystick, which gives optimal precision.

Tested again, space stabilization works as shown in Wags' tutorial. Make sure the Maverick Seeker is boresighted. Press and hold DMS forward as soon as the Wagon Wheel Symbol is near target area. While holding DMS forward slew the Maverick Seeker; release DMS forward to lock on a target.

No. The mission is still broken.

Stimmt, danke! Habe mir das in meiner Checkliste sogar falsch notiert. Mein letzter Coldstart mit der Hornet war leider schon etwas länger her.

Zwischen 4 und 5 fehlen noch einige Schritte fürs "Fine Alignment": FA DX/DY: ausrichten = TDC slew übernehmen = TDC depress Uncage FA DROLL: ausrichten = TDC slew übernehmen = TDC depress Uncage Erst danach wird das komplette Alignment mit dem PB20 [ALIGN] bestätigt. Schau dir vielleicht nocheinmal @Wags Tutorial zum HMD-Alignment an: ...und wenn's nicht am Alignment liegt, dann lade bitte ein Trackfile hoch, damit wir sehen können, was du falsch machst.

100 % agree. I see absolutely no reason to configure the TrackIR curves in DCS instead using the native TrackIR software. If you wish you can use my profile, which was originally from @Spudknocker: DCS World.zip. It works perfectly for me since years. Simply extract the profile to %USERPROFILE%\AppData\Roaming\NaturalPoint\TrackIR 5\Profiles and select it in your TrackIR software. You may have to restart the TrackIR software to find the new profile.

As we're still waiting' to get Mountain COIN (another official mission which came with the AH-64D) fixed since months , I'm afraid that ED doesn't have any interest to fix this mission as well. But maybe - or hopefully - I'm wrong.

It was my fault, there's no problem by transferring the elevation from the ME to the planes:

Thanks @razo+r & @ASAP! I think, we've located the source of the issue. The elevation has been proper set to the ground level (36 ft) in the ME. But there might be a problem by transferring the correct elevation of the WP from the ME to the planes. Sorry, my bad. By copying the original F-16C to the F/A-18C and A-10C II for testing purposes the original WP elevation of 36 has changed to 136 - and sadly I didn't double check this on the other planes.

I think we've found the source of this issue. There might be a problem by transferring the elevation from the ME to the planes. Sorry, my bad. By copying the original F-16C to the F/A-18C and A-10C II for testing purposes the original WP elevation of 36 has changed to 136 in the Hornet and Hog - and sadly I didn't double check this on the other planes. There are no issues with the TGP in the Hornet or Warthog.

Great catch - but that's sadly not the solution (as marked by yourself), but the way to the source of the issue. All four WPs have been proper set to ground level (36 ft/~11 m) in the ME (that only counted for the F-16C in the test mission): After manually correcting the wrong transferred elevation of the WPs in the Hornet (HSI/DATA/UFC) the ATFLIR has been perfectly aligned: As the problem occurs in several modules (at least in the Hornet, Viper and Warthog), there might be a problem in the core by transferring the elevation from the ME into the planes. Sorry, my bad. By copying the original F-16C to the F/A-18C and A-10C II for testing purposes the original WP elevation of 36 has changed to 136 - and sadly I didn't double check this on the other planes (see above ME screenshot).

Impossible, the WPs have been placed in the ME, exactly over the four targets and at ground level.

Exactly. Sure, here's the tiny mission file (corrected version for A-10C II and F/A-18C): CA A-10C-II F-16C FA-18C TGP Test.miz

Mission setup: Map: Caucasus Targets: 4 static tanks Hog: each tank has a WP 1 - 4 at ground level Issue: TGP doesn't slave exactly to the WP/STP/Target. The TGP points far offset from the STP (> 20 m) Track: (removed) Note: The same issue occurs in the F-16C (see https://forum.dcs.world/topic/316221-jdam-and-targets-of-opportunity/?do=findComment&comment=5124926) and in the Hornet (see https://forum.dcs.world/topic/316650-tgps-inaccurate/) as well. So the problem appears also in other modules and is might related to the core.

I've done some further testing. Since the same problem with the TGP offset occurs in the Hornet and in the Hog (A-10C II) as well, it might be a problem with the core. There's no problem in the Hornet & Hog, see next answer.