ggerman2862 Posted March 24 Share Posted March 24 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? Link to comment Share on other sites More sharing options...
razo+r Posted March 24 Share Posted March 24 Did you check that your stick is perfectly, 100% centered before engaging B/RALT? If not, it won't engage. Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted March 24 ED Team Share Posted March 24 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
markom Posted March 24 Share Posted March 24 Also, make sure your radio altimeter warning altitude is set. If it's not set, RALT won't engage. Link to comment Share on other sites More sharing options...
PawlaczGMD Posted April 29 Share Posted April 29 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. Link to comment Share on other sites More sharing options...
some1 Posted April 29 Share Posted April 29 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. 1 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 Link to comment Share on other sites More sharing options...
PawlaczGMD Posted April 29 Share Posted April 29 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. Link to comment Share on other sites More sharing options...
Recommended Posts