Harker

You can edit World.lua, in \Eagle Dynamics\DCS World\Config\World. Probably doesn't pass IC.

Welcome to the forums. I personally don't get the logic of the video above. Looking past the fact that the person can bind the buttons like the real thing but chooses not to, the Sensor Control Switch will see much more use than the Weapons Select one, so it makes sense for it to be at the top of the stick (its real position). The Weapons switch on the stick also has a slightly hard time clicking to the left, making it even less useful for sensor control. Since you have the Hornet grip, I would recommend just binding the buttons to match the real thing, it'll be more intuitive this way. Check page 72 in the manual (\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Doc\). As for the extra buttons on the wheel-looking thing, I use them for zoom-in, zoom reset and hide/show pilot body (depress).

This is indeed part of the damage model. The Hornet has two Digital Data Computers or Mission Computers (MC), and they control different functions. MC1 controls the navigation functions, while MC2 controls the weapons delivery calculations, associated data processing etc. Each computer offers limited backup functionality for the other. Since your MC1 failed, it's normal that navigation data became invalid, while other stuff worked. Also, the HUD system wasn't damaged, and thus was still working. Sometimes it's possible to restore some of the lost functionality by using the MC1 OFF/MC2 OFF switches, located in the back of the left console. This will attempt to pass over the work to the remaining computer, if it's included in the latter's backup subroutines.

There isn't a lack of documentation on the subject, but that also doesn't mean it can be posted here. I very much understand this is frustrating to hear, but this is a sensitive topic. What I can say is that QTY is actually meant to be used with multiple target coordinates, and like I mentioned before, it will enable the calculation of the common ILZAR for all targets. That function contrasts directly with what you're proposing (QTY sharing the same target across all stations).

Do the TOO coordinates in the MSN sub-page of the JDAM Display change, when you designate the second target? You could also make a quick video or a track, so others can see exactly what you're doing.

In TOO mode, you need to pass on the new coordinates with TDC Depress. It sounds like you do: designate, drop, slew, drop. What you should do, is: designate, drop, slew, designate, drop.

Normally, PP targets are loaded via data transfer, not typed in manually by the pilot (the pilot can still manually overwrite PP targets). So, I expect we'll be able to do that once DTC functionality comes to DCS. Having 6 preloaded PP targets per station offers the pilot flexibility in choosing targets, upon arrival to the AO. Maybe the targets corresponding to PP1/2/3 are too heavily defended and the flight opts to attack secondary targets at PP4,5,6. It is also possible that PP targets are shared between aircraft, for redundancy. In that case, 1 can attack PP1/2/3 and 2 can attack PP4/5/6, for example. Generally, it never hurts to have more options

Disregard my second paragraph, this is a separate issue, that causes the Litening to work despite of the present bug. The problem you brought forward has to do with the fact that, in your example, the ATFLIR is driving (updating the position of) the designation in AUTO, while moving. If the pod is driving, or slaved to the designation, and the designation is moving, the missile can't see the laser. I've since discovered that missile can see the laser after it's released. So, as a workaround until it's fixed, you can launch towards a stationary designation (so the missile will see the laser, while on the jet) and then track a moving target with the ATFLIR, for example.

Because you're selecting PP1 for one particular station, while the others remain on PP2. Using QTY does not make every station selected with QTY change PP# together, it merely allows for a single pickle release, instead of Pickle-Pickle-Pickle-Pickle in DCS. (IRL, it also shows you the combined IZLAR (optimal release zone) for all stations, so it's more useful.)

I was able to reproduce in our closed build. The issue is present when the pod is slaved to or driving a moving designation. The reason the Litening works at first glance is that PTRK does not drive the A/G designation (which it should in all cases) if you've previously used WPDSG to slave the pod to a Waypoint, so that's another bug. Same for the ATFLIR, if you don't first depress the TDC. OP, thank you for the report, it helped spot two bugs at once!

What I understand here is that after selecting PP2 for all stations to program them, you then selected PP1 only for the first station. As you pickled, the first station had PP1, so target 1 was hit. The rest of the stations, however, still had PP2 selected, so targets 6,7,8 are hit. After, you switch to PP2 for the first station only as well and the rest of the stations remain on PP2, so targets 5,6,7,8 are hit. This is correct behavior. QTY merely enables the simultaneous release of JDAMs from different stations, but these stations still need to be configured individually, and have their PP or TOO targets selected or changed individually. The one thing that we don't have in DCS is that selecting QTY should also calculate and display a common launch zone for all stations in QTY, if it is possible, whereas now only the primary station has its launch zone displayed. Still, the above behavior is not a bug.

BIAS should be available with AMRAAMs in flight, as per available public docs. If it's not, then it's a bug. OP, include a small track if you can.

You can program the other sequences on the ground, before takeoff. In general, you have three Sequences available, of up to 15 WPs each. You can insert and delete WPs from a Sequence at any point after the jet and the mission computers are powered up and WPs have been loaded. You can even create a Sequence of random WPs, such as 1-5-12-3-6-12-4, depending on the order that you insert them. In DCS, SEQ1 is populated automatically with the first 15 WPs. SEQ2 and SEQ3 are empty when you spawn, but you can populate them yourself, as mentioned above.

