Main Hydro, Engine Virbration, Fire

[Logite]

I made a custom mission and whenever I start to take off or fly this happens (in order)

 

ELEC ON ACCUM

COMMON HYDRO

HI VIBR LEFT ENG

 

Then the rotors stop and the engines start to catch fire. What might be causing this? What steps can I take to diagnose these problems myself in the future?

[EtherealN]

Track file?

[Logite]

I apologize in advance for the headbanging.

client-20100522-164041.miz.trk

[Frederf]

Governors not on or in some sort of test mode?

Excessive dust consumption?

Battle damage?

[EtherealN]

Well, startup procedure is the automatic one, so nothing much funny there (one note though: try not to do anything while it's running, you can confuse the script, though that's not what happened here). I started a server and ran it myself with a manual startup, and it happened again.

 

Noticed you have birds at 100%. Odds at that nailing often aren't too big though, but try placing that at 0%. I never actually checked if birds affect the shark though.

Edited May 23, 2010 by EtherealN

[EinsteinEP]

Double check that you don't have any failures set in the mission editor!

[Frogfoot1606687865]

I just tried your mission, (at least start up and take off) with no problems. However I used manual start (not 'Win + Home' shortcut). It may be usefull if you were to post another track, but this time scan the guages/switch positions during start up rather than moshing :D !

Cheers Tom.

[sobek]

Noticed you have birds at 100%. Odds at that nailing often aren't too big though, but try placing that at 0%. I never actually checked if birds affect the shark though.

 

The intakes of the Ka-50 engines are too small to ingest birds, supposedly, therefore it is not modelled for the Ka-50 AFAIK.

[AlphaOneSix]

The intakes are big enough to ingest birds, but there is not a straight path into them, which helps immensely.

[Vecko]

I made a custom mission and whenever I start to take off or fly this happens (in order)

 

ELEC ON ACCUM

COMMON HYDRO

HI VIBR LEFT ENG

 

Then the rotors stop and the engines start to catch fire. What might be causing this? What steps can I take to diagnose these problems myself in the future?

 

In the pit everything is looking just fine, this is very strange and mystical failure. Or maybe is some strange bug with birds settings...If this happen only in this mission,delete and create new one... ;)

[sobek]

The intakes are big enough to ingest birds, but there is not a straight path into them, which helps immensely.

 

I guess additionally, the speed envelope of a helo makes it easier for the birds to prevent a collision.

[Logite]

I'm still mystified as to why this is happening, like a few of you. Could it be that the engineers forgot to put air in the tires? :P

 

I don't have any failures set afaik. Failures are set in the triggers window no?

[winz]

Nope, failures got set in the failures window, its one of the subviews (waypoints, loadout...) when you got the helo selected. And from looking at the mission file, I'm pretty sure its failures.

From textfile editor:

 failures = 
   {
       hydro_common = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 5,
           id = "hydro_common",
           mm = 4,
       }, -- end of hydro_common
       hydro_main = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 2,
           id = "hydro_main",
           mm = 1,
       }, -- end of hydro_main
       asc_a = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 10,
           id = "asc_a",
           mm = 3,
       }, -- end of asc_a
       asc_p = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 1,
           id = "asc_p",
           mm = 1,
       }, -- end of asc_p
       r_engine = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 3,
           id = "r_engine",
           mm = 2,
       }, -- end of r_engine
       asc_r = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 1,
           id = "asc_r",
           mm = 0,
       }, -- end of asc_r
       l_engine = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 2,
           id = "l_engine",
           mm = 3,
       }, -- end of l_engine
       asc_y = 
       {
           hh = 0,
           prob = 100,
           enable = true,
           mmint = 1,
           id = "asc_y",
           mm = 2,
       }, -- end of asc_y
   }, -- end of failures

[Frogfoot1606687865]

Hmm, interesting. It seems that you can't set failures on aircraft set to 'Client' only 'Player', has it always been like this?

Also If I edit the mission and change the A/C from Client to Player, and then look at the failure modes they are unchecked.

Something fishy here.

 

Tom

[Frogfoot1606687865]

Logite, if you edit the mission and change each of the 3 'client' Ka50's to 'player', then save the mission, then change them back to 'Client', then save the mission it seems to reset the failure modes to false.

I just tried it an it seemed to work.

 

Tom

[Logite]

Interesting. Also checked out Frogfoot's response and I have to say, I never set failures to begin with. Quite odd.

[Logan9773]

The techs are slacking off. Have them beaten, then try again.