ggerman2862 Posted March 24, 2024 Posted March 24, 2024 After the latest update, whenever I try to engage either BALT or RALT, I get an immediate Master Caution indication, warning tone and an AUTO PILOT indication on the the left DDI and neither hold mode will show as being engaged. All other AP hold modes (ATT, CPL, HDG) work as intended... It's only the altitude hold modes that are not working. All was fine prior to the FM update. Thoughts?
razo+r Posted March 24, 2024 Posted March 24, 2024 Did you check that your stick is perfectly, 100% centered before engaging B/RALT? If not, it won't engage.
ED Team BIGNEWY Posted March 24, 2024 ED Team Posted March 24, 2024 Hi, please check your controls are calibrated, and if possible attach you track replay showing the problem. I've tested and not seeing a problem with mine. thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
markom Posted March 24, 2024 Posted March 24, 2024 Also, make sure your radio altimeter warning altitude is set. If it's not set, RALT won't engage.
PawlaczGMD Posted April 29, 2024 Posted April 29, 2024 On 3/24/2024 at 12:09 PM, BIGNEWY said: Hi, please check your controls are calibrated, and if possible attach you track replay showing the problem. I've tested and not seeing a problem with mine. thank you Same issue as here: It is caused by not perfectly centered stick, but we think this should be looked at, as there is zero allowance for stick deflection. Doesn't seem correct/realistic. 1
some1 Posted April 29, 2024 Posted April 29, 2024 2 minutes ago, PawlaczGMD said: there is zero allowance for stick deflection. Doesn't seem correct/realistic. I agree. The band for autopilot activation is so narrow, it causes issues with most high end sticks without firm centre detent or large deadzone in the middle. Other aircraft in DCS don't have such issue. I couldn't reliably activate the autopilot in the Hornet with VirpilT-50 base, and I still can't with Vpforce. 2 Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro
PawlaczGMD Posted April 29, 2024 Posted April 29, 2024 4 minutes ago, some1 said: I agree. The band for autopilot activation is so narrow, it causes issues with most high end sticks without firm centre detent or large deadzone in the middle. Other aircraft in DCS don't have such issue. I couldn't reliably activate the autopilot in the Hornet with VirpilT-50 base, and I still can't with Vpforce. Exactly, it is not just narrow, I think it is literally zero for some AP modes. I cannot engage ACL without a deadzone no matter what I do. This cannot be realistic, it's very dangerous. The allowed deflection to engage should probably be similar to the deflection that auto disengages the AP.
UrgentSiesta Posted March 10 Posted March 10 On 3/24/2024 at 6:09 AM, BIGNEWY said: Hi, please check your controls are calibrated, and if possible attach you track replay showing the problem. I've tested and not seeing a problem with mine. thank you I just had this problem on a new build computer with a fresh install of DCS & Hornet (and an old TM Warthog HOTAS). Thanks to advice in the other linked post, I'm able to work around it by just giving a *slight* jiggle to the joystick Pitch just after hitting BALT / RALT. I haven't run into this problem on any of the many other DCSW modules I have. Seems like Hornet AP might be just a touch too sensitive...?
Chacal_IX Posted March 12 Posted March 12 It would be nice if the F-18's autopilot were less sensitive and we didn't have to add a dead zone around neutral. I find that with a dead zone, in-flight refueling is much more painful. It would be a good thing if this problem, which has been with us from the start, were finally solved. 1
gulredrel Posted April 1 Posted April 1 Got this today in same mission when I was unable to set SEQU1 to AUTO. I thought it had something to do with having flown a mission on a different map in the same DCS session before. I I tried to replicate but it worked in next missions I loaded in new DCS session (both AUTO sequence and BALT mode). Strange behaviour.
DD_fruitbat Posted April 3 Posted April 3 On 4/29/2024 at 8:16 AM, some1 said: I agree. The band for autopilot activation is so narrow, it causes issues with most high end sticks without firm centre detent or large deadzone in the middle. Other aircraft in DCS don't have such issue. I couldn't reliably activate the autopilot in the Hornet with VirpilT-50 base, and I still can't with Vpforce. This. 1
PawlaczGMD Posted May 11 Posted May 11 After getting the Moza FFB base with self-centering, this issue is solved without needing a deadzone. Still it's a bit silly that it's not a software special option in the Hornet, or something like that.
Recommended Posts