AstonMartinDBS

Why you don't provide a short trackfile which shows your problem exactly? Without track we just can guess, what you're doin' wrong... Did you activate the gun via Weapon Action Switch (WAS) Forward on the cyclic or the TEDAC left handgrip (LHG)? Hint: read the AH-64D Quick Start Manual, pages 277 - 279. It's located in your DCS installation, subdirectory \Mods\aircraft\AH-64D\Doc\ BTW: Why do you frequently start a single thread which contains several completely different problems? Your initial post contained two totally different problems: Gun and Rudder. And here you've started a thread about LOW ROTOR RPM warning and a few posts later you've been complaining about the absence of autorotation training missions...

I cannot see any problem with the sensitivity of my TFRP in the AH-64D. If you don't have problems with other choppers I suggest to double check your bindings for conflicts (especially the axis bindings) and proper adjust your trim settings. BTW: You can find my trim settings in this thread (only the cyclic is affected by trim with these settings).

As Raptor mentioned in my initial thread, the IAS value "0" should be displayed in the FLT page, as it does in the IHADSS. Track: 04 CA AH-64D IAS 0 not displayed in MPD.trk

Thanks for your answer. Yes, it is reproduceable: 04 CA AH-64D IAS 0 not displayed in MPD.trk BTW: Maybe @BIGNEWY can move this thread to the correct subforum under this conditions?

Well... obviously nobody knows... Of course, this isn't very important, but I'm just interested if it has been correct implemented.

Did you try to change those settings?

@Raptor9 maybe...?

I can confirm, that trim (binding "Force Trim/Hold Mode Switch - R/Up") with the following settings in the special options for AH-64D won't affect the pedals: After depressing trim I can/have to re-center my cyclic - but I have to leave the pedals in the current position.

Does anybody know if this little detail has been implemented correct or should there be a "0" displayed (as in the IHADSS)?

Make sure, the MAV page has sensor priority (diamond in the right upper corner) Undesignate now you're able to slew or cage/uncage the MAV

The IAS value 0 (zero) is visible on the IHADSS, but not on the FLT page in the MPD. Shouldn't the FLT page act as a kind of mirror of the IHADSS?

Steps to reproduce: obtain a stable hover and engage the position attitude hold mode in the [PLT] seat switch to [CPG] activate George panel set IAS to 40 Issue: Position attitude hold mode doesn't disengage, IAS in the IHADSS stays boxed Effect: It takes > 30 seconds until the AH-64D starts accelerating Solution: Position attitude hold mode should be disengaged when George is forced to accelerate Track: 01 CA AH-64D PositionAttitudeHold George.trk

No problems here. Adding the points works fine for me. Make sure you've done a proper setup for your SHOW pages (T3).

That also happened to me before. The first two points have been totally misaligned, because the INU alignment procedure hasn't been completed. Don't add the TSD points until INU alignment procedure has been completed. Watch this post how to check the INU alignment state: https://forum.dcs.world/topic/297651-how-long-is-the-inu-alignment-supposed-to-take/#comment-4937166

When can we expect the working version of this mission? Can/are you allowed to upload here or do we have to wait for the next DCS update?

You can force Steam to install DCS 2.5.6 (Stable): The second option is to transfer your DCS modules from Steam to the Standalone version (it's not possible to transfer from Standalone to Steam). For further details/restrictions see:

Since this bug obviously isn't caused by the Apache, it should be moved out of the AH-64D forum. Syria Map/Bugs and Problems https://forum.dcs.world/forum/534-bugs-and-problems/ or DCS World 2.7/Bugs and Problems https://forum.dcs.world/forum/253-bugs-and-problems/ would fit better for this issue.

Thanks @pokeraccio. Changing my two other F/A-18C flights in my ACLS test mission to F-16C resulted in my first successful ACLS recovery. Since all my previous attempts failed, I assumed I did something wrong.

Your initial post contained the phrase so I've assumed, this was your announced "long version". Sorry for my misinterpretion. I've just tried to help solving your problem and I see no reason for such useless comments: So if you want to avoid wrong assumptions from other community members define your problem and goal clear.

To fly the AH-64D without issues you shouldn't bind the axis commands/bindings "Cyclic Pitch" and "Cyclic Roll" simultaneously to your stick (which provides real axis inputs) and keyboard (which delivers only a on/off-state). That's the reason for the described input conflicts. If you wanna trim the AH-64D correctly (and as real as possible in DCS) you should use your stick to bring the Apache in the desired attitude and the binding for "Force Trim/Hold Mode Switch - R/Up", which "locks" the virtual stick in your current positon. ...and don't forget to clear your keyboard bindings from the section axis commands. In the "Special" options tab for the AH-64D you can change the settings for "CYCLIC TRIMMER MODE" and "PEDALS TRIMMER MODE" to your preferences. I'm happy with the settings "Central Trimmer Position Mode" and "Pedals without Springs and FFB". I fly with my TM HOTAS WARTHOG Stick@WarBRD Base and TM TFRP.

Thanks for your support @Flappie. I've updated my nVidia drivers in the meantime from 512.15 to 512.59 and watched the track again right now within a fresh DCS session. I was able to reproduce the bug, but this time it didn't have such a massive impact as yesterday (origin of the track): the boxes appeared only for ~1 second, yesterday they filled about 95 % of the screen and were present until I changed the view from cockpit to external (F2). It's very sad that this issue exists. Due to the great visual effects I like to fly missions during dawn or dusk, but this bug appears exclusively in those time frames.

Sadly the issue is still present in the current OB (2.7.12.23362). Setup: Syria, F/A-18C, SC (self made training mission for ACLS) Log: 01 dcs.log Track: 01 SY FA-18C GraphicsIssueDusk.trk In contrast to my previous observations the black boxes didn't disappear in the recorded flight by looking left/right within the cockpit view. Only switching to an external view resolved the problem. Hopefully ED is able to repoduce and fix this annoying issue someday...

No. Each input device is configured separately. Mulitple devices can be used side by side. Just make sure that there are no conflicts - that counts especially for axis bindings.

As it is titled "Unofficial Road to Completion" I'd say: no. You can find the official Hornet Features Roadmap here:

I don't had any issues so far with laser hellfires in the latest OB. I've been able to deliver 12 AGM-112K in my last mission right now. As @Kharrnalready observed you've selected AGM-114L (RF), which isn't implemented yet. Set your missile type to SAL for AGM-114K (button R1 on weapons page) and try again. If this doesn't solve your issue provide a trackfile, please.