finnish3r

No mention of this being fixed in today's changelog

Would it make sense to mention it in the designer notes?

Just flew the mission for the first time and was confused because there was no EA-6B Prowler (Astro 55) in the air. Looking at Tacview afterwards, it looks like it spawned as a FA-18C Hornet. Running DCS-MT 2.9.1.48111 Open Beta. No mods. Tacview attached. PS. Botched the mission by attacking COUGAR too early and not having SLAMs left when I was supposed to do so. So went in for guns and then ended mission early... Tacview-20231117-131715-DCS-RODF M12.zip.acmi

Thanks for the reply baltic_dragon! Just to clarify, am I supposed to engage the HOT BOX after Sluggo fires the HARMs? Also, since Vaicom is not really needed for these campaigns, is it sufficient to just not run it to see if that fixes things or does Vaicom has its roots deeper in DCS configs that might cause the bugs?

I'm also having issues with M10. We engage the SA6s successfully with Sluggo and then turn towards LUKE. Sluggo calls the HAT BOX and engages with two HARMs. Then he just casually flies over LUKE through AAA fire and heads west, no comms. At some point he decides to head for the Tartus SA3, but apparently it's not active and he then just turns towards the boat. I'm running MT 2.8.8.43704 and my only mod is VAICOM. Tacview attached. Tacview-20230903-185855-DCS-RODF M10.zip.acmi

Just VoiceAttack and SIMPLEX shaders.

Just finished the campaign and I can confirm that I wasn't able to use ACLS successfully in at least any of the CASE III missions. ACLS seems to work just fine, Mode 1, tadpole and CPL P&R all come on just as they should, but in the groove the jet drifts away from the centerline. Could this be related to the wake turbulence issue reported preventing successful ACLS coupled landing on the Hornet? I have wake turbulence off in DCS settings, but at least I got wake turbulence from the tanker. Is it forced on in the campaign?

After dropping bombs on the Souria, 420 (Matrix) decided to stay on ASL course and deflect into Iran (or at least keep on going until crashing). Was able to finish the mission nevertheless without 420 on the wing anymore. Two Tacview tracks attached, was running DCS 2.8.1.34667.2 Open Beta. Tacview-20230124-173347-DCS-Persian 15 Saving the World.zip.acmi Tacview-20230124-181624-DCS-Persian 15 Saving the World.zip.acmi

I'm having the same issue with Hornet and Supercarrier. Everything works like a charm until the end but the plane just does not catch a wire. It was reported in another thread to try disabling "Wake turbulence", haven't tried it myself yet though.

This happened to me just now for the first time after Rise of the Persion Lion mission 9. I've attached dcs.log and the debrief log here. Was not using BuzzLine's hot fix. Now I am, let's see if it happens again. dcs.log MIZ9_debrief.log

Thanks for your reply! The problem is universal, not just DCS. The screenshots are from SimAppPro. Windows recognizes the device just fine, but the axis input data appears dead. I guess I could try to disconnect the 4-pin wire to see if that has any effect, but other than that I guess I just need to wait for Winwing to reply. The stick is only a few months old so warranty should cover this.

In the middle of a dogfight my plane pitched full nose down and right roll. I thought I was hit, but the problem persisted when I started a new flight. I quit DCS, tried to recalibrate, reboot but to no avail. I tried reseting to factory config, I tried the IsSyncCalibration fix, updated firmware, connected directly to motherboard, opened the case and checked the 4-pin connector, removed the stick from the base. Nothing helped, the stick is pointing to top right corner and I'm getting no axis data input. All the buttons work fine though. Any suggestions on what might be the problem? I already opened a ticket at Winwing support, but thought I'd write here too while waiting for answer.

This might have been covered here a million times and if so, I apologize already in advance as I’m a newbie when it comes to this stuff. Anyhow, I just recently received my Winwing Orion F18 HOTAS and so far I love it. I would, however, like to bind some DCS comms menu actions to the comms switch on the F18 throttle. Namely, I would like the aft to be “Previous menu” and forward “Exit menu”. There doesn’t appear to be bindings in DCS for these so is there a way to correspond these actions simply to key presses of F11 and F12 on the keyboard somehow? Thanks (and apologies, again if necessary) already in advance!