BarTzi

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.

-what if the wind blows from the direction of the land? - I don't see the issue. Place it somewhere that makes sense in the first place to avoid potential issues. -how close are we allowed to go to land?(especially to stay realistic) - That's a mission maker choice, not a game developer choise. (can also be added as an adjustable value for this specific task. When the task ends, the carrier should follow it's original path of waypoints in the mission editor). -what if there're other objects ie. oil rigs in the way - AI in the game itself should avoid collision, but this is yet again an issue of placing the carrier in a suitable place in the first place, aka a mission designer's choice. -for how long does the carrier need to sail into the wind? This is a mission designer choice, again. Ideally, you should be able to select the start and end times for this task. So you know this starts much earlier IRL than at the time of recovery - on blue water in the middle of the ocean it might work just to turn when it's needed, but in confined areas such as the Persian Gulf it takes a good bit of pre-planning. Which is why, in my opinion, it is the responsibility of the mission editor to make it happen. I'm not saying this is an easy task. However, I do think it should be an option in DCS. I can do all of the above with MOOSE, and even more (cyclic ops for example).

Stumbled upon this completely by accident. This mode is super useful for mission makers, as it allows creation of bookmarks and will quickly move the free camera from one to the other. My request is to keep the camera settings while travelling from bookmark to bookmark. As it is right now, if I choose 'look down', I have to select this option every time I switch to a different bookmark.

The rectangular zones are a very good addition to the mission editor! Thank you very much for this addition. I was thinking about two way to take it further. 1. Please consider alowing us to add (and also remove) vertexes to a rectangular zone. You can limit it to a maximum of 20-30 (and a minimum of 3 or 4). Having the ability to control the number of vertexes will truly give us the option to create very costumizable zones. 2. A tool that would let us rotate a given rectangular zone could be very helpful as well.

Take a look at a class called NAVYGROUP (it's in moose). It will give you the ability to turn the carrier into the wind, and it has no ATC connected to it. However, I absolutely agree that turning into the wind (from XX:XX until YY:YY) should be integrated as a task in the mission editor.

ED, thank you so much for adding weapon restrictions to the historic mode - it's really good to have this as an option. I noticed that some weapons are not affected by this. For example: GBU 31 (v2 and v4), and GBU32, can all be selected for the hornet when the mission takes place in a time before JDAMS became operational, while GBU-38, 31v1 and 31v3 are restricted. I would also like to note that you can easily bypass this system, if you don't set up the inventory of the airfields that are used in the mission, to match the weapons restrictions of the historic mode. Can those two be connected somehow in the future?