QuiGon

From memory: On the A/A radar page on the left side of the upper row of OSB buttons, there is one that controls the radar channel. It should say something like channel 1A or so. You can push it to change the channel.

It's actually implemented. The manual is not up to date in this regard.

The GBU-28 isn't implemented yet. The one available in DCS currently is and old model for use with AI aircraft only and doesn't work properly if employed by players.

I'm no radar expert, but to me it looks like you're putting the radar into a look-down situation there, thus making it loose the lock. Having said that ED is currently working on adjusting the radar simulation and look-down performance.

Ich denke das dürften schon das sein, was dann auch in DCS zu sehen sein wird, wenn auch vielleicht nochmal weiter angepasst (Reduzierung der Texturschärfe oder Polygonanzahl um die Performance zu verbessern). Das kann aber @OPEC vielleicht besser beantworten?

An interactive replay of your flight, that gives the viewer the option to take control at any point.

There's one option missing from your poll question who your RIO is: myself I don't need a RIO, because I am always playing as a RIO myself. I have probably spent somewhere between 500 and 1000 hours in the DCS Tomcat by now and of those I have only spent around 20h in the front seat (usually teaching other RIOs).

The GBU-28 isn't really implemented it. The current GBU-28 is a very old model for use by AI aircraft. It doesn't work properly with player aircraft and will be entirely re-done.

Clearing out the configs folder under Saved Games/DCS should fix these issues (make a backup of your inpouts and options.lua if you don't want to loose them).

Correct

AGM-130 AGM-154 AGM-65 As per FAQ: https://cdn.discordapp.com/attachments/544231925263630336/1008508215643873381/Frequently_Asked_Questions_ver_2.pdf Fun part about the Mavericks:

You will be missing the depress animation for the trim switch and instead see the CMD switch move on the throttle.

Ich wollte auch keine böse Absicht unterstellen. Wichtig ist aber bei solchen Dingen immer möglichst alle Rahmenbedingungen zu nennen, so dass man das Problem möglichst schnell eingrenzen kann Die Paveway II-GBUs funktionieren wunderbar (GBU-12, GBU-10). Alle anderen (z.B. GBU-28) sind noch alte Modelle für KI-Flieger und funktionieren noch nicht richtig wenn sie durch Spieler verwendet werden.

Das kann sein. Ich tue immer manuell bewaffnen und bei mir steht der TPOD immer auf 1111. Ah, du nutzt die GBU-28, das hattest du uns bislang verschwiegen. Die GBU-28 ist meines Wissens nach noch nicht richtig implementiert. Das ist noch ein uraltes Waffenmodell für KI-Flieger, dass noch für die Nutzung durch Spieler generalüberholt werden muss. Das RAZBAM das Teil trotzdem schon verfügbar macht ist bissl dämlich...

Ist standardmäßig auf 1111:

This button on the debriefing screen lets you save a track file:

Enter 1A, 2A, etc. If B is selected the system doesn't know if you want 1A or 1B if you just enter 1.

Yeah, the poor IFF modelling (or even lack thereof) is one of my biggest gripes with DCS. It's great that ED added a neutral side a while ago, which would give IFF at least some depth, if it would actually get used by mission makers. I've been trying for years to raise some awareness of how poorly modelled IFF in DCS is.

Dann liegt da das Problem, denn du musst den Laser-Code ändern und zwar den vom TPOD. Dieser ist standardmäßig auf 1111. Wenn der TPOD nun mit Code 1111 lasert und die Bomben nach 1688 suchen, dann werden sie keinen passenden Laser finden.

Solo oder multicrew?

For other users that might have a similar problem when editing a SP: Make sure that you're not editing the SP you're currently navigating to, as that is not possible.

It can only be turned on in the front. If it shows up as on in the front and off in the back it's bugged.

Ok, this is indeed the only exception. If a player aircraft gets such severe damage that DCS treats it as dead (it will disappear from the F10 map and also from TacView recordings), then it will indeed not respond to IFF.

A short track file depicting the issue would help.