BarTzi

It should be visible 10nm out according to documentation.

And that's the point.. If the pod LOS doesn't move to the offset location, what's the real purpose of offset as it is modeled in DCS at the moment? Shouldn't it be like the ATFLIR? In DCS it does everything else except moving the LOS, which seems odd.

The E seeker will be slewed to the offset (it follows the designated target while uncaged), and will try to spot the laser there. The F will be slewed to the offset and try to track a target. If it's correct, offset has no purpose. The point is to track something, while you offset the pod LOS to a different location. This whole thread is about whether or not the pod LOS should center on the offset target, like the ATFLIR: Currently, it does everything except shifting the pod LOS.

Using offset will defenitely update the designated target location (HUD). It will not lase that spot, so a laser guided bomb will most likely hit the center of the pod LOS anyways. Now that we know that the 65F will track the new offset location (this also works for the E), and that the designated target is updated on the HUD, it makes much more sense that the pod LOS should also move to the offset location. Otherwise, you will need someone else to lase for you, or you will be limited to use this with JTAC only.

I think the designated target will be updated if you use offset. It's jus the pod LOS that won't move.

That's my point. If what you are saying is pretty much using a mark point, why does offset exist in the way that it is right now? It's redundant for no reason, which might suggest the way offset was modeled is not 100% accurate.

The way to launch it is to hold pickle after the MAV is ungaced and the seeker is looking at the target. The TGP will start auto lasing and MAV LKD will momentarily appear on the HUD, as the missile leaves the rail. TTMR is still a thing even if the TGP isn't lasing.

I think he means the possibility to change the weather settings in the mission to be the same as the real location at the start of the mission

Yeah - right. I was able to take control while replying this track and hit every target I wanted.

Because the F model will try to lock every new target designated by the TGP. You don't have to undesignate anything. Also keep in mind we don't have markpoints and some hotas shortcuts that will help in this case.

I don't know, I don't really see an issue here: https://www.thedrive.com/content-b/message-editor%2F1562203225359-f-16.jpg?quality=60

In a HOTAS centric piece of softwawre, no GUI will ever be good enough in my opinion. The ultimate solution is a built in voice recognition capability, tied to a slightly improved F menu. Just like voice attack.

Thank you for including my livery pack in the base game! There's one small issue with the way they were added: not all textures are of the same livery version. This is 100% my fault for updating them regularly, which made it hard to keep up. This can be easily solved by updating to v1.31 and replacing/overwriting all of the textures, including the tail art (they were all changed in one way or another). Download links: https://www.digitalcombatsimulator.com/en/files/3308784/ https://www.digitalcombatsimulator.com/en/files/3308785/ https://www.digitalcombatsimulator.com/en/files/3308782/ https://www.digitalcombatsimulator.com/en/files/3308780/

The Turkish one being selectable for the USA is the minor glitch here :)

Let's ignore the fact that OP is wrong here for a minute. You have no sources to back it up other than the way it feels, and you never mentioned what is wrong in your opinion. Don't you think different companies implement systems in different ways? Do you think its right to compare it to the A-10C, which has a HOTAS based on pilot feedback from previous aircraft (namely the F16)?

What you are describing is the equivalent of using markpoints. This thread is about wether or not the implementation of the offset in the DCS LITENING is accurate, especially since it doesn't offset the pod at all. A better example of this is the ATFLIR offset, as shown in the video Swift linked.

You don't, but I have to. I'm limited to 300Mb per livery, otherwise I won't be able to upload them to ED's website.

You don't have to lase for yourself because the pod does that for you. You will almost never lase manually for yourself in DCS. Only for someone else. And even if you don't buddy lase, it's another way help your wingman slew the pod to the correct target (LSS).

Are you asking what's the point of manually lasing? Marking targets for another pilot is a good example.

When trigger is boxed, pulling the trigger will manually lase. No pull- no laser is fired. However, when you launch a weapon - it will automatically lase for you. The steps to launch the AGM65E are as I explained above. Just press and hold the pickle. The pod will start lasing, and when the missile tracks it will leave the rail. Let go of the pickle and the pod will continue to lase until impact + 5/10 seconds. Read what I wrote above again. Since day one, any AGM (65F/65E/88.) has priosity over the TGP when it comes to the HOTAS, doesn't matter which one has the sensor priority (diamond). So you can't use the FOV switch to control the TGP FOV if any AGM is displayed on any display.

Slew the TGP instead and designate a new target?

Issue 1: The TGP will lase automatically for each laser guided weapon. What you should do instead is press and hold pickle. The TGP will start lasing, the missile will then track and launch. Let go of the pickle only after whe weapon is fired. I believe Chuck's guide doesn't cover the latest changes to the TGP. Issue 2: That's intended.

Planned for later in EA

When you set the ampcd to night and increment the contrast manually, each press of the rocker should translate to one contrast stage (going up to 9). However, it takes two clicks to get past level 4. Edit: when the AMPCD is set to day, and the rocker controls the auto contrast - it takes two clicks to get past level 5. Mind the typo in the title. It should be contrast. ampcd cont stages issue.trk

Possible issue with LTWS and MSI Referring this video: LTWS + MSI should display HAFU symbols, unless the target is painted only by your radar. I recently noticed that I get the HAFU symbols only if my radar doesn't track the target at all, and when it does (doesn't matter how many other donors see the targets) the HAFU instantly changes to a brick. The attached track is of a mission with one AI wingman, and one AWACS that is set up correctly. The S/A page works fine and displays the right contacts and information from donors. Notice how the bricks change to HAFUS and vice versa as I move the vertical scan limitations. ltws with msi.trk