EagleA25

Just an FYI and as an update, I had the same problem develop after the latest update. I use the Throttle Friction Control Slider Axis as the Flap handle and suddenly the range became shorter, so when selecting the flaps fully up, the sensor would not recognize it as fully up, ergo, the wing sweep would stop at 55 Degrees. After adjusting the curve all is good...

Awesome! Thanks for this! Really appreciated!

Awesome... Thanks Mr. Big

Hey everyone... I'm almost sure not to be the first to ask, but... any chance to animate the Hold-In-Place-Hooks during closing and opening of the Canopy? Would look awesome! Thanks

So, there was a post by Le0Kong a few years ago where he published some Registry Edits for the X65F, which like the Rhino has a MiniStick; one post even has a RegFix for the X52. The link is here, but it's an old post, and the RegEdit for the X65F is not working anymore. I have a feeling that it's got something to do with the latest driver versions by Saitek. Any Registry Wizards here wanna take a shot? I'm a humble moron and have no clue what that sorcery is all about...

Hey guys, thanks for reading this post. I (still) fly with an old Saitek X65F and previously had used Le0Kong’s Registry Mod for DCS to detect the Throttle Ministick. Due to work I was out of the game for a while and even had to rebuild my Rig replacing my SSD’s. So, after a complete Windows reinstall the Registry Mod has no effect. I tried contacting Le0Kong directly, but he seems busy and hasn’t responded… I’ve tried pretty much everything, from registry modding to MadCats changing all options, but to no avail, unfortunately. Anyone have any idea what else I could do to make DCS recognize? Edition Windows 10 Pro Version 22H2 Installed on ‎3/‎19/‎2023 OS build 19045.2846 Experience Windows Feature Experience Pack 120.2212.4190.0 Saitek Driver Version: 7.0.45.0 Saitek Software Version: 7.0.53.6 Thanks in advance! Picnic I CVW-14 I VF-11 I Ripper 105

Yeah, I was about to report the same... and it's called "Lightning Strip"

Hey everyone... Is this thread still active? I couldn't get the ministick to function... Any help available? TIA

Hey DK.... Yeah, I did all what you mentioned... to no effect. Thanks for taking the time to reply, though

Me too; but I want to turn all labels off for good. Any ideas here? TIA!

Kinda agree on this topic… its been a decade! Also, there should be an option where if a human controller is on the frequency, no need for the AI ATC or AWACS to make calls… Just sayin…

Don't have that one and still didn't load...

Man... there's my Dyslexia again... Sorry...! You're absolutely right! SEPECAT! Interesting thing I remember: I saw a few Saudi or Kuwaiti Jaguars coming back during Desert Storm having the Sidewinders mounted ON TOP of the wing... must have been a ME add-on?

There is actually an important difference between “little” and “no warning”. Any Fox 3 shot in TWS will not go “Pitbull” (active) until it is at a pre-determined range, so its normal to not have an active missile warning until that moment. And that depends on your aspect of the missile (if you’re going head-on at Mach 2 with your hair on fire you will probably just get a one-second impact advisory; cranking/notching turns the missile active a lot earlier!). So to sum it up, it’s normal…

Colleague of mine and former F-16 C/D instructor in the Chilean Air Force completely confirmed this is in fact real… He tells me if engine isn’t sufficiently turned by the time Fuel-on is selected, the N2 will not accelerate and it will hung start. so, yeah, thanks ED for the realism!