Harker

The Hornet's EXP3 doesn't work like it should. It's just another magnification level in DCS, while in reality, it is capable of building a medium resolution SAR image, whose resolution is consistent with range. In game, it does not perform any sort of buildup, every frame's clarity is dependent on range and angle. Also, the picture in DCS suffers from excessive azimuth and/or range uncertainties, which show up as these long, wide lines that correspond to returns. They should be smaller to begin with and the picture should get clearer as more frames are integrated and the overall uncertainty decreases. Now, the picture only gets clearer if you move closer. The APG-73 RUG2 is capable of much better resolution than that, to the point that you can sometimes distinguish types of vehicles or aircraft. Although the displays on Legacy Hornets might not be good enough to show the full resolution of the SAR picture, it shouldn't be as messed up with azimuth and/or range uncertainties as it is in DCS, it should just have less detail.

No effect AFAIK. The only thing that matters in the whole MIDS "simulation" is that you turn the system on. If you have SRS, you can use the two MIDS radios (VOCA, VOCB) with Radio 3 and 4 and people need to be in the same channel (other than 127).

Incredible indeed, but no one here can do anything more than tell the OP how the situation is. At least they won't waste their time testing for an old, reported bug or thinking they're doing something wrong. And at least, they can go in the Bugs section and check about other bugs there.

There's a massive list of reported issues in the Bug section, some of which date back to the release of the Hornet. Since they're posted in their own forums, ED is or should be aware of them. No one can comment on whether or not they are a priority, though.

Never mind, I can't read.

Currently, with the A/G radar, when operating in EXP modes that use DBS/SAR, the picture for +/- 5 degrees in front of the nose of the aircraft is completely blanked out. While this is correct for the older APG-65, based on documentation I've found, the APG-73 should have that part filled with RBM (Real Beam Mapping), like it is currently implemented in the F-16C and the JF-17. https://archive.org/details/introduction-to-airborne-radar/page/n545/mode/2up Page 545(553). "For navigation: wide-field-of- view, 8:1 DBS, with real beam mapping filling the ±5° forward blind sector." AG Radar RBM EXP +-5 degree blank spot.trk

Not to mention several videos which show the ATFLIR with the LTD/R code visible, without the laser being armed. It is also visible while in A/A mode.

