Daniel M Posted July 14, 2012 Posted July 14, 2012 First off I'm flying mouse and keyboard* so that's part of the problem right there...:D The other is i'm normally tucked away safely with my two rotors in the ka-50, so this "high speed" stuff is strange to me. Anyway, when I put on the autopilot in "alt+3" mode, some times the aircraft will continuously sweap back and forth from left to right, and right to left? Am I doing something wrong? *Out of country for another 3 weeks, then back home to my tir +hotas...cant wait
OpusTheFowl Posted July 14, 2012 Posted July 14, 2012 I find the Toad goes into odd banks kinda out of the blue. It might be caused by a bent airframe due to over-G's but I haven't quite figured this out yet nor have I played with trim yet. I bit different than what you posted but of the same thread...
Inseckt Posted July 14, 2012 Posted July 14, 2012 Although the Toad uses AFM, I don't believe soft body physics is involved at this point... Help Beczl with his DCS MiG-21Bis project by Pre-Ordering DCS MiG-21Bis module NOW! CLICK HERE TO GO TO PRE-ORDER PAGE AT INDIEGOGO
BKLronin Posted July 14, 2012 Posted July 14, 2012 Those behaviors were often caused by unsymmetrical loading after weapon release or autopilots trying to stay on course. At least for me. [sIGPIC][/sIGPIC]
Zakatak Posted July 14, 2012 Posted July 14, 2012 Just make sure that the Toad is already flying perfectly straight when you activate any sort of autopilot.
Exorcet Posted July 14, 2012 Posted July 14, 2012 This is normal for aircraft, though in DCS things are a bit more ideal than in real life, for instance no win gusts, so this may or may not be physics related. When does it happen? If you're flying the plane steadily and go into autopilot, any oscillation should be relatively small and eventually die out. Once steady, the plane shouldn't divert from course again unless something happens (accidentally hit the controls, release a weapon, etc). Awaiting: DCS F-15C Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files
Mar Posted July 14, 2012 Posted July 14, 2012 I usually make myself as level as I can and then engage attitude hold before I engage auto-level, this trims it up and stops the autopilot from bouncing the nose 40 degrees up and down, but even that won't work if your AoA is too high. I haven't had any experience with it rolling yet though. From the shadows of war's past a demon of the air rises from the grave. "Onward to the land of kings—via the sky of aces!"
Buzpilot Posted July 14, 2012 Posted July 14, 2012 I find the Toad goes into odd banks kinda out of the blue. It might be caused by a bent airframe due to over-G's but I haven't quite figured this out yet nor have I played with trim yet. I bit different than what you posted but of the same thread... Could be you have axis on other than joystick (on by default), so if you touch brakes on rudder, you move x or y axis instead. i5 4670 - Sabertooth Z87- GTX Titan - Dell U3011 30" - 2x8GB RAM 1800 - Samsung 840 EVO 512GB SSD - Warthog HOTAS - CH Pro pedals - TrackIR5 - Win7 64bit EVERYTHING IS SUBJECT TO CHANGE :thumbup:
Corrigan Posted July 14, 2012 Posted July 14, 2012 Yep, the default mappings are INSANE :D Win10 x64 | SSDs | i5 2500K @ 4.4 GHz | 16 GB RAM | GTX 970 | TM Warthog HOTAS | Saitek pedals | TIR5
OpusTheFowl Posted July 15, 2012 Posted July 15, 2012 I'm going to post his along with a big slice of humble pie... Figured-out what my problem was. The default key-mapping for left rudder trim is Rctrl+Z. The default mapping for time compression (acceleration) is Lctrl+Z. I must have been advancing compression without realizing it thus getting the huge exaggerated inputs... Sorry for wasting your time. ...and yes, I feel like an idiot. :clown_2:
Recommended Posts