Master Caution after firing AMRAAM
-
Thanks for this. I always thought bags = CAT III. I have not checked the caution panel, because normally when I am shooting off a 120 my thoughts/eyes tend to be on the HUD/Radar/6 :).
Will check next time though.
Me too. I thought wing tanks or ground ordnance = CAT III. Centerline tank and/or A-A loadout = CAT I.
Has this been changed recently or was I wrong the entire time? -
Given its been answered, is there a compelling reason to keep things simple?
Well… unless it’ll someday be exported as some sort of data, I don’t see a good reason to write ALL the -2 possible combinations into the code
-
Me too. I thought wing tanks or ground ordnance = CAT III. Centerline tank and/or A-A loadout = CAT I.
Has this been changed recently or was I wrong the entire time?Changed in 4.33 - was as you thought in 4.32, incorrectly.
Well… unless it’ll someday be exported as some sort of data, I don’t see a good reason to write ALL the -2 possible combinations into the code
You make a good point. Seems like a text file could be a good spot to save that sort of data. Personally I like having as much stuff in external config files as possible, myself.
-
Changed in 4.33 - was as you thought in 4.32, incorrectly.
So it was that way in 4.32…. but it was wrong. Gotcha, thanks!
IIRC, having wing tanks in 4.32 and being in CAT I or when in CAT III but going fast enough or pulling hard enough, a strong pull would result in some banging sounds and I always thought that as me stressing the pylons/supports and getting an earful out of my crew chief once back on the ground. The “banging sounds” no longer happen in 4.33?
-
They shouldnt. Realistically, it shouldnt generally end up with any issues outside a great deal of paperwork and increased maintenance workload. Which is not something that can be simulated well in the sim. So you end up with either realistic play by some folks, and unrealistic play by most, OR you put in place unrealistic limitations (4.32 approach for example) to enforce realistic gameplay.
It would be neat if the debrief complained if you exceeded symmetrical or rolling G limits for the stores during the mission.
-
The master caution light will illuminate whenever a individual light on the caution panel illuminates whith the expection of the IFF caution light. Check the caution panel. I bet the STORE CONFIG will be illuminated.
4 AIM120 + 2 AIM9 + 2 wingtanks + pod is a CAT III loadout
3 AIM120 + 2 AIM9 + 2 wingtanks + pod is a CAT I loadoutthis is so frustrated, one missile determine i was FAT.
-
this is so frustrated, one missile determine i was FAT.
It is not about being “fat” or not. You seems to be stuck into a very old conception of the CAT limiter in Falcon4.
Please watch : https://www.benchmarksims.org/forum/showthread.php?18086-F-16-Viper-Cockpit-Tour&p=259825&viewfull=1#post259825
-
It is not about being “fat” or not. You seems to be stuck into a very old conception of the CAT limiter in Falcon4.
Please watch : https://www.benchmarksims.org/forum/showthread.php?18086-F-16-Viper-Cockpit-Tour&p=259825&viewfull=1#post259825
it is a good enough concept to challenge AI, which i deal with 99% of time.
if i was CAT I, i said “c’mon, let’s have a good fight!”. if i was CAT III, i felt like “leave me along, go find another loser to bully”. -
this is so frustrated, one missile determine i was FAT.
Best bit about it is, the BMS dev team do not write the rules about what is and what isn’t CAT3 config on the F-16, they only apply them. Perhaps a vent on the Lockheed forum would be better served?
-
Maybe it could be link to some flutters at high AoA, you don’t know. CAT doesn’t apply a heavy weight. For example on MLU’s, you are in CAT 3 when you took the sniper. Not because it’s heavy ;).