Thank you gentlemen.
I learned the -200 version would be likely damaged when going over 800 KIAS, while the -220 and -229 are able to exceed that speed, having a closed loop control that limits the compressor discharge pressure.
Thank you gentlemen.
I learned the -200 version would be likely damaged when going over 800 KIAS, while the -220 and -229 are able to exceed that speed, having a closed loop control that limits the compressor discharge pressure.
@Mav-jp Thank you for your incredible work on BMS. On the same subject, I have an additional final question:
what is the source of the engine thrust curves showed in the HFFM documentation? I’m talking about the one below (there’s 5 of them in total):
Are they estimated from known performance data? (Acceleration, max speed, etc.)
Thank you gentlemen.
I learned the -200 version would be likely damaged when going over 800 KIAS, while the -220 and -229 are able to exceed that speed, having a closed loop control that limits the compressor discharge pressure.
Good day,
this is a very technical question that can probably only be answered by developers themselves, but I try neverthless.
Consider this chart:
As far as I understand it, the right side of the continuous black lines represent the thrust-limited max speeds, in other words where the max AB thrust equals aerodynamic drag.
Now, as we can see, at lower altitudes (below 22.000ft) the continous line is interrupted by a dashed line labelled “LIMIT AIRSPEED”. This, I reckon, represents the structural limit airspeed, and is the max speed at which the engine (and the aircraft as a whole, per manual) can safely operate, and is equal to 800 KIAS.
Now, from this chart we could deduce that the engine could in theory provide, say at sea level, a thrust which would allow the aircraft to exceed the limit speed of 800KIAS/M1.2. In other words, that the max operative speed at S.L. is not limited by thrust/drag (like it is above 22.000 ft), but by operative airspeed limitations for the engine/airframe.
My question is this: how does BMS model all of this?
In other words, does the engine in BMS produces higher thrust than that needed to reach M1.2 at S.L. (Basically, extending the continous black line in the chart down to sea level)?
Or, does the engine in BMS “loses” thrust below 22.000 ft, in order to match the max attainable speed to the LIMIT AIRSPEED dashed line in the chart?
And, supplemental question, what does the real aircraft/engine do? Would it be able to exceed M1.2 at S.L, with the pilot being responsible to not exceed speed limitations?
Or would the FADEC limit fuel flow (and hence thrust) once the airspeed approaches 800KIAS?
Yes, I know Maddog is not the advised launch mode, I was just practicing. In any case thank you, I was missing the uncage part! Now it works.
Hi there,
I tried shooting an AIM120C (just to try, without any radar contact) in Bore mode, but it doesn’t launch. When I press the pickle button, the fpm flashes and that’s all. Of course the master arm is on.
I tried both selecting “bore” in the AIM120 WPN page, and also holding down the cursor enable button (which sets the AIM120 mode to “bore”), but the result is the same: no launch and fpm flashing.
Do you have any idea?
Hi there, 3 questions on the AA FCR for which I couldn’t find an answer.
What is the caret on the right of the display when in AA radar modes? It changes position when changing radar range. I couldn’t find any mention in the docs, or I missed it. It’s circled in red in the following screenshot:
The STP triangle is quite huge, and if an aircraft is co-located with it, it gets hidden by the big STP symbol. Can it be reduced? Is it so big also in the real aircraft?
Apparently the VSR mode is not working. I tried approaching a Mig 29 both from its six (with a high closure rate), or directly head on, but in neither case any simbol appeared on the VSR radar screen.
Hi udidwht,
I have a slower PC than yours (notebook, i5-2430M @3.0GHz, AMD 6650M 2GB, 4GB RAM). I turned off many performance heavy options and I’m using only 2XAA, but I usually have >60FPS in any of the training missions I tried (still haven’t tried the campaign).
I think you should not have issues with your specs, provided you don’t set all the graphical options to the max, and that you’re not using excessive AA or resolution.
@Red:
By the way, you didn’t say which hotas you use?
I suppose it’s not a cougar, because the cougar can be programmed fully like the real thing, and that’s the best scenario imho
I can’t afford a full HOTAS setup, I use a Sidewinder FF2, but it gives me a total of 27 buttons with the button-shifting function.
Thanks to you too Rabbit, very good advices!
How are you going to be handling looking around? That might require a hat to itself.
I’m gonna probably use FreeTrack (similar to TrackIR).
I would skip the paddle switch as well - it’s nice to have, but not really necessary until you’re doing low-level TFR flights. I’d bind that to wheel brakes instead, so you can easily stand on your brakes while you’re running the engine up at takeoff, and keep your hand on the stick when landing.
I have rudder pedals (with wheelbrakes). So maybe I will keep the paddle switch, since I like to use the autopilot and I find the AP override very useful.
Falcon allows you to make one the pinky button work as a shift. It acts as the pinky button if you press and release quickly, but as a shift button if you press and hold it down, so that may free up an additional button for use.
Yes I know, it’s already included in the 27 buttons count.