You say you failed to align your HMD, it seems that is the issue here. Are you following the correct procedure to align? For the Hornet, that is: 1. Enable the HMD via the knob in the cockpit. 2. Run a BIT test and stop it after all the patterns show. (BIT -> DISPLAYS -> HMD). The status for the HMD should now be GO. 3. SUPT menu -> HMD -> ALIGN. Match the HMD and HUD crosses for Coarse alignment. Press and hold the Cage/Uncage button until you get the OK message. Then, the alignment will automatically change to Fine alignment, where you can use the TDC to finely align the two crosses with the HUD symbology. You can switch between XY and Rotational alignment via Cage/Uncage (that part is correctly updated and different from Wags' tutorial). When satisfied, exit alignment via the HMD page. There is a similar procedure for the Viper and it's explained in one of Wags' tutorials on Youtube. You can also find it in the mini-updates thread. Also, could it be that you start your SP flights already in the air or in a hot started jet? In those cases, HMD alignment is already completed.

Look at this bug thread /topic/274042-a-g-radar-exp3-and-aircraft-movement-issues/ Towards the end, you can see a difference between the FLIR (which is pointing to the correct location) and the A/G radar cursor location. It appears that the A/G radar image is shifted with the motion of the aircraft. Normally, the MC should be able to use Radar and INS data to present a correct picture.

On my end, nothing seems changed. I tried the mod now and I get grayscale FLIR and A/G Radar. All sensor video in the Hornet is controlled by the same file, so it is very strange if you get the one and not the other. Could you remove the mod completely, run a Repair of DCS and reapply it? (Be aware that the Repair will replace every file in your install directory with its default one, so it might mess up other mods). Or simply re-download the mod, apply it again and see if it works. I updated some instructions for 2.7.7, since the mod does not break IC anymore (yay!), but nothing changed in the way it works. Also, sorry for not responding quickly, but I'm not receiving notifications from this thread for some reason. I've opted to, several times.

Not possible. You can only affect another flight by adding triggered actions to them and then either having the triggers be activated by an event or activate them manually yourself through the use of the F10 radio menu (you're going to need to set a Radio Item in the Triggers page of the Mission Editor).

Could be. There is also something off in the way the missile guides itself to intercept the target, sometimes it'll pull too much lead and end up with the target outside the gimbal limits, as it gets closer.

I've had middling success in SP testing missions, but I noticed that no matter how much I pull up to give the missile the best loft angle possible, it will still pull Gs straight from the rail in order to pitch up and then pull negative Gs in order to pitch down to its desired trajectory. I also noticed it doing jerky movements, especially against defending targets. So it now loses speed due to both of these things.

If you could see IR picture from the seeker, then you definitely had the 65F. The Laser Maverick does not display a typical video feed, the feed is just a seeker grid and you have the laser code above, which you need to input yourself. So it's possible that your missile simply locked onto the ship just when you pressed the button by coincidence.

Can you be more specific when you say night lighting effects? You mean how strong the backlight is? If so, it's as Tholozor says, through the Alpha (opacity) channel.

The X denotes that the weapon does not meet the conditions required to fire it. For the Maverick, these conditions are: A/G Mode, Master Arm On, seeker is uncaged and actively tracking. As long as you have an A/G designation, the seeker will be slaved on the designation LOS. However, you still need to command the seeker to track, either by uncaging it and it tracks itself or by depressing and releasing the TDC to command track. Often, if it's already looking at a valid target, it'll track straight out of uncaging. For the IR Maverick (65F), it needs to track based on the IR contrast of the picture. For the Laser Maverick (65E), it needs to track a laser spot. There is specific functionality for the Laser Maverick, where if you have a TPOD yourself and the laser is armed, depressing the weapon release button will fire the laser and if the missile is uncaged, it'll fire as soon as it spots the laser, as long as you keep the button held down. So, the MAV will have an X over it, which will go away as soon as the seeker spots the laser, just before it fires. Which is likely what happened in your case.

FLIR designation, A/G radar slaved to the FLIR A/G radar designation, FLIR slaved to the radar Notice the difference in coordinates.

Since the MAV has a video and information interface with the aircraft, I'd expect laser code entry to work the way it does right now, more or less. I've seen at least one IRL video that shows the MAV display with the laser code, that we have in DCS.

They don't necessarily have to be raised in order to go to past MIL, they can also be pushed through the detent.

You should be able to designate with TDC Depress while in SPOT, the current implementation is wrong and IIRC it has been reported. As for exiting TWS and the scan reverting to the center, I'm not sure of the IRL behavior here. I'm inclined to say that the RWS scan should remain where the TWS was, as we're supposed to be able to center the azimuth in RWS as well.

Another way would be to create a new waypoint with the HSI Slew function, but that's not implemented yet either.

They are mutually exclusive, but not in that way. The functionality should be: * With or without the TDC assigned to the SA page, STEP will place the box over the highest priority contact, moving down the list. L&S, DT2, remaining ranks etc and then cycle back. * When STEP is active, the TDC will disappear. * If the TDC is slewed on the SA page while STEP is active, the STEP box will disappear and the TDC will show up at the place of the box. It was actually working correctly until now, except for some wonkiness with the STEP priority list. Also, the STEP box should be black on the inside and hide everything behind it, so you can clearly read the info on your target.

AFAIK, high fidelity radars work the same. There is no radar simulation at all. It's all a set of attributes. Is there an aircraft in XYZ point? Is the player's radar pointing to XYZ? Is the target hot/cold/beaming etc? Is the PRF appropriate for the target's velocity? Is the target in range of that radar, in that PRF mode? Is the target jamming? If everything above is satisfied according to the situation in question, then you get a brick or track on your radar display. The track info is also not provided by your radar, but by the target itself (the simulation tells your display to show that altitude, Mach, heading). There is no "radar", there are attributes and then your display in the cockpit. Think about the fact that, the same aircraft, in the same scenario, is going to show up at exactly the same range, every single time you run a test. It's even simpler for the A/G radar. MAP is just a terrain overlay with a LOS calculation for the radar shadow. Notice how we don't see trees, for example. GMT simply sees if a unit is close to ground, moves between certain speed limits and is not obscured by terrain. If those conditions are satisfied, a brick pops up.

Terrain Avoidance is a radar mode, selected via the A/G radar menu. It simply displays incoming terrain as above you (high intensity), unsafe (between 0 and 500 ft below you - intermediate intensity) or safe ( more than 500 ft below you - not displayed).

This seems to be more of a problem of RCS values for different aircraft instead of something specific to the Hornet. The RCS values in DCS are very different from IRL. It'd be better if ED fixed that first and then adjusted the radars based on known radar equations.