Bearfoot

Well, you did an excellent job! All the info is at that link, very clearly presented, and with lots of nice, enriched detail! Thanks!

I'm searching through the entire repo though for text patterns, so it should pick it up. The key issue is whether or not I've got (and am understanding) the parameter name correctly. For example. here is a a search through the entire repo for all occurrences of "min_alt"

Thanks. That database has lots of info. It's a little tricky to figure out. I see many unit types have "min_alt_finding_target" (e.g., "SA-11 Buk LN 9A310M1", given as "20", or "Gepard" or "HQ-7_LN_SP", given as "0"), but many others do not (e.g., SA-10, SA-2, SA-6 etc.). Which does not make sense.

Has this been fixed?

Thanks! I did look at that, but it seems the SA-2 information is missing or "TBC"?

Does anyone know where I can find this info? As it relates to DCS of course? Alternatively, I guess if we knew what specific variant DCS is modeling and whether it is modeled accurately, we could look it up here

IIRC this was fixed Good to hear. It was such a fuss sometimes.

Wasn't there a bug where if you WPDSG while TDC is assigned to the ATFLIR, the designation goes crazy? Sky, clouds, random point in the ground, etc. Has this been fixed? Work around is (was?) make sure TDC priority is on some other DDI when pressing WPDESG.

DCS infantry cannot be suppressed. Only killed. They are recruited from solid lunatic stock and are pumped full of angel dust and 1000000% grain alcohol before being sent to the front. They will stand their ground calmly firing at you with laser accuracy even as the entire planet disintegrates around them in a haze of smoke and fire and shrapnel.

Yep. AFAIK, DCS has never had, or ever got around to implementing, any EW shortcut.

For me (and RL might vary), I like the double ugly because: It keeps the left inboard station clear or at least not having a huge fuel tank your view if you have the ATFLIR or some other TGP loaded. It frees up one "smart" (not sure of the correct word) pylon (center pylon can only take dumb bombs, I think, while wing pylons support the full range of ordnance). So you end up with 3 pylons to take the special toys, while a tank on either wing only leaves 2. If I am doing anything on the ground I typically take the ATFLIR, unless it is a totally pre-planned JDAM strike. For a general A2G loadout, I typically carry: Left wing: sidewinder Left outboard: weapon 1 Left inboard: optional weapon 2 (or datalink) Left cheek: ATFLIR Center: fuel Right cheek: AIM-120 Right inboard: fuel Right outboard: weapon 3 Right wing: sidewinder Where: If I am carrying Walleyes: I usually have a Walleye on station 2 and the datalink on station 3. This balances the fuel. Typically Station 8 (and 3, if not occupied by the datalink) is empty or has double rack of AIM-120's if I'm self escorting (or do not trust the AI escort ), or maybe a HARM or something (a little bit game-y maybe ... but hey, it is a game!). For A2A or CAP, I don't typically do the double ugly,I take 6 AMRAAMs (two doubled racked on each wing + 2 on the cheeks), an either 1, 2, or sometimes even 3 (!!! I get thirsty! don't shame me !!!) bags. All the above is within the context of the game. For real life loadouts, you need to speak to someone who knows what they are actually talking about!

Ok, some progress. Adding the following line {action = id2163a_commands.ID2163A_SetMinAlt, cockpit_device_id = devices.ID2163A, name=_("Push to Test Switch"), category = {_("Right Vertical Panel")}}, into "C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua" exposes the control to be mapped to a key in the game, and the control responds. So ... yay! Problem is when assigned to an axis, the axis control acts as an incrementer/decrementer rather than a slider. That is, pushing the axis past the center continuously increments the value until the axis is centered again. And vice versa. For example, setting the axis at 25% does not result in an altitude at 25% the range, but continuously decreases the altitude down to zero and beyond until the axis is brought back to 50 %. Of course, I've tried clicking the "slider" box inside the game in axis tuning for the control, and that doesn't seem to have changed things. So maybe I'm missing something. The "id2163a_commands.ID2163A_SetMinAlt" is defined in "C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\clickabledata.lua" as: elements["pnt_291"] = default_button_axis_extended(_("Push to Test Switch, (LMB) activate BIT checks/(MW) rotate clockwise to apply power and set low altitude index pointer"), devices.ID2163A, id2163a_commands.ID2163A_PushToTest, id2163a_commands.ID2163A_SetMinAlt, 292, 291, 0.1, true, nil, {30, -145}, {0,-60}) Maybe some of those numbers at the end need fiddling, or maybe I need to define a new element ("default_button_axis_limited"?) Is any of this documented somewhere, or does anyone know how it works?

