(new feature?) Aircraft in-flight problems… Avionics Shut down, losing HYD-Pr, etc.
-
Are you doing a Ramp start? Sounds like you may have missed something or the Dev’s put Easter Eggs in U4 and you found ALL of them!
-
I have had a Hydraulic failure shortly after takeoff and had to abort the mission as well as a bizarre electrical system failure in flight. In researching I found out about the “Random Fault” code in the sim. As I recall this can be turned off in the config. I actually leave it on as there’s no point having the “Emergency Procedures Checklist” if you don’t ever have an emergency . . . LOL
-
This sounds like you have some issues with input or install or mod or something isn’t turned on in the plane properly.
While 4.34.4 has random failure, the chances are incredibly small and would not occur as often as you seem to experience.Is your air knob set to Norm?
-
This post is deleted! -
Random failures are off by default
-
Check your falcon BMS config file and see if: set g_bEnableRandomFailures 0
-
Reply to previous replies:
- Starting in Taxi
- I might have accidently activated random fault somehow, will try to figure it out…
Check your falcon BMS config file and see if: set g_bEnableRandomFailures 0
I can’t open your attachment…
I found the bms.cfg file looking into this…Cheers
-
I would hate to think he is getting a random failure every 4th flight give or take 1 even if he had it turned on. ???
-
Now I’m even more confused…
In my bms.cfg, I found it:
set g_bEnableRandomFailures 0 // This enables random failures
I guess I have a ghost in my game who creates failures to drive me crazy…
Oh… forgot to mention that I’m on the Balkans Theater 4.34.3, Flying F-15E-229 but it’s doubtful that’s the source of my problems…
One more thing:
I haven’t modded/modified anything in the game, except installing Balkans Teater 4.34.3…Anw… I’ll give it a try an other day…
-
I fly F-15E as my favorite and I am not having the problems you describe. The main one I have is that the autopilot only works part of the time. I don’t know maybe I get 10 minutes out of it, or I’m doing something that causes it to fall asleep.
-
Oh… forgot to mention that I’m on the Balkans Theater 4.34.3, Flying F-15E-229 but it’s doubtful that’s the source of my problems…
-
Oh… forgot to mention that I’m on the Balkans Theater 4.34.3, Flying F-15E-229 but it’s doubtful that’s the source of my problems…
it most certainly is.
-
Time to fly a few KTO F16 and report back.
Otherwise the ghost would be in your new hardware setup, if I understood correctly.
-
I had a strange occurrence yesterday when practicing Ramp Start Training TE.
When running the FLCS BIT Test I kept getting a ‘FAIL’
I have to confess that the first time I ran the test I had not got the Flyup switch in the ‘down’ position but then I corrected it so all switches on the FLCS panel were ‘down’
Training Manual says to perform the test again if there is a FAIL condition but despite several attempts, it would not PASS
I then tried shutting down the aircraft and followed the Ramp Start Procedure all over again but still got FLCS FAILFinally I exited the TE and ran it over again.
This time I did nothing different (apart from ensuring all FLCS switches were ‘down’) and FLCS BIT passed first time
I checked the RandomFailures flag in cfg file but was definitely set to ‘0’Anyone seen this before?
Was it something stupid that I was doing?
(e.g.if Flyup was not ‘down’ first time around, does FLCS BIT latch to FAIL?)
Is there any way to track such failures in a capture file of some sort in BMS? -
I had a strange occurrence yesterday when practicing Ramp Start Training TE.
When running the FLCS BIT Test I kept getting a ‘FAIL’
I have to confess that the first time I ran the test I had not got the Flyup switch in the ‘down’ position but then I corrected it so all switches on the FLCS panel were ‘down’
Training Manual says to perform the test again if there is a FAIL condition but despite several attempts, it would not PASS
I then tried shutting down the aircraft and followed the Ramp Start Procedure all over again but still got FLCS FAILFinally I exited the TE and ran it over again.
This time I did nothing different (apart from ensuring all FLCS switches were ‘down’) and FLCS BIT passed first time
I checked the RandomFailures flag in cfg file but was definitely set to ‘0’Anyone seen this before?
Was it something stupid that I was doing?
(e.g.if Flyup was not ‘down’ first time around, does FLCS BIT latch to FAIL?)
Is there any way to track such failures in a capture file of some sort in BMS?are you FCC/MMC power on?
-
Sorry for the delayed reply Suhkoi69 thanks for your response.
I do not recall if it was switched on or not, would that make any difference?
There was no warning in the Training Manual for FCC/MCC only that all switches on the FLCS panel should be in the ‘down’ position or it could produce a ‘fail’ on the FLCS BIT -
Sorry for the delayed reply Suhkoi69 thanks for your response.
I do not recall if it was switched on or not, would that make any difference?
There was no warning in the Training Manual for FCC/MCC only that all switches on the FLCS panel should be in the ‘down’ position or it could produce a ‘fail’ on the FLCS BIT“FLCS BIT detected degradation of FLCC MUX interface when attempting FLCS BIT without FCC/MMC power”
-
I had a strange occurrence yesterday when practicing Ramp Start Training TE.
When running the FLCS BIT Test I kept getting a ‘FAIL’
I have to confess that the first time I ran the test I had not got the Flyup switch in the ‘down’ position but then I corrected it so all switches on the FLCS panel were ‘down’
Training Manual says to perform the test again if there is a FAIL condition but despite several attempts, it would not PASS
I then tried shutting down the aircraft and followed the Ramp Start Procedure all over again but still got FLCS FAILFinally I exited the TE and ran it over again.
This time I did nothing different (apart from ensuring all FLCS switches were ‘down’) and FLCS BIT passed first time
I checked the RandomFailures flag in cfg file but was definitely set to ‘0’Anyone seen this before?
Was it something stupid that I was doing?
(e.g.if Flyup was not ‘down’ first time around, does FLCS BIT latch to FAIL?)
Is there any way to track such failures in a capture file of some sort in BMS?Make a “Reset FLCS” and run the FLCS bit test again
-
@Bad:
Make a “Reset FLCS” and run the FLCS bit test again
Thanks guys
However Bad Boy, as Suhkoi69 indicates in his FLCS Caution list above, if the fault occurs due to FCC/MMC Power not applied then “Reset FLCS” will not work.I am fairly sure that during one of my repeats of this TE during this session, that I must have remembered to switch on the FCC/MMC but the FLCS fault came up every time until exited the TE completely (back to the ‘Commit’ stage instead of the “Takeoff” stage. As mentioned in the training manual though, failing the FLCS BIT does not have any impact on the operation of the game.
Stranger still was the issue that I had yesterday.
I had PFLD failure warnings as follows:
1st TE Run:
After engine start:
CMDS DEGR
RWR DEGR2nd TE Run (from “Takeoff” Stage not “Commit” Stage):
After Engine start:
CMDS DEGR
RWR DEGR
Then the engine stopped and I had an “Engine” and “HYD OIL PRESS” warnings on the right Eyebrow Lamps3rd TE Run (also from “Takeoff” Stage not “Commit” Stage):
CMDS DEGRIn all 3 cases I had made sure that Main Power was selected; Fuel Master Switch “On”; Fuel Feed set “Norm”; Air Source set “Norm”
In each case the faults lit up after main engine spool up from “Alt+i” in other words after idle released. From keyboard not Idle Detent on throttle (which is not enabled on my throttle). In each case I had heard the audio ‘click’ after Alt+i and the engine spooled up normally past the 20% RPM.I do not have random faults enabled in cfg file (I checked after the previous FLCS BIT issue)
Maybe I am doing something dumb during my sweeps but I believe that I was being careful after missing the FCC/MMC enabled that caused my first FLCS BIT issue
Nobody else experiencing Random Faults when RandomFaults in cfg is not enabled?
-
Define Commit stage.