BMS is nearly perfect. The only thing I would like to see added in a future version is an AI JTAC to improve CAS missions.
Envoyé de mon D5803 en utilisant Tapatalk
BMS is nearly perfect. The only thing I would like to see added in a future version is an AI JTAC to improve CAS missions.
Envoyé de mon D5803 en utilisant Tapatalk
I’m replying here because I have just read a testimony of three former US officers about air interdiction in WWII, Korea and Vietnam. According to them the accuracy of unguided bombs has never been enough to strike a target the size of a bridge if dropped from an altitude that keep the attacking plane safe from SA-7 for instance. Even with the F-111 the amount of planes that needs to be committed to that kind of target is enormous if they are only equipped with unguided ordnance. They are strong advocates of guided ammunitions (and especially laser guided ammunitions because of their reasonable cost).
We need to remember that as good as the computer is, it does not take into account fabrication differences that may alter the trajectory of a bomb far from what it has predicted neither does it account for the density of the air or the strength of the wind or its direction along the flight path of the ammunition (just because those parameters can’t be precisely measured). At the end the CEP may be as large as 350 ft (that’s not that bad considering a 12 000 ft drop) and it’s not enough for a lot of targets to be hit with a reasonable probability (vehicles, bridges, ammunition depot, aircraft hangar, landing stripes, ships, bunkers…). That’s why I think all western air forces have transited to using almost exclusively PGM.
An other consideration is collateral damages. They have become unacceptable after WWII for Western Air Forces and therefore each time a target is near inhabited areas they need to use PGM because they can’t take the risk of a computer miscalculating area elevation for instance or the dumb bomb CEP.
I have the same problem. Me, others friends try but, sometimes laser flashing and the bombs don’t hit the target. Laser combat, code set… and I think a bug…
I have experienced the same thing. It happens when the laser does not stop flashing after pickle (no matter what laser time is set, I’ve tried 10s, 16s, 24s… when the bug occurs it doesn’t matter what duration is set).
In order to get rid of the bug I have reinstalled BMS and it may have solved the bug though its randomness make it difficult to track.
High termination criteria is Husky, i.e. missile (radar) goes active earlier for high aspect/closure targets. Nominal is Pitbull, i.e. missile relies on data-link for longer before it switches on it’s own radar.
I have difficulties to understand you here.
In the definition given in both the BMS documentation and the irl doc, it’s only linked to the missile energy during its endgame. I don’t see why PRF of the seeker would be involved. The notion of HTC (which is also linked to Rpi in the documentation) remains pertinent even for close range shot with a target fleeing me (low closure speed, short range, the missile should not use HPRF). Furthermore, at range above Ropt the missile might go husky too so I don’t quite see the link between HPRF and HTC.
ASC = Attack Steering Queue. Just put it in the centre of the ASEC (big circle) to ensure optimum loft for your BVR shots.
I know ;), I think Frederf just mixed up DMC and ASC in its first answer.
TLAs are hard to keep track of.
OK DMC is a number expressed in degrees 0-180 which represents how much turn is required by target to spoil (degrade) the shot kinematically. It only appears in the range R-PI to R-TR. We expect that DMC value just barely outside R-TR is equal to his aspect because at this range the assumption is that a turn to 0 aspect is marginal kinematically.
At farther ranges the amount of turn required by the target to degrade the shot decreases from his aspect (the maximum that will display) down to zero at R-PI. The value always assumes target turns in the unfavorable direction.
And to correct what I said before R-OPT and R-AERO both assume ideal launch azimuth and elevation. It’s R-PI that assumes current conditions. Thus we expect R-OPT and R-PI symbology to be equal positioning when we aim the airplane ideally (no post launch missile steering required) at the moment of launch.
Thank you for your answer. The way DMC was explained I thought of it as a pure function of the AA of the target, I understand know that it’s also a question of termination criteria.
Remain my question about what exactly is a high quality termination criteria.
Hello everyone,
I was going through the -34, and reading the AIM-120 part, I notice a few things I would like to have more informations on.
When looking at range indications on the DLZ it says that Ropt is the same thing as Raero but a shot at this range will end up with high termination criteria instead of nominal termination criteria. And the only definition for high termination criteria is that a missile with high termination criteria has more energy than a missile with nominal termination criteria. I’ve been looking in IRL F-16 MLU Part 2 manual only to find out this same definition.
My question is : Is there an other definition somewhere (something that’s not relative to an other abstract quantity) ?
Second question : How do you use the DMC (digital manoeuvring cue) ? I thought the aspect of the target displayed on the HUD would be enough information to establish the probability of my missile to hit the target so I’m wondering if there is an other use to it.
I thank you in advance for your answer.
Well I’m not a RL F-16 engineer but from an engineer POV it’s simple, the system has no way to know if the failed Handoff is because of bad Boresighting or from a faulty Maverick, for example. So it registers a fault just so someone will check it later anyway.
True enough.
@Leech Thanks for this complement of information.
Well… basically there is a chance that the Maverick Handoff will work even without boresight procedure, but it’s a pretty low chance.
That’s an interesting answer. Thank you. I am know wondering why the engineers decided to display an error message while indeed it’s not really an error but the result of a failed attempt. However this is another matter.
Thank you all for your answers.
Nowhere in the manual does it say its mandatory to use this function. It says it must be done to improve precision and shorten the time to handoff.
“The AGM-65 mounting procedure induces an unknown amount of misalignment of the launcher. This misalignment must be removed to improve accuracy and shorten the time required to achieve a handoff.”
As I understood it if you don’t do the boresight procedure then it’s only longer to achieve the correlation.
And it seems that the game does not do the procedure when you are taking a plane already started up.
Hello all,
I’ve tried using the hand-off function with AGM-65D and I’m having a hard time understanding what’s happening.
I have my missiles ready and uncaged, TGP in IR-point on a target. Then the message “hand-off in progress…” is displayed but, after that, my Master Caution switch on and I can read “Avionic fault TGP HAND” on the fault panel. Am I missing something or is this a bug ?
It might be related so I’m writing it down here; I often have an “IFF fault” message while starting my plane, something I had never seen before.
Thank you in advance for your answers.
Assuming you install linux turbojpeg libraries, yes the displaysreceiver should work. However keyboard capture and shared memory will NOT work.
Like you say, the reason keyboard capture and shared memory does not work is because I used win32 APIs through JNA (simpler than JNI). Shared memory has equivalents in linux, yes, so that could be doable in a patch. Global keyboard capture could prove……tricky though, I do not handle linux very proficiently I’m afraid ^^
Then I’ll try to make the receiver work on linux. Thanks for the answer.
The installation pdf says windows only so I assumed it would not work on a linux environment.
Hi !
I would like to know if a linux version is possible ? Especially for the receiver part of your software.
Hello everyone,
After talking with jcenzano about shadowplay and display extraction while in fullscreen I decided to try GPT. Thought I have way less image stutering and no random HUD image display on my extracted MFD thanks to GPT, it causes some BMS crash. Here are one of my crash log so you can look at it. PC specs below:
Windows 7 Professional 64 bits
Intel Core i5 4670k
8 Go DDR3
Geforce GTX 760 OC
Falcon is installed on my SSD
Thaks in advance for your help.