Hi, Currently, the only bindings available to set the radar altimeter RALT bug are: - "Push to Test Switch - CCW/Decrease" - "Push to Test Switch - CW/Increase" Is there way to bind this to an axis? Either a mod or patch or otherwise? (Note: not talking about radar antenna elevation)

Yep, for me too it does not automatically step to the next SLAM-ER station, and have to manually step. Not sure if this is correct behavior or not.

Yep. That's exactly what I described (I think? If not, then I did a bad job of describing it). All the other stuff was just to provide a way for folks to convince themselves that there is, in fact, no hand-off!

(BTW, I'm not saying that this is how it works IRL or is supposed to work. Just that how it works in DCS currently)

What I see in your video is that you switched the TDC to your MAV format immediately after acquisition of the point track. This is the case I described above: Once the Maverick independently locks on the target, it doesn't matter if the vehicle moves or not -- the Maverick will independently track the target. The situation I describe is the case where the tracked vehicle moves significantly from the position it was originally acquired before you switch to the Mav page: (1) Acquire point/auto track on a vehicle (2) Wait a while, while the TGP continues to successfully track the vehicle. Allow some good travel time (maybe 10-20 secs) so that there is no doubt the vehicle is no longer in the original position it was acquired. (3) Then switch to the IR Mav. You will find that the Maverick head slews to the place where the point track was first acquired, not where the vehicle is now. If your vehicles are in a convoy, you might be lucky enough that there is another vehicle in the same position where your original vehicle was acquired, and the maverick picks up and locks and tracks on that one. In this case, a launch will result in the vehicle being hit, but it's not the one you are tracking. Otherwise the Maverick will blow up dirt.

For Mav-F, even if the TGP (whether the LITENING or ATFLIR) has an outstanding solid point track or auto, that the latest target position is not automatically handed off to the Maverick: switching to MAV DDI or caging/uncaging simply slews the Maverick head to where the point/auto track was acquired. If this is close enough to where the vehicle is currently, then you are in luck. If not, SOL. As far as I can tell, there's no formal hand-off from the TGP to IR Maverick head as such: the Maverick head just looks at the last designated position, which is many times NOT where the point track is looking. This means that it is impossible to have a workflow where you, for e.g., acquire a point track and then wait a bit (for whatever reason) before launching the IR Mav. What you need to do is (on the TGP page), after acquiring a point/auto track, depress the TDC twice. Once to get the offset cursor (which will be superimposed on the point tracked vehicle), and a second time to designate the current offset cursor position as the target. THEN immediately switch to the Mav format page to launch (cage/uncage if needed to update the seeker head position) . If you find that the IR Mav has not locked on the vehicle or is on some spot behind the vehicle, then switch back to the TGP page, TDC depress once to redesignate the current offset cross (which should still be on the vehicle) as the target point and switch back the IRMAV DDI to get the head to look there. TL;DR -- use the offset cross to designate the current vehicle position to the Maverick instead of just relying on the point track.

Same thing happening to me -- crew ignores me, cannot hook-up to the cat. This is a bug introduced in 2.7. Someone who has a track should post the bug in the bug section. Unfortunately, I don't. There's another thread about the same issue happening in MP (only), but this one here occurs in SP.

"Next Launch" has been promised. But does not seem to be a priority -- IIRC they are going to push out this and other bindings toward the end?

Thanks, Vulcan. Yep, just peeled it off. PERFECT nose gap. It peeled off cleanly in the sense that the rubber came off intact, but there is a lot of residue left on each side. Have you tried removing it or are you just living with it?

It's not a comfort issue or a love/like issue or anything else, for me. I just need the nose gap.

Uncomfortable because it has sharp edges around the nose, or because it lets in too much light, or does not stay on, or too much pressure around face? I guess if there is no choice, and the frankenfov does not help ... seems very drastic

So I want my nose gap back! In both the Rift S and the G1 the gasket could just be popped out. With the G2, it seems glued on. I can rip it out, but that seems like a permanent / damaging solution rather than the modular one of the Rift S/G1. Am I missing something, or is this the only way to remove the nose gasket in the G2?

You know, I don't know. I've never actually done it myself. I imagine it will turn up if you search for "HSD" or under the category "HSD" based on the Lua. And if it is an axis bind, you should be able to bind it to any axis.