BarTzi

That's fine by me, but it doesn't make sense that the SA page displays the tacan course line without displaying the tacan station icon (when you use the CRS switch to set a course using the HSI). It should either display the tacan icon and course line, or not display both of them.

It is probably the only difference between SA and HSI in DCS (datalink aside). I was wondering why the SA page displays every bit of relevant tacan infoamation, including tacan course, without displaying the tacan station icon.

Can confirm this is a major issue for harpoons as well in the current OB build of DCS.

Just making sure: are you using steerpoints for the path of the missiles? (we only observed the problem when using a pre planned missile flight path). If your build is different than OB, then this could have been solved internally somehow.

I don't think you can replicate this on your own, as the desync is between clients. Client A sees only his missiles follow the designated path (slam er steerpoints), while the rest of the missiles (launched by client B) don't follow their path and go straight to target. Client B sees only his missiles follow the designated path (slam er steerpoints), while the rest of the missiles (launched by client A) don't follow their path and go straight to target.

I don't think this is correct, and it also says it is not correct in the documents ED uses to implement the JDAM interface. I can show you that via PM if that's ok.

This can be more easily seen here:

I'm literally quoting documentation here. JDAM coords should not be earased when you undesignate.

"Stepping to another JDAM station or canceling a target designation causes the TOO target coordinate to be retained in the selected weapon(s)"

Respectfully, let's not derail this thread any further, since this is rather important QOL change. When we have two people who used the system explain to us that this can be done, I don't think this thread should be tagged as 'no evidence'

Sure, you can't arm the laser, that doesn't mean you shouldn't be able to change the frequency though. I agree, which is why I think they should ask their SME about this.

I'm going to take a guess and say it's the system schematics documentation, but the only thing I can understand from it is that you can't arm LTDR on the ground.

Not to underestimate the team's efforts during this time, but will you consider asking your SME's?

As a part of the strike eagle modernization plan, RFTF was installed to allow the aircraft to use the radar while jamming. This is roughly at the same time as AESA radars were introduced to the airframe. https://boeing.mediaroom.com/2009-09-15-Boeing-F-15E-Radar-Modernization-Program-Receives-New-Designation So ,yeah - jammers can interfere with radar usage.

@BIGNEWY Can you take a second look at this, please? Thanks!

What does it mean if it was moved to the wishlist section?

Well, it clearly shows the picture does not freeze when the pilot slews it around that timestamp.

The ten shade gray scale is initiated by selecting 'setup'. It should only be displayed when 'setup' is boxed. There is, however, one condition in which this is not true. 1. Bring up the ATFLIR display while the airplane is in nav mode 2. Box 'seutp'. It should work correctly. Keep it boxed. 3. Select A\G or A\A mode. 4. Bring up the ATFLIR display again. 5. You will notice two things. The first is that 'setup' is no longer boxed. The second is that the ten shade gray scale is visible. 6. From this moment, boxing 'seutp' will mask the ten shade gray scale, and unboxing it will do the opposite. This is a bug. grayscale bug2.trk

+1

Hi BIGNEWY - thanks for taking the time. There might be something off with the track. I'm talking about slewing the TGP in A\A mode. When I watch the track, I see you slewing the radar brackets. Your plane is not equipped with a targeting pod, but this might be due to differences between 2.7OB and your dev version.

I used the keyboard when I recorded this track (it also doesn't work when I use a mini stick on the throttle or a 4-way hat). This is only true for A\A mode. It works just as it should in air to ground.

I noticed that when using the targeting pods (both litening and atflir), I can't slew the pod in air to air mode using two inputs at the same time (up and left for example), which means I can't move it diagonally. It will move either up, down, left or right only. Reporting this because I don't think air to air mode should actually change the way the TDC interacts with the pod. This limitation does not exist when using the pod in air to ground mode. tgp air to air slew.trk

That's just the brackets adjusting to the relative size of the target. The expanding scan zone (the square) is missing (both symbology and logic)

Said target box is shown here.

It allows you to navigate between your own or ED's bookmarks. It's just a coordinate for the free camera (F11) to go to, as far as I can tell.