Jump to content

Recommended Posts

Posted

Just getting back into BS (now BS2) after a long time. Either the game is confused, or I lost my mind. I can't take off, or gain altitude with the throttle levers in auto, or max without the rpm warning beeps going. Warning only stops by pushing down on the collective. :confused: Thanks for any help.

Asus ROG Z390, I9 9900K , 32 GB DDR4, EVGA GTX 2080 Ti , Win10 64, Rift CV1 & S VR

Posted

Are you ramp starting of starting on the runway? If you ramp started do you advance the power levers (sorry forgot their name) on the far left side of the cockpit? You need to use either the page-up or page-down to adjust them, forgot which.

Posted

Ramp, or runway does the same. Played with page up/down works like it should. I can take off in idle, or govern with no warning beep.

Asus ROG Z390, I9 9900K , 32 GB DDR4, EVGA GTX 2080 Ti , Win10 64, Rift CV1 & S VR

Posted

if you look at the left side of the throttle, there are two yellow levers. they are moved with pg-up and pg-dn. they have four positions which are, from bottom to top, Idle, <some sort of middle-speed setting>, governed, and Max. you want the throttle set to Governed for normal flight, and Max under emergency conditions such as one engine failed. a quick way to verify which position you are in is that in Governed setting, the levers rest against the detent wire, and on Max the wire is pushed up out of the way.

Posted

Hi ShuRogal According to the manual, I should have it in auto ( notch) for normal operation.

 

At IDLE mode are usually performed startup procedures and most of the systems functional tests.

 

 

GOVERNOR FAIL is needed in case of failure of power turbine’s RPM governor to avoid engine (power turbine) overspeed.

 

 

AUTO is the main mode during normal operation of the powerplant. All flights must be performed at this mode, except for specific emergencies.

 

 

MAX mode is intended to ensure maximum power of one engine in case of failure of the other engine.

Asus ROG Z390, I9 9900K , 32 GB DDR4, EVGA GTX 2080 Ti , Win10 64, Rift CV1 & S VR

Posted
... with the throttle levers in auto, or max without the rpm warning beeps going. Warning only stops by pushing down on the collective. :confused: Thanks for any help.

 

 

What the others have said, but it sounds to me like you're forgetting to turn on the engine governors before take off? Right side wall panel, near "back right".

 

Or post a trk :D

Posted
Hi ShuRogal According to the manual, I should have it in auto ( notch) for normal operation.

 

At IDLE mode are usually performed startup procedures and most of the systems functional tests.

 

 

GOVERNOR FAIL is needed in case of failure of power turbine’s RPM governor to avoid engine (power turbine) overspeed.

 

 

AUTO is the main mode during normal operation of the powerplant. All flights must be performed at this mode, except for specific emergencies.

 

 

MAX mode is intended to ensure maximum power of one engine in case of failure of the other engine.

 

 

beg your pardon for the confusion, i was saying "governed" to refer to the "auto" position (because that's what auto is, the governer controls it)

Posted

quite strange .. .

check this out

when you set throttle from idle to auto check that the rpm gauges reach 85% ( i hope to remeber the correct value )

when raising the collective check the gauge of the blade inclination if it is working.

If you are in correct rpm and inclination of the rotor blades works ... what can be? to heavy loaded maybe? don't know. Try without external loadout.

hope it helps

Posted

Altitude is a deciding factor in helo performance. At what altitude ASL is your pad? Try at sea level as well.

The KA-50 has a hover ceiling of 4000 m... Which should do for most locations of course, but performance drops significantly at altititudes well below 4000 m.

 

Another idea: check your game controller calibration. Use RCTRL + enter to check the in-game flight controller positions.

[sIGPIC][/sIGPIC]

  • CPU i7 4970k @ 4.7 GHz
  • RAM 16GB G.Skill TridentX 1600
  • ATX ASUS Z97-PRO
  • DSU Samsung 850 PRO 256GB SSD for Win10, Plextor M6e 128GB SSD for DCS exclusively, RAID-1 HDDs
  • GFX Aorus GTX 1080 Ti 11GB Xtreme Edition, ASUS ROG Swift PG279Q, 27" with G-Sync, Oculus Rift CV1

  • HID TM HOTAS Warthog + 10 cm extension, MFG Crosswind pedals, TrackIR 5, Obutto oZone

 

My TM Warthog Profile + Chart, F-15C EM Diagram Generator

Posted

You should really post a track, or else we'll have to keep guessing.

 

Another guess :): did you check the position of the low RPM switch on the collective? It's used for autorotation; when set to low RPM, the rotor RPM gauge should indicate ~83% whereas normal operation should be at ~87% IIRC. It's somewhat unlikely that this is the cause, but who knows. It would match the symptoms.

Posted

I have it now. Part my piloting, part axis for collective calibration. Too much, too fast. Thanks for all the suggestions. :thumbup:

Asus ROG Z390, I9 9900K , 32 GB DDR4, EVGA GTX 2080 Ti , Win10 64, Rift CV1 & S VR

  • Recently Browsing   0 members

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