Yaga

The FCR in RWS set to Quiet or Silent will also detect new bricks despite No Rad displaying. Bricks can be tracked in SA or STT with FCR set to Quiet or Silent for a moment before being lost and the track position is accurate until it is dropped. Similarly, new bricks are regularly detected outside the current scan volume regardless of radar emitting or not. Sometimes other client's RWRs see the radar emitting when in Quiet or Silent, both inside and outside the current scan volume. This is stupid and needs to be fixed. Sent from my Pixel 3a using Tapatalk

In 2.9.4.53549, the changelog lists this for the F-16C: Fixed: Multiplayer datalink share of detected air targets. As far as I can tell, prior to this patch datalink sharing and adding/removing flight members' STNs worked fine in MP. Now it seems to not work at all. Neither preset flights from the ME or flights created in the DED from the cockpit work at all (members don't turn blue or even become PPLI, members don't share targets). Could we get some more detail about what changed in this update? Is there a different procedure or intended behavior now? Do we need to update our mission files with something? Or ??? This is only an issue with clients in MP and AI behave fine as group members. Any guidance would be appreciated. Maybe I'm doing something wrong. Thanks,

Interesting info! I wonder if this is why it always wants to roll left.

Can confirm. Surely this is unintended behavior. However, if you want to use these modes without bringing A2G weapons, loading and unloading A2G weapons works to unlock the A2G sensor modes iirc.

Thanks so much for looking into this and passing this along. Are there any updates in their investigation occuring internally? Were you (or they) able to reproduce the reported behavior in the .trk created per your request? Please let us know if you need any additional tracks to document this occurrence in game. I might have one or two or several.

TGT SEP functioning the way you are describing makes very little sense for exactly the reason you list: you can't separate outward for the vast majority of symbols that will be displayed. Especially when you consider that the primary use case is separating multiple search symbols on the same bearing. Interestingly, what you describe is not separation "in a radial fashion", as you put it. Radial separation is defined as: "Given some central reference point A, the radial separation between locations X and Y is the number of degrees (or radians, if you prefer) in the angle XAY". TGT SEP behaving in this way makes it a lot more useful because it breaks out symbols on the same bearing. I'm curious now if the reference material being used said "radial" and that word was misunderstood somehow.

Does the 3 pos ap pitch switch ingame remain in the up (alt) position after you click it, or is it returning to the center position? As long as it isn't snapping back to center, you should be in pitch alt hold. I suspect a binding issue, likely between the specific binding entry you're using in DCS and the way your physical controller is handling button outputs. Also, a dead zone of 9 is massive and you shouldn't need anywhere near that much to compensate for a controller issue. Sent from my Pixel 3a using Tapatalk

Hi there, Have you had a chance to review the track you requested in order to verify that the FCR acquisition cursor will indeed move while on the ground? Thanks so much. Sent from my Pixel 3a using Tapatalk

They're ground unit returns. Also, they still show if you turn the radar to quiet or silent.

No update.. Is the current scoring logic in MP intentional? Is this the complete and final state for this game mechanic?

Navigate to: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick With Notepad++ or similar, open: default.lua Once open, paste each line of code from my post above into the lua file. It should be evident where it goes because it should look similar to the control entries that are already there. Like this (line 1011): Make sure you place it above the }} seen here in 1023. We are creating a keycommand, not an axiscommand. Then, you just bind it in game to a joystick button like normal. If we look at the lua entries we've just created, we can see that these bindings will be called ROLL TRIM RESET and ANT ELEV Level in the F-16C bindings menu and will appear in the bindings subgroups for Throttle Grip, HOTAS, and YAGA MOD. Unless you enable this lua via OVGME or another mods manager, this file will be overwritten every time you update or repair DCS and will revert. Does this help?

Roll trim reset for Joystick default.lua: { down = control_commands.RollTrim, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 0.0, name = _('ROLL TRIM RESET'), category = {_('YAGA MOD'), _('Throttle Grip'), _('HOTAS')}}, --MODDED Unrelated, but here's another useful 'reset' for anyone that doesn't have a linear wheel for the radar: { down = hotas_commands.THROTTLE_ANT_ELEV_AXIS, cockpit_device_id = devices.HOTAS, value_down = 0.001, name = _('ANT ELEV Level'), category = {_('YAGA MOD'), _('Throttle Grip'), _('HOTAS')}}, --MODDED

Agreed. The logic used to be pretty solid and fool-proof. If you unslotted anywhere other than at an airbase or farp, on the ground and stationary, you were scored a death. If something did damage to you prior, then that was credited for causing the death. Not sure why this changed all of a sudden, but at this point it was years ago that it stopped working and really should be adjusted to score reliably again. Seems like it's an easy change to make, if the willingness to make the change exists.

Also seems like there's an over-willingness by the fire control computer to corelate the new brick into the location of an old track. This makes it very easy to be looking in the wrong place, because the FCR gives you every indication that it is the correct location, falsely. Each patch feels like a slightly fresh variation on how the FCR track management/handling logic/whatever is strange, illogical, and utterly unhelpful for achieving the task at hand. But it always centers around old tracks ageing out, track donation, and the rules used for correlating tracks.

Yep, I'm totally off here. You should be able to store the alignment through power off as long as you do a full alignment prior to shutting down, and this is indeed nonfunctional in the sim.