AstonMartinDBS

Thanks for clarification @NineLine. I am familiar with these posts @Silver_Dragon, I just missed an official announcement, that the Hornet already left Early Access.

In the DCS E-Shop the Hornet isn't marked anymore as "Early Access" as is still the case with the Viper, for example: When and why did the Hornet leave the "Early Access" state, as there are still several planned features, which are currently not implemented? Thanks.

This is just your opinion and doesn't reflect that of the community for sure. I'm actually a very patient person and haven't complained about delays so far. Since we're waiting for an update since nearly six weeks and the patch announced for today has been pushed back by a week (at least), I would like to give my opinion: The last noteworthy feature updates for the F/A-18C, F-16C, AH-64D or the SC have been released more than three months ago. Instead bringing the already released modules out of early access status, ED seems to focusing it's resources to the release of more and more new, unfinished content (CH-47F, MiG-29A, Afghanistan, Iraq). The next feature update for the AH-64D was announced by Wags in an interview with Casmo as "very soon" for May or June 2024. The last AH-64D feature update has been delivered in December 2023. I hope you don't expect that the community really believes, that ED does not move many resources from developing existing early access modules to announced and/or pre-purchaseable modules like Afghanistan, when you let us wait more than five months for LINK, C-SCOPE and ZOOM for the AH-64D. Unfortunately, I have lost my trust and will no longer support ED by (pre-)purchasing early access modules, as long as ED doesn't change the current strategy. This is my opinion.

The original mission is bugged and obviously wont get fixed by ED. Did you already try one the user modified, working versions of this mission from the postings above, like PG AH-64D MountainCOIN (fv21).miz for instance?

You can find the autosaved trackfile usually here: %USERPROFILE%\AppData\Local\Temp\DCS\LastMissionTrack.trk

The Ramon Airbase ATC is not responding at 39.900 MHz. Communication via 251.500 MHz and 119.200 MHz works as intented. Tested with A-10C II SN A-10C-II Ramon-ATC-Comm.trk and F-14B SN F-14B Ramon-ATC-Comm.trk. I'm not sure if there are similar issues with other ATCs, I've only tested it with the Ramon Airbase ATC.

Did you set the Intercom Mode selector to the desired radio? 1 = VHF 2 = UHF 3 = FM Watching this UH-1H radio tutorial may helps you.

See

The official sources haven't been updated since several month. Maybe @BIGNEWY can provide an updated sheet again. If you're looking for the AN/FPS-117 codes: 210 - AN/FPS-117S 211 - AN/FPS-117 DomeS Source: https://docs.google.com/spreadsheets/d/1p77yaLQJaUMbAIKJDKX5iMN5N5qm_Qqt_dJNyJjLQtw/edit#gid=0

Same here. No issues - at least in SP.

Sofern die Rechnung für den HOTAS noch vorhanden ist, würde ich den Defekt einfach mal über den Thrustmaster-Support reklamieren. Mit etwas Glück bekommst du den defekten PinkySwitch - auch nach Ablauf der Gewärhleistung/Garantie - kostenlos ersetzt.

Try to reproduce your issue and upload a short track of your try, so we can take a closer look.

Check your bindings for the RAID/FOV/FLIR button and make sure that the DDI displaying the FLIR has SCS priority, which is indicated by the little diamond in the upper right of the DDI. I've tested it right now - changing FLIR FOV and switching CCD/IR works as described.

Super, vielen Dank! Dann sollten die TPR unter meinem Schreibtisch also Platz haben.

Da ich in diesem Thread bislang leider keine Antwort auf meine Frage über den Platzbedarf der Thrustmaster TPR erhalten habe, versuche ich es mal hier im deutschsprachigen Forum: Auf der Produkthomepage von Thrustmaster lauten die Angaben 45,6/33,6/41,5 cm (Länge/Breite/Höhe), die auf dieser Grafik angegebenen Abmessungen weichen davon aber deutlich ab: null Wie viel Platz benötigen die Pedale denn tatsächlich, wenn man den vollen Ausschlag der Pedale in alle Richtungen berücksichtigt?

I replayed the track with the same results (4/4 GBU-38 missed). Then I tried the mission at an altitude of 5k ft and didn't touch the TGP - result: 4/4 GBU-38 missed. After the release of the 4th GBU I used the TGP to observe the target area, as I noticed, that the TGP was lookin' about 10 m offset of the CZ. There must be something wrong with the coordinates. Please take a closer look. CA F-16C TGP offset.trk CA F-16C GBU-38.trk

I think about purchasing the Thrustmaster TPR as a replacement for my TFRP and have exactly the same question about the dimensions. Do you have any further information in the meantime @Eugel? Do the published dimensions on the Thrustmaster website (45,6/33,6/41,5 cm - l/w/h) consider the full limits of movement?

You just have to hold down the left mouse button, until the wiper has reached the parking position.

Thanks for the update @Rudel_chw, this command works!

v0.7.2 available: [PLT] COMM setup adjustments after implementation of COMM presets (DCS Open Beta 2.9.0.46801); [PLT] step 67 changed from [PageUp] to [Num+] to avoid the 'Low Rotor RPM' warning;

If you're using the default keyboard bindings to move the power levers into the "FLY" position, I suggest to use [Num+] instead [PageUp]. [Num+] moves both levers smooth, while [PageUp] brings the power levers instantly from the "IDLE" to the "FLY" position, which results in the described "Low Rotor RPM" warning. And you can use [Num-] To bring the power levers smoothly back from "FLY" to the "IDLE" position (instead [PageDown], which does this instant).

It's possible that this was the case. It happened two times in two different missions at Syria. I'm tryin' to reproduce.

Well, it seems that George learned to avoid VRS, but now he sometimes cannot manage to obtain a hover and continues flying at speeds of 20 to 40 IAS. I'll open a new thread fot this issue as soon as I have a short track.

FYI: I've tested the IA free flight mission at Syria right now and had absolutely no issues.

I don't use any of the known workarounds since several weeks and the MT version of DCS runs fine in about 10 to 20 sessions, but at some random point the issue occurs again. I wasn't able to find out any pattern for the appearance of the issue so far. Sometimes it appears even after a cold started system. For this reason I can understand, that it is hard for the team to address the issue.