steelrfan85 Posted March 3, 2019 Posted March 3, 2019 I have tried using the HSI to set heading and I have also tried to use the heading on the UFC gauge heading select with the semicolon next to heading but nothing seems to respond. Nor does the radar altitude or barometric altitude hold or the attitude hold. I’ve hit the AP and seen the semicolons and nothing responds
KittyVCAW-1 Posted March 3, 2019 Posted March 3, 2019 As per the manual: Autopilot modes listed on the UFC are selected by pressing the Option Select Button next to the Option Select Window of the autopilot mode. When selected, a colon is displayed next to the autopilot name on the Option Select Window. Once selected, pressing the ON/OFF button on the UFC enables the mode. An A/P advisory is displayed on the left DDI when an autopilot mode is engaged. Nobody likes me because I'm unsafe.
imacken Posted March 3, 2019 Posted March 3, 2019 Hmm, interesting. I have never had to press ON/OFF to get the A/P modes to work. The advisories show up on the left DDI just by selecting on the UFC options. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
steelrfan85 Posted March 3, 2019 Author Posted March 3, 2019 I don’t get anything on the left DDI. When I click on baronor radar altitude hold, I get no semicolons. Still heading has semi colons but nothing happens. Not even my ATC. So strange!
KittyVCAW-1 Posted March 3, 2019 Posted March 3, 2019 yeah i went into the game to play around with it and I dont have to press "on" either. Stable version or OB? I'm on OB and used to not get the semi colons for Balt and Ralt but updated today and they work now. Also didn't notice any A/P advisory on the DDI. Will play for another hour or so tonight I'll check everything again. But regardless all A/P modes are working for me. Nobody likes me because I'm unsafe.
jonsky7 Posted March 4, 2019 Posted March 4, 2019 Make sure your control stick is dead centre, maybe add a small deadzone, Hit A/P button on UFC Press round buttons to left of their description to activate that mode semi colon indicates active alt hold modes might disconnect if you're at a high/low pitch angle when selecting, but it still moves for a second or two That's it
steelrfan85 Posted March 4, 2019 Author Posted March 4, 2019 Tried that as well. Not sure the problem.
Scofflaw Posted March 4, 2019 Posted March 4, 2019 (edited) I experience the same as you, sometimes hitting BALT/RALT only turns on AP, and not the ALT hold mode itself. Sometimes heading does nothing as well. Have you tried increasing the deadzone on your control axes? I read somewhere that if the game thinks your controls aren't perfectly zeroed, it won't engage the selected AP mode. Edited March 5, 2019 by Scofflaw run come save me
NahkaSukka Posted March 4, 2019 Posted March 4, 2019 With my T-50 + TM WH grip + 70cm extension it's next to impossible to set BALT autopilot. It usually just turns on and immediately turns off after clicking it. I tried +5 deadzones but sticky felt really wonky after that.
steelrfan85 Posted March 5, 2019 Author Posted March 5, 2019 Update on AP. I created a deadzone. Working well. Now if I could keep my jet on the runway on take off. It’s all over the place. Smallest rudder movement and I’m everywhere like a car sliding in ice
KittyVCAW-1 Posted March 5, 2019 Posted March 5, 2019 i think by adding some curve to your rudder axis would make it less linear and more progressive thereby making minor corrections easier. Maybe a tiny dead zone too. My pedals are super sensitive and just the act of resting my feet on them gave me a minor amount of input one direction or the other. Glad you got your A/P sorted out. Nobody likes me because I'm unsafe.
Sarge55 Posted March 5, 2019 Posted March 5, 2019 What Jonnie2Bad said and check to make sure you've turned off NWS. [sIGPIC][/sIGPIC] i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog
imacken Posted March 5, 2019 Posted March 5, 2019 NWS turns off automatically on take off. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
mkosmo Posted March 6, 2019 Posted March 6, 2019 NWS turns off automatically on take off. News to me -- The NWS indication will remain on until you select gear up unless you disengage it yourself. You sure you're thinking about the correct aircraft?
imacken Posted March 6, 2019 Posted March 6, 2019 Nice to bring news to people! Here you go http://igmack.co.uk/NWS.mp4 Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Slug72 Posted March 6, 2019 Posted March 6, 2019 Now if I could keep my jet on the runway on take off. It’s all over the place. Smallest rudder movement and I’m everywhere like a car sliding in ice I disengage NWS as soon as I push the throttles through the gate; even with a -25 curve I have enough rudder authority to correct minor "drift" during takeoff. i9-9900K @5GHz, Z390 Aorus Pro, 32GB DDR4-3200MHz, EVGA RTX 2080Ti FTW3 Ultra, Seasonic Focus+ Platinum 850W PSU, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, MT deskmounts, Asus 32" 1440p display, EDTracker Pro Wireless, HP Reverb
some1 Posted March 7, 2019 Posted March 7, 2019 I found out that after you press balt and wiggle the joystick a bit around centre, it will activate itself. It seems like it has a very small activation zone requiring stick to be perfectly in the middle, but then after activation the stick can be deflected and it won't disable the autopilot. 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
imacken Posted March 7, 2019 Posted March 7, 2019 What I find strange is that all this works perfectly - as per the manual - for some (like me) and not others. Even with no dead zone, it all works fine for me. I don't get why that should be. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
some1 Posted March 7, 2019 Posted March 7, 2019 Thrustmasters and Saiteks usually have a little deadzone built already inside firmware. If your joy stays at X=0, Y=0 when released then it will work. But if a joystick gives even a little off centre input, which some high end hardware with no centre detent does, there seems to be problem with activating ALT hold. 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
imacken Posted March 7, 2019 Posted March 7, 2019 Thrustmasters and Saiteks usually have a little deadzone built already inside firmware. If your joy stays at X=0, Y=0 when released then it will work. But if a joystick gives even a little off centre input, which some high end hardware with no centre detent does, there seems to be problem with activating ALT hold. But you are using the TM Warthog and seem to have issues. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
some1 Posted March 7, 2019 Posted March 7, 2019 I have virpil T-50. And a bunch of other sticks. 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
Recommended Posts