Jump to content

Recommended Posts

Posted

I'm sure this must be an easy fix and I'm doing something obvious, wrong . . . but when I hover, I've started to drift relentlessly to the left.  No idea why.  Any assistance gratefully accepted!

aka MadMonk; Windows 10, 64 bit, Radeon 6800XT gpu, Ryzen 5 5600 cpu, 32 gig ram; Samsung 2TB EVO SSD, Thrustmaster Warthog throttle and stick, Saitek combat rudder pedals; Oculus Rift.

Posted

No wind.

 

 

aka MadMonk; Windows 10, 64 bit, Radeon 6800XT gpu, Ryzen 5 5600 cpu, 32 gig ram; Samsung 2TB EVO SSD, Thrustmaster Warthog throttle and stick, Saitek combat rudder pedals; Oculus Rift.

Posted

Will do.  Away from game computer.  Check back in a couple hours please.  The problem is this:  I overfly my targets, use the pedals to turn, then no matter what I do to compensate, the chopper continues to drift slowly in the direction of the turn and I can't stabilize for a shot.  I'm sure I'm doing something simple, wrong.

aka MadMonk; Windows 10, 64 bit, Radeon 6800XT gpu, Ryzen 5 5600 cpu, 32 gig ram; Samsung 2TB EVO SSD, Thrustmaster Warthog throttle and stick, Saitek combat rudder pedals; Oculus Rift.

Posted

Heading hold is on, and your pedals and cyclic are centred (or at least trimmed where you intended them to be) as shown in the controls indicator?

I can think of nothing heavier than an airplane
I can think of no greater conglomerate of steel and metal
I can think of nothing less likely to fly

Posted

Here you go.

testtrk.trk

aka MadMonk; Windows 10, 64 bit, Radeon 6800XT gpu, Ryzen 5 5600 cpu, 32 gig ram; Samsung 2TB EVO SSD, Thrustmaster Warthog throttle and stick, Saitek combat rudder pedals; Oculus Rift.

Posted

Thanks, razo+r; actually I've been doing that all along -- using the three standard autopilot channels -- which is why I was surprised and frustrated when this started.  I've tried it with and without flight director too.  After recording the track I posted, I then tried again, this time explicitly giving the "hold heading" command on top of the three already active channels.  That seemed to work, but I may be so screwed up at this point that I'm missing something basic.

aka MadMonk; Windows 10, 64 bit, Radeon 6800XT gpu, Ryzen 5 5600 cpu, 32 gig ram; Samsung 2TB EVO SSD, Thrustmaster Warthog throttle and stick, Saitek combat rudder pedals; Oculus Rift.

  • Solution
Posted
42 minutes ago, franx said:

Thanks, razo+r; actually I've been doing that all along -- using the three standard autopilot channels -- which is why I was surprised and frustrated when this started.  I've tried it with and without flight director too.  After recording the track I posted, I then tried again, this time explicitly giving the "hold heading" command on top of the three already active channels.  That seemed to work, but I may be so screwed up at this point that I'm missing something basic.

Well, in the track you posted, the 3 Channels, with exception of the ALT channel, were turned on just after you took off and then they were turned off after you flew forward.

So, unless that was what you actually did, check your controls if you by any chance have mapped these buttons to anything unwanted, and then also try to use the HOVER mode in addition to the autopilot channels.

  • Recently Browsing   0 members

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