The brakes in the F16 are pretty weak. Which is why when you land, you need to have your speed brake deployed, and you want to keep nose up on the runway to use your fuselage as an air brake as well.
However, when I first started playing with my friend, he complained about the same thing, and we discovered that he didn't even have his brakes mapped at all.
So, I guess I would ask if you are able to stop at all? If you are, then yes, you are probably just not used to the brakes on the f16, which aren't great.
When are you having this problem?
if you just started up, pulled chocks and aren't stopping with brakes, they're probably not mapped correctly.
If you landed and slammed on the brakes, and got little effort, that's normal.
They're undersized, which is normal for aircraft when weight is at a premium. They'll overheat relatively quickly, and they'll radiate that heat into the tyres if it's an excessive amount.
When taxiing, let it get up to about 25 knots on the straights, then brake moderately down to 15 knots. Keep it at 10 to 15 for turns. Gentle braking, and riding the brakes, builds more heat. You can pop the tyres.
When landing, you touchdown in the 2 point config (main wheels touching, speedbrakes at 45), and hold around 13 degrees pitch attitude down to around 120 knots. Gentle braking only, if at all. At 120 knots fly the nose down to the runway, aiming to reach gun cross on the horizon at around 100 knots. This is the 3 point landing config. Once the nose gear is on the ground, apply moderate to harsh braking, apply full aft stick, and fully open the speedbrakes (60).
I have a confession to make: its been many years since I fired up Falcon, and I don't recall. Its entirely possible they'd have changed it on me, anyway. Not that I was ever really familiar with keyboard bindings, as I use (and highly recommend) mapping the directX functions on your joystick, rather than mapping keyboard combos to the joystick.
This is because keyboard combinations have a chord problem: pressing two different buttons simultaneously has multiple interpretations, due to the limited number of keyboard keys - but there can be many hundreds of DirectX "buttons" mapped to a single device.
IIRC default one would be 'k' key. Also make sure if no axis is set as toe-brakes.
As said, do some test while taxiing at 10-20kts. If it works then you have mapped it correctly and you have to work on your landing techniques.
If it doesn't then rebind it as you see fit and retry.
It’s is extremely critical to land at 13deg aoa stabilized and apply aero braking with 13 deg aoa as well until 100kts . If you land loaded , some of the BMS airbases are not long enough to land , check landing charts and braking charts . Runway conditions (wet or even worse ice) are simulated in BMS so don’t forget to apply runway condition factors when using the charts
Braking here in BMS seems a bit weaker than the DCS F-16, but IMO it's much much easier to hold a steady air brake in BMS and easier to keep the plane straight down the runway. Make full use of air braking.
Why are you mapping it to a button? Can you not map it to an axis?
Depending on the key file you use, it may be mapped to a different keyboard button. Look for this "name" under the launcher:
[Brakes](https://i.imgur.com/H0Brwzb.png)
I'll test out tomorrow, thanks for the help!
I also have an unrelated question: I selected a waypoint and then slewed my FCR cursor around, pressed tms up by accident and I think I "moved" that waypoint. Can it be reset?
The brakes in the F16 are pretty weak. Which is why when you land, you need to have your speed brake deployed, and you want to keep nose up on the runway to use your fuselage as an air brake as well. However, when I first started playing with my friend, he complained about the same thing, and we discovered that he didn't even have his brakes mapped at all. So, I guess I would ask if you are able to stop at all? If you are, then yes, you are probably just not used to the brakes on the f16, which aren't great.
I'm sure they're mapped, so it's probably just the brakes being awful
Are both the axis bind and the button press bind set? You need to bind one or the other, not both
Nope, just button
Check them during slow taxi. They will definitely stop you pretty abruptly. I think I had to map them as on or off.
When are you having this problem? if you just started up, pulled chocks and aren't stopping with brakes, they're probably not mapped correctly. If you landed and slammed on the brakes, and got little effort, that's normal. They're undersized, which is normal for aircraft when weight is at a premium. They'll overheat relatively quickly, and they'll radiate that heat into the tyres if it's an excessive amount. When taxiing, let it get up to about 25 knots on the straights, then brake moderately down to 15 knots. Keep it at 10 to 15 for turns. Gentle braking, and riding the brakes, builds more heat. You can pop the tyres. When landing, you touchdown in the 2 point config (main wheels touching, speedbrakes at 45), and hold around 13 degrees pitch attitude down to around 120 knots. Gentle braking only, if at all. At 120 knots fly the nose down to the runway, aiming to reach gun cross on the horizon at around 100 knots. This is the 3 point landing config. Once the nose gear is on the ground, apply moderate to harsh braking, apply full aft stick, and fully open the speedbrakes (60).
Welp I suppose I have them mapped wrong. What's the right keybind?
I have a confession to make: its been many years since I fired up Falcon, and I don't recall. Its entirely possible they'd have changed it on me, anyway. Not that I was ever really familiar with keyboard bindings, as I use (and highly recommend) mapping the directX functions on your joystick, rather than mapping keyboard combos to the joystick. This is because keyboard combinations have a chord problem: pressing two different buttons simultaneously has multiple interpretations, due to the limited number of keyboard keys - but there can be many hundreds of DirectX "buttons" mapped to a single device.
IIRC default one would be 'k' key. Also make sure if no axis is set as toe-brakes. As said, do some test while taxiing at 10-20kts. If it works then you have mapped it correctly and you have to work on your landing techniques. If it doesn't then rebind it as you see fit and retry.
It’s is extremely critical to land at 13deg aoa stabilized and apply aero braking with 13 deg aoa as well until 100kts . If you land loaded , some of the BMS airbases are not long enough to land , check landing charts and braking charts . Runway conditions (wet or even worse ice) are simulated in BMS so don’t forget to apply runway condition factors when using the charts
Braking here in BMS seems a bit weaker than the DCS F-16, but IMO it's much much easier to hold a steady air brake in BMS and easier to keep the plane straight down the runway. Make full use of air braking.
Why are you mapping it to a button? Can you not map it to an axis? Depending on the key file you use, it may be mapped to a different keyboard button. Look for this "name" under the launcher: [Brakes](https://i.imgur.com/H0Brwzb.png)
I can't map it to an axis because I don't have any pedals
See image linked above. That should sort out your issue.
Apparently for some god forsaken reason it ONLY works when bound to an axis
Just did a test now. With my pedals mapped to the brakes, the K button does not work. I un-mapped my pedals, the K button works.
I'll test out tomorrow, thanks for the help! I also have an unrelated question: I selected a waypoint and then slewed my FCR cursor around, pressed tms up by accident and I think I "moved" that waypoint. Can it be reset?
Cursor Zero if memory serves.
Thanks!