You want to abide by the 30/30/30 rule:
Not more than 30 degrees off axis
Not more than 30 degrees of bank
Not more than 30 degrees of bank change after track
Posts made by Frederf
-
RE: Those Darn Blinking Crosses
-
RE: HUD display with DelanClip
HUDs don’t have zoom. They are defined in angular position. The image isn’t on the glass; it’s at infinity. You’re supposed to sit at design eye.
-
RE: Hook is not fully retracted
@Tiger-0 said in Hook is not fully retracted:
@Mav-jp said in Hook is not fully retracted:
not a bug, thats a feature
the hook is spring mounted, you can’t retract it from the cockpit alone
Is there any way to get it reset or do we need to reload to do that?
Deploying the hook breaks a bolt. The cockpit switch up will retract it enough to clear a cable on the ground but not return it to the pre-deploy position. There is a heavy spring which presses against the bolt. The hydraulics of the hook apply more pressure and break the bolt.
-
RE: Boresight and Cycling from A/G to A/A
@yop217 said in Boresight and Cycling from A/G to A/A:
In the training manual on maverick, you are asked to boresight, then you leave & go to NAV. It is also requested to CZ right after the boresight operation.
So, from this doc, I do not understand that neither CZ nor leaving A/G mode should delete the boresight.
Anyone could confirm this understanding ?Correct. Boresight is never deleted only overwritten and only when “BSGT” OSB is pressed. It sounds like you either didn’t boresight or the LOSes were mismatched when the boresight was saved.
-
RE: Fragments from the explosion: how high to fly?
Intact cluster would be a cluster that hit the ground intact, i.e. didn’t burst and a high-order detonation. ( https://books.google.com/books?id=omAX-QGXFdMC&pg=PA7 ). This is a worst case scenario for frag hazard.
It should be noted that not all Mark 82s are created equal. Newer warheads have scoring for more consistent frag elements which is more fragments but the big nasty pieces with good ballistic properties more rare. It’s interesting to compare the 1985 Tac Attack table with the 1996 MCH table.
Of course P(hit) threshold is 0.1% which is what is considered acceptable risk. The distances at 1%, 10%, etc. are appropriately closer. The size of your airplane also has an effect. The PH for a B-52 and an F-5 aren’t the same at a given distance.
-
RE: 4.37.3 AIM120 AQUISITION MODEL
Looks like radar (quality of data) has a much larger effect on engagement performance than missile. I have heard that TWS is of a low enough quality to that it is a rule not to use it (outside of needing 3+ or 5+ simultaneous engagement beyond TTS or MTS abilities of course).
I wish I could find the reference but I swear I’ve heard that there is an interpolation of DL updates and seeker info throughout the engagement process. Even when the missile “sees the target” he should still take efforts to blend DL data. Obviously the blend will start DL-heavy and end DL-lite but every DL update is weighed (Kalman filter?). RCS size setting would likely play a role into that blend balance.
Remind me if BMS has RAID. AIM-120 should be able to assign EONs to different missiles to sub-target a cluster which returns as a single track. I know that’s well beyond the already challenging task of a 1 missile, 1 target modeling but it is an interesting notion.
I’m a bit surprised there’s no mention of weighing targets by factors other than geometric location (PRF closure aside). Weighting a contact higher that more closely matches the closure of the DL despite being slightly farther away from the geometrical position seems sensible.
Hopefully for testing purposes there can be a debugging way to specify repeatable “random factors” to at least have a solid representative sample instead of just having to play on the final product and do the statistical analysis, at least before the final draft.
-
RE: Firmware upgrade for warthog throttle - fast slew
Does it work for standard Warthog?
-
RE: how to specify the network card.
@asleepwater lower metric means priority. It should mean if X.X.X.X IP is held by NIC1 then you can choose it
-
RE: TWS vs. RWS
You can take two shots in TTS/DTT (DTT being TTS without search) or up to four shots in MTS for those radars that can do that.
For BMS 3+ targets is where TWS becomes a strict requirement.
-
RE: how to specify the network card.
I remember there being a way to prioritize NICs in Windows. This isn’t the way I remember but adjusting the “Interface metric” to a lower number should prioritize it for traffic.
Looks like the old way is replaced by this new way.
-
RE: TWS vs. RWS
@airtex2019 said in TWS vs. RWS:
no explanation other than random chance, for why RWS would be better than TWS… it should be slightly worse
RWS SAM should be superior to TWS
-
RE: IR Missiles Basic Training
Set the AIM-9 into “BORE” to ensure that the seeker when caged is aligned to the airplane boresight (or the HMCS when used). “SLAVE” is to slave to the radar LOS. You can set this on the SMS format and holding the enable switch will alternate to the opposite selection while held.
AA missile types can be changed hands on by a long press of the MSL STEP switch.
-
RE: Naval warfare - is the AGM-65G best weapon on F-16 with no HARPOON capability
“The AGM-65G has a ground-selectable LAND/SHIP switch which allows the missile to use different algorithms in order to bias the aiming point to cause the greatest damage.”
It’s behind a little door on the missile. I don’t know if the F is superior compared to a ship-configured G but the G does have a ship mode.
-
RE: Maddog Launch.
It’s called “visual AIM-120 launch” in the manuals. The idea that you’re chucking missiles out BVR may be tactically valid but isn’t supported by the language of the books.
I feel that outside of desperate circumstances shooting low Pk missiles is not a good primary strategy unless that’s the only hope against some superior enemy that other teamwork or traditional BVR positioning has failed to achieve.
-
RE: Az/El HMCS Align
There should be no problem engaging the fine adjust modes while not being centered although I admit that I always am. The fine adjust is just nudging the coarse calibration to “more perfect”. In theory a quality coarse adjust can be perfect. Do make sure to hold your head as still as possible when the coarse adjust is in process. I think it averages out your head motions and will fail if they have too much deviation but it can’t know if there’s any actual error, i.e. if you keep your head still but point entirely the wrong way.
I wish I could look over your should when you have these problems because I’ve done dozens of these calibrations with only rare to none issue.
-
RE: Az/El HMCS Align
You can’t align outside of NAV master mode. Normally you do all 3 steps on the ground. There shouldn’t be a problem just doing coarse and then XY/roll later but it’s not my habit.
-
RE: TD box in DTOS
The term is “ground-stabilized”. In the pre-designated state the TD can be slewed (relative to the FPM) and designated which causes it to be ground-stabilized. Once ground-stabilized it can be refined further by slewing. There is no “locked” where it’s not slewable.
Slewing in DTOS requires that the HUD be SOI. There’s little reason that HUD is not SOI but when in doubt refer to the “*” symbol on the HUD.
-
RE: Loss the function of one of the POV hat
@igorry The 5 values have somewhat non-obvious relations.
NumOfPOVs: Total number of POV, valid values are -1, 0, 1, 2. In this case you want the maximum, 2.
POV1DeviceID: ID number of the controller device which POV1 takes input from, valid values are -1 and then 1 through the maximum ID count for devices. The ID for your device can best be discovered by looking in the SETUP section inside Falcon BMS and opening the drop down menu. The list will be: keyboard, deviceA, deviceB, deviceC, and so on. The ID number is the device’s placement in that list and because the keyboard is #1, the minimum practical value is 2 corresponding to the first device listed immediately below keyboard.
POV1ID: ID number of the POV belonging to the indicated device to assign to POV1. The DirectX API allows for multiple POVs to be defined per controller but in 99% of cases the first POV (POV0) is the only one. Normally use value “0” to choose the one and only POV from that device.
POV2DeviceID: Device ID number that will provide the input for POV2 (see POV1DeviceID)
POV2ID: POV number from the device indicated above that will provide input for POV2 (see POV1ID)An example set of values:
set g_nNumOfPOVs 2 // Two POVs
set g_nPOV1DeviceID 2 //First joystick
set g_nPOV1ID 0 //0th POV from first joystick
set g_nPOV2DeviceID 5 //Fourth joystick
set g_nPOV2ID 0 //0th POV from fourth joystickThe confusing thing is DeviceID starts counting effectively from 2, 2 being the first ID after “keyboard” and POV_ID begins counting at 0, 0 being the first POV.
-
RE: Datalink and AI
I may have remembered old behavior or if bad memory. I thought that IDM assignment was an explicit “attack my target” command. Currently it is not doing that. I will check if it has any effect on AI target choice if more than one is available.
Attack my target/targets are also for AA context.