AstonMartinDBS

Did you already try this @captain_dalan?

Looks great!!! Thanks for your neverending try to further improve your already excellent work!

The tables are based on official data from ED. For further details see the information in the first post in the linked thread.

I just was wondering, but I didn't make that claim. It was @FoxOne007:

Shouldn't the current view settings in the mission "Persian Gulf Super Carrier Case II Recovery" for the Hornet result in a Case III Recovery? View range at sea level is clearly < 1 NM.

I have absolute no issues with Win 10 x64 (Build 19044) nVidia 516.59 TrackIR 5.4.2.27545

Please realize, that the Hellfire is an Anti-Tank-Weapon. And for exactly that reason I guess, that Hellfires have never been tested vs. larger vessels IRL, so there is propably not enough data available to finetune their damage vs. ships. And please don't doubt the words of @Raptor9 - he's a real AH-64D Pilot and knows what he's talkin' about.

Frequency should be 251.45, not 251.54 But I cannot confirm right now, if 251.45 is working.

Trying to sink larger ships with Hellifres is as unrealistic as destroying bunkers with AMRAMMs. @DmitriKozlowsky obviously still doesn't realize, that DCS stands for Digital Combat Simulator, what means that it isn't comparable with an arcade game, where you can destroy buildings with a hand gun for instance.

So you've solved your problem, right? If not, here's the working mission: RAT_UN9249.miz You can extract the script from the mission file, if you open it with 7-Zip for example.

Upload your mission and we can check for errors, please.

Kann @Groove diese Mission-Editor-spezifischen Design-Probleme direkt an das Entwicklerteam weiterleiten oder müssen wir das im Bug-Forum für den Mission-Editor erledigen?

https://www.digitalcombatsimulator.com/en/support/faq/repair/

Das schaut mir eher danach aus, als ob das Textfeld um ein paar Pixel zu klein ist, was dazu führt, dass das "W" von der rechtsbündig angeordneten Statusmeldung "Warte bis das Fenster geschlossen ist..." abgeschnitten wird.

@Furiz: I'll create a special table, if someone can provide a full overview of all thread codes which are included in the HDS-Mod. Needed data: Display Name RWR code DED ID I don't include mod-based data in a core-based table for the exact same reason which @Minsky already clarified in the following posting:

I didn't add those threads so far, because they're not listed in the official thread table. Can you provide any additional information to those threads? In particular I need the (full) Display Names and the correct RWR codes. Thanks.

This known bug has been already reported: George should disable ATT/ALT hold before he begins to manouver the AH-64D.

That was my first thought as I saw this screenshot: @DmitriKozlowsky: Have you ever tried to reduce your three-button-bindings to a single button? Just for testing purposes... What AI issues are you talking about exactly?

...and A-4E-C and Hercules. If you remove those two from the mission, I'll take a look.

@skywalker22: Note that the declination depends not only on the global position but also on the date/time. When the declination (between magnetic and true) is +5, then you have to subtract 5 from the magnetic to calculate the true heading. That's how I understand declination, but I may be wrong.

I'm not an expert, but except the missing livery definitions (you only defined the a320skins, but not the others) I can't see any syntax error. Can you upload your sample mission containing the RAT script, please? Maybe there is an issue with the triggers.

Any news about the progress of the bug fixing? Nearly three months are gone in the meantime...

Thanks again for your excellent work @Minsky! I really love your well designed sheets

You're right. The bug has been fixed. I'm also unable to reproduce the issue in the current OB. Of course, sorry for that. I've assumed, that you've overlooked the thread. As I've been aware, that this cosmetic only issue has an absolute low priority, I'm surprised now, that it has been already fixed in the meantime.

If it looked like one of the following sample videos, your issue might be related to this known bug, which is still present. As I've observed, the issue appears only in certain conditions, usually in the dawn at a specific time frame and/or altitude of the sun: