Very interesting presentation with details about engagements during Allied Force and an even more interesting comment from Claw regarding the AIM-120 and RWR around 1:19:50:
Best posts made by Bowser
-
MiG killers, AIM-120 & RWR
-
ILS and crosswind
The Dash 1 mentiones: “The pilot flies the FPM to the command steering cue to intercept and maintain the localizer course and the glideslope for an ILS approach.” However, when there’s a crosswind the steering cue will not bring you to/keep you on the localizer course (verifiable on HSI and visually). Is this intended behaviour or a bug? It’s clearly visible with higher cross winds.
-
RE: Radar braking lock often
@Tumbler31 I’ve observed it in all radar modes. The most interesting is when going from TWS track file into hard lock, sometimes the lock is lost 4 or 5 times in a row in very quick succession before it will remain. Lock breaking within a second from hard locking each time.
Is there any difference between hard lock from RWS and hard lock from TWS?
-
RE: Korea Training Theater (including CATMs that can simulate missile fire)
@Geraki @chihirobelmo Will there be a release for 4.36 U3?
-
Speed caret bug
On the old forum was a thread about a bug in the speed caret:
https://www.benchmarksims.org/forum/showthread.php?41677-Speed-carret/page2&highlight=speed+carretIt was mentioned that the bug has been identified and will be fixed in 3 to 4 weeks but it is still present in the latest release. Hope it will be fixed in the next update.
-
RE: Jan Has F-16 LV6 Update packs
@cougar56th How to make the 'Exhaust angle" text disappear in the top right corner? It’s present for all models in KTO I’ve tried so far.
-
RE: ILS and crosswind
See picture, the ILS bars line up OK but the command steering cue is off to the right (while looking at the HSI I should be a tad more to the left even). When following the tadpole it will take you to the touchdown point but not on the localizer course when there’s crosswind. Can any of the devs confirm this is a (known) bug?
-
RE: Unexpected HARM behaviour
@Mav-jp said in Unexpected HARM behaviour:
Primary Targets :
if Sam system is loaded : Load the FCR and the EWR next
If a FCR is loaded : Load the FCR and the EWR next if FCR belongs to a SAM system
if a EWR is loaded : Load the EWT and the FCR next if FCR belongs to a SAM system
load the threat directly and alone if not part of a SAM systemIf this is how the real thing works OK, but the second line does not make sense to me. For example, I’m on a SEAD mission and spot a SAM launch in the distance. I’m not illuminated myself and I don’t have any further info as to determine the type but I do want to suppress/destroy it. From intel I know the enemy has SA-6 and SA-3, so it has to be either one of them. In this case I’d like to have my HARMs set up to only look for the FCRs of both systems and not any possibly accompanying EWRs. Or at least have the priority like: SA-6 FCR as primary, SA-3 FCR as secondary, SA-6/3 EWR as tertiary.
-
Wheels effect upon touchdown
I’ve noticed an interesting effect on touchdown when landing in (heavy) crosswind conditions. When coming in crabbing and de-crabbing just before touchdown with proper cross controls, aligned the jet with the centerline, wings level (or upwind wing slightly down) and smooth touchdown, the aircraft suddenly turns massively in upwind direction, whilst keeping rudder deflection. I’ve never experienced this in any other sim nor in real life. It seems there is a big discrepancy between the aerodynamics modeling of the jet in the air vs when in contact with the ground without smooth transition. Any ideas on this? Is it modeled that the grip of the wheels slowly transitions from 0% to 100% upon landing?
-
Hung stores
Even with the ‘possible fix’ in one of the updates I keep getting hung stores while I shouldn’t have (no over speed/over G etc, pickle button held for the correct duration). Can you PLEASE fix this, BMS is not fun to fly anymore this way.
-
RE: Hung stores
@Seifer said in Hung stores:
@Bowser hi, sorry about this. Be sure that we are working hard to undertand this one. It is still not clear why it happens, though.
Is there a temporary fix that can be applied? Or change the code so a short pickle will not result in a hung store until the root cause has been found?
-
GBU-24 and AI
The release distance of GBU-24’s of AI wingmen are significantly smaller than ownship. Flying level around 20k feet, 350 kts CAS I can release them around 8 nm while AI releases around half that distance! Verified this multiple times flying wingtip formation of AI wingmen.
Also since 4.34 AI always seem to release LGB’s at 350 kts CAS. Mil power release as in previous versions was better in my opinion for greater standoff distance
-
AI not releasing AG weapons
I’ve encountered multiple occasions in which AI will not release AG ordnance (all in a simple TE flying level at around 20k feet and assigning them a ground target with AG radar or TGP with the ‘Attack target’ command at around 20 nm):
- Multiples times after AA combat, after I had my wingmen rejoined in formation and ordering them to attack they all went straight for the deck and made an 180 degree turn to never come back (with GBU-24’s still on the pylons).
- One time after an initial ground attack with GBU-10’s which went fine, then have my wingmen rejoin in formation, order them to attack again and they just keep flying straight without dropping anything (while still having LGB’s)
-
Radar braking lock often
I’ve noticed in BMS for a while that the F-16 radar often breaks lock time after time on non-maneouvring, non-beaming and non-jamming targets, even when they are within 20 nm. I’m talking fighter sized targest. I wonder if this is realistic?
-
RE: Hung stores
@Mav-jp said in Hung stores:
@Bowser said in Hung stores:
@Mav-jp said in Hung stores:
Make sure you use DX for pickle and not emulated spacebar
I have been using a HOTAS Cougar with the following code: BTN S2 /H SPC for many years. Why would it make a difference when using DX?
Because the cougar and foxy are a piece of shit ( I own 2 of them)
Use DX for pickle, trust me
I was more hoping for a technical answer.
Anyway, I’ve two Cougars myself and have been using them for years without problems. If the issue is with the input device I should have experienced weapons not releasing way before 4.36 which is not the case, considering that the delay before weapon release has been around for a while.Furthermore I’ve verified the proper operation of my sticks many times with a key tester and they work OK.
Also I’ve noticed that a hung store almost never happens when launching air to air missiles and almost only when releasing AG ordnance. If it was input related, I’d expect it to happen with all weapons with delayed pickling. And to make sure: the jet is never over-G’d or oversped and I always confirm that I hold the pickle button for over 1.5 seconds (way longer even) and that REL is visible continuously for that time.
I’ve also experienced a couple of times now that regular MK-84’s get hung while releasing them in CCIP without delay cue, so they should come right off upon pickling (one pair, no interval), instead they go hung…