Jump to content

Recommended Posts

Posted

Hey guys

 

I only use three basic buttons for the F-14 autopilot - autopilot toggle, (bound to button 26 on TMW throttle), autopilot reference (button 3 on VFX stick with TMW base) and autopilot altitude hold (one of my toggle switches on the TMW throttle).

 

However, as of today's patch, toggling autopilot no longer locks my aircraft in it's current direction, and I also can't get altitude hold to work. I've tried rebinding the buttons, no difference.

 

Is this a new bug?

Intel 11900K/NVIDIA RTX 3090/32GB DDR4 3666/Z590 Asus Maximus motherboard/2TB Samsung EVO Pro/55" LG C9 120Hz @ 4K/Windows 10/Jotunheim Schiit external headphone amp/Virpil HOTAS + MFG Crosswind pedals

Posted

I used at least autopilot engage switch and it worked. Check your speed and SAS channels.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

Thanks for the tip. It seems using the emergency autopilot disconnect paddle stops it engaging properly thereafter (I only started using the paddle as of yesterday). However, if I switch off my autopilot via the autopilot toggle switch, it's all fine. Any idea why this might be?

Intel 11900K/NVIDIA RTX 3090/32GB DDR4 3666/Z590 Asus Maximus motherboard/2TB Samsung EVO Pro/55" LG C9 120Hz @ 4K/Windows 10/Jotunheim Schiit external headphone amp/Virpil HOTAS + MFG Crosswind pedals

Posted

Another tip is to use anything with "emergency" in its name only in emergency. Also there's a bug which doesn't let you use autopilot switch binding after messing around with SAS switches even when they are set correctly. Only manual switching with mouse works then.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...