BarTzi

1,2 and 4 to B.

The target must be illuminated by the laser until impact. If you use a MAVF that's not a limitation (you can turn around after shooting).

The magic of coordinates and good information? Can you tell a tank from a small shed or tree if it isn't moving, while relying on the A/G radar only?

Number 3 is also not modeled correctly.

Hi Bignewy- just a heads up that the AO indexer brightness knob doesn't work, and that OP is right (I believe it's a known and reported bug since release). It's the one under the HUD brightness knob. As for the IFEI brightness, you are right. However, can this be looked at? It seems that the lighting for the buttons between the two IFEI screen displays (mode, qty, zone, et) kicks in only after turning the knob more than two-thirds of the way to the left (at this point the gauges are very well lit, but the buttons are dim).

You align the icon on the S/A page with the target waypoint. Slaving the pod to a WP was WIP and added by mistake. It's now removed.

Using AUTO mode and trying to fine-tune the position of the impact point using the TDC, I noticed the target diamond tends to move erratically and is generally not smooth and sometimes hard to control. In the attached track I set the TGP to follow the impact point, so you can have both the HUD and the pod to look at and see what happens. I used the keyboard only, but intentionally used exaggerated movement patterns (going up and then immediately down, or left and then immediately right and then left again), to make the issue more clear. You can see the icon wobbling and shaking. From my experience, it also happens when the TCD is mapped to an axis and gets worse when you try to move in more than one axis at the same time. I hope the overall smoothness of the icon movement can be looked at. I recorded this a while back. Should give you an idea of what I'm talking about: auto hud designation.trk

While I agree with you, it's important to stick to the facts. It's half a year since the TGP was released for the Hornet :) ED did release a very WIP version of the pointing modes (probably a mistake), that can be used reliably only with bombs at this moment. Use WPDSG when in A/G mode, and the pod will snap to that point.

Not sure about 'CCIP in AUTO', but the plane treated high drag bomb as high drag bombs all the time, even if you chose not to deploy the high drag mechanism. That eventually gave you a false impact point. Today they changed it :)

After updating to 2.5.6, I can place the objects in the editor but they are never visible when the mission starts. Does that happen to anyone else?

And also have move than four available callsigns :P

There is no unique symbol for the position the TGP is pointing at. It should point at the target waypoint, the velocity vector or the CCIP cross. The target itself can be designated using every sensor the plane has, and that includes the HUD. If you want a visual representation of the position of the target- HUD designation is the tool you want to use. Otherwise- you will not have a HUD symbol unless you designate a target using the TGP. Most of what I wrote above is not yet implemented, which explains some of the things you are struggling with (currently - just try to work with the S/A page marker). The rest is understanding the concept and usage of the pod itself.

And still, scan centering (if you scan less than 140 degrees) around the TDC is a feature for all scan modes. You can center the scan area around the current position of your TDC, but you can't slew the scan area like you can in the F-16. SPOT is a different feature. That's what OP was probably talking about. https://forums.eagle.ru/showpost.php?p=4032302&postcount=22

Scan centering was discussed here before and indeed is a feature of the plane in all scan modes(not TWS exclusive). I hope this was labeled 'non-realistic' because of the word slew. This might seem like you are hoping for the same feature the F-16 has (where the cone follows the TDC movement). Scan centering works how you described above.

But they already have HUD designation (ball and chain). It works only with weapons that support AUTO (CCRP) at the moment. Like so: You used to be able to do it regardless of the weapons you were carrying but it changed a while back.

@drPhibes The version in your picture is the one ED will make (cooling intake on the right side of the pod). The ECU can be rotated. What ED has to do is to mirror everything behind the forward section. See the pic below). This version is the one we currently have in-game:

The pod sits in a different position when mounted on station 4. (cooling intake is on the right side). The original model of the LITENING does not support this (this = the station four configuration), so they have to correct it.

It's not a white vs green issue. HUD and DDI font in the hornet needs improvement. The rendering is making it very hard to read (visible easily when you switch to night mode). They added an option for VR users to project the JHMCS differently than it is done in real life. Making the font easier to read (optionally) won't hurt the sim.

Looks like you have to have ordnance on your jet to create a target point using the HUD. Is that accurate?

Same question for the hornet TGP improvements :)?

While that is true, he should actually adjust the brightness of the AOA indexer itself. However, that switch does nothing at the moment.

Some developers from the Hornet team switched to Viper related tasks prior to the release of the Viper. I guess (and I can be wrong here) that the 'TGP guy' was probably assigned the task to integrate the LITENING pod to the F-16. We can't really complain about it at this point in time. Let's just keep hoping the ability to slave the TGP to a waypoint will be added in the near future.

First of all, it's obviously a good thing if they decided to scrap the LITENING, because if I'm honest- the majority of players won't even bother with it once we can mount the ATFLIR on station 4. With that being said, they mentioned a few times that the ATFLIR will come around the time the new IR renderer will be implemented. The most logical answer is that you didn't see any improvements to the LITENING because it wasn't being worked on (remember the whole F16 saga?). I was convinced they will get to it in the updates after the pod was released. They probably will once it's higher on their priority list. In the meantime, I just stopped using it.

I have a feeling he meant a Hornet related update.

Are you joking? Wags does a hell of a good job explaining the functionality of new features for the Hornet and Viper. His videos are not long, not boring and on top of it all, he also reads the comments. Additional details are usually added by him to the mini updates thread. ED updates the manual in 'chunks', which is the right way in my opinion. Once enough content was added they push an update for the manual. Updating and maintaining a document that is supposed to guide you through the avionics of a modern jet is difficult enough.