In DCS, only SEQ1 is automatically populated with the first 15 waypoints (WP0 - WP14). The rest of the waypoints are available for navigation and targeting, outside of SEQ1 (you need to unbox SEQ1 to access WPs outside of it), but are not automatically placed in SEQ2 and SEQ3. In your case, if you want SEQ2 to contain WP15 - WP26, you need to insert them yourself, using the SEQUFC option in the DATA->WYPT submenu of the HSI.

It's for emergencies that would otherwise lead to the loss of the airframe or the pilot anyway. Obviously, you don't want to be in a position that necessitates for you to rely on that, it's a last resort. And in any case, pilots are much more difficult to replace than aircraft.

Not what was being discussed, catastrophic failure through over-G is modeled in both aircraft. But with the F-16 lacking a G-limiter (instead only offering an AOA limiter via the CAT I/III switch), it's up to the pilot to make sure they don't over-G the stores. Which means that if you're not paying attention, you can pull 6.5G without realizing, for example, and then that JDAM you were hoping to release over the target area is hung. The Hornet has a dynamic G-limiter, so the same scenario is less likely. But that's not what we're talking about. We're talking about the consequences of pulling the paddle in the Hornet and going over the 7.5G limit. Which are modeled just fine in the context of DCS, considering that the Hornet can go to 9G without any immediate effects (except when stores are attached, as mentioned above, but I'm guessing the OP refers to a clean configuration), and the 7.5G limit is there as a means to guarantee that the aircraft's structural integrity will remain optimal in the future, especially during carrier landings. Pulling the paddle and exceeding the limiter is to be used in emergencies, and that includes life or death situations. No pilot will choose to get shot down, if they can help it in any way and there's little sense offering the pilot an option that will cause their wings to disintegrate. ED can certainly include over-G effects on weapons stores and the targeting pod, as mentioned above, but that's it, that won't do anything for clean Hornets, since the effect on the airframe itself is more long term. And since every plane spawns as new, the current implementation doesn't need to change on that front.

In addition to the regular priority list (7 tracks shown at most, btw), the HMD will also always display the track you have under the TDC or have selected with STEP, on th SA page. That track will have an asterisk next to it. So. if you want to always have an eye on the tanker, select it with STEP. The only issue is that STEP will exit if you want to slew the TDC on the SA again, and oftentimes deactivates by itself after a while.

The last thing you're talking about is called Bump acquisition and it's been a feature in the Legacy Hornet since at least the early 2000s. We just don't have it in DCS yet. With the radar in STT, using the SCS in ACM, it rejects the original target for 2 seconds. It's also available in AACQ and it rejects the current STT target. In both cases, it'll re-acquire the original target, if another target is not available within the time limit.

The missile will guide to whatever object its seeker is tracking. The A/G designation you're creating with the ATFLIR merely serves to slew the seeker towards that point, but you still need to make sure that the missile seeker is tracking the desired object. If the seeker is not switching to the new designation, you might need to cage it and then uncage it again. The seeker quality is not the best indeed, but that's to be expected, it's a disposable seeker, after all. You can zoom in with the FOV command if the seeker is not tracking an object, but that's just about it. You may also want to fly closer in order to have a better picture.

If this is about the Velocity Vector showing this behavior when outside of the HUD boundaries, it's fixed internally. If the problem appears while it's inside the HUD boundary, then it's a new bug.

Good point. The radar contribution circle is also featured in all publicly available documentation (in most figures in the 742-100, for example).

It's also valid for 15C and up, according to the 742-100. Both for AACQ and ACM modes (2 second exclusion for ACM). Described in sections 011 03 and 013 00.

IRL, the ATFLIR has better optical zoom, offering better picture quality from further away. The LITENING has less good optical zoom, while it allows to zoom in digitally (but digital zoom is offers worse quality than optical). In DCS, depends on which one you prefer, since the picture quality doesn't degrade with digital zoom. I personally prefer the ATFLIR, because I can fully use it using the radar elevation controls, can slew SCENE, and is accurate to IRL for USN Hornets. There are also other differences, but are irrelevant in the scope of DCS.

CCIP shouldn't be available with a designation, it should revert to AUTO. The bug here is that it's possible to have CCIP with a designation. When in CCIP, in A/G mode, the FLIR is slaved to the CCIP aiming reticle.

To my knowledge, this can be done using what's called a Running Rendezvous, whereupon the lead will fly the typical 300 knots / 500 ft departure, and the wingmen will maintain 500 ft, but speed up slightly in order to form up with the lead. Alternatively, the flight can join up after the 7 nmi part, using a CV Rendezvous, whereupon the lead will set up an orbit some distance from the boat and the flight will rejoin in that orbit. When everyone is joined up, they'll resume the flight plan.