Mo410

Usually trimming the rudder first with asymmetric loads should remove the rolling tendency. Have a look at the ball on the standby AI and see if it needs trimming. I do agree though that the effect is a little over done, the airplane is able to compensate a bit more for adverse roll, but its up to you for yaw trim.

I've sent them a list of things that could be improved on to get closer and they are having a look, but nothing formal, which is fine.

Yes, if they could address this and populate the AZ/EL / SA Format with off board tracks, I think it would be a lot easier and more realistic to use.

Double action of the TDC or fast acq will command a mini raster provided no L&S and nothing under the cursor - or if a lock is commanded and the radar is having difficulty meeting the requirements to track (like an aging out hit that is no longer valid). Similar to SPOT, but will time out and return to search. Undesignate should stop it, but it seems like you action the TDC in DCS to get it to stop. Edut - So not likely a bug, just needs fixing to have the correct implementation

No, you can bump the azimuth or push button it down like you can with the range (where left side of scope is less az) and the single TDC depress like on AZ/EL to move radar FOV around. It works exactly like the AZ/EL but on the ATTK format. It makes sense when it all works like it should. If something is displayed on the Attk format, the computers have a good guess if not the actual answer of the altitude of the trackfile/surv track, so when you TDC over it, the altitude and mach will also appear, something that is currently absent for offboards.

So in real life, you get all your track files (and PPLI's, and Surv tracks -on and off board) displayed on the AZ/EL so you know if your radar FOV is in the right spot or not. Normally SPOT is used to either breakout a two ship if you only see one contact, or to get an initial detection on someone you know is there, but need some extra energy down range. Not frequently used, only when things aren't working out. You can also make L&S and DT2's from the SA format and the AZ/EL, which make things much easier when track files are not in front of you. So you have a half implemented system that is getting there, but the features that are still lacking cause the current system to not make sense. Make sure you are managing your PRF in TWS, and up your aging to keep the bricks appearing. It is better, but still could have some improvement on the integration of the SA/AZ/EL/Rdr Attk formats.

The TWS scan volume is not supposed to follow the cursor, as you should be able to move the cursor over other contacts without changing where the radar is looking. TDC action should be required to move the radar FOV.

My experience has been that this was always a feature back to 17C, which would put it in the neighborhood of the time frame that is being simulated. You can just push button into TWS, but I understand the desire to HOTAS given the mouse movements or VR considerations.

Yes, correct as you said as well as the folks above, shoot, step with undesignate (verify it stepped and it stepped to the correct next trackfile) and shoot. In fact, if you shoot from STT and hit undesignate, it should go into TWS (but may not be modelled right now, will check in a bit).

Different techniques for different folks. To shoot a 4 ship, RWS detects and breaks out at least one. STT that contact and go into TWS. See how many it breaks out. If it breaks them all out, shoot step shoot step shoot etc. Watch that it steps correctly. If not, SCAN RAID to break it out, again same shoot step, but because you are zoomed in, there is a potential for stepping to the wrong contact without knowing it. One cue is to watch the triangle flyout at the bottom, it shouldn't move much when you step. Once all shots are gone, back to TWS until active and then decide. If you break all four out in TWS, shoot step, etc - SCAN RAID only if necessary. Try to keep as much SA as possible by avoiding SCAN RAID/EXP as it may stop you from picking up a closer threat if you stay in it too long, or gimbal the target before you want to, it happens a lot.

Only way to undo an L&S is reset (or ACM mode), but if you happen to have DT2's you can swap them, maybe it wasn't clear. Double click almost always results in STT / mini-raster.

Single TDC action should be required, a double action (>.3 s) would command STT. Single action to make L&S, single action to unmake it. With an L&S already, single action to make another track a DT2, single action on same contact to make it the L&S and swap DT2 to previous L&S. DT2's are good for when you need to shoot specific targets in a group when there are multiple, or running an VID and you want to keep track of both as long as possible. Otherwise, EXP and stepping work well and avoid the DT2 headache.

If you push button (PB5) to TWS then the parameters stay the same. If you switch weapons and exit TWS via and ACM mode (most common, a quick boresight / undesg), then you get the weapon settings, which is a feature to help you clear the airspace ahead of you.

Manual can be used to terminate datalink to the missile without going into an ACM mode which can remove Link-16 track info - not sure if this is modelled or not. You can also move the radar FOV around too in MAN, but might as well do that in RWS. Normal flow would be to search and ID in RWS, STT for one shot, undesignate into TWS (Auto), shoot the remain contacts and leave or merge. If only one contact or targets mnvr, back to STT if necessary. It is there in reality, so ED put it in there, it is just not overly useful given the strengths of RWS information.

The above description was not always a feature, came in with 21X - so it may not necessarily need to be implemented. Only with an L&S selected and RWS and it goes into TWS Auto. TWS manual is seldom used.

So that's how its modelled in the game. In reality, turning the TCN to on powers the MIDS terminal but leaves it in essentially a standby state. Turning the DL to on will allow you to access a populated MIDS page in order to select the net you want, enter the time and date, as well as a few other setting prior to net entry. All of this admin is not modelled and you are in Fine Alignment as soon as you turn it on (which is a blessing in some ways). Side note, setting a channel to 127 actually disables that channel (voice A set to 127 will turn off voice A, same as F/F1 etc.) Turning off the TCN should not turn off Link-16, as there are times you need to turn the TACAN off occasionally. Both need to be selected to off to remove power prior to shutdown.

Correct, all those symbols are part of the Link-16 and SA Format / Radar Attack format displays. MSI is used to fuse multiple sources into one track file to avoid double targeting while giving an accurate (ideally) picture. All A/A tracks and Link symbols for A/A will appear on the Rdr/SA/Az/El, which I don't believe is how it is currently modeled. A/G tracks will appear on the SA Format and the HSI (one only) if designated by the ownship. We are getting there, but not quite modelled correctly. TX Desg, for example is only for A/G designations, as A/A are always passed unless turned off. Again, this is how they chose to model it, and it is not too far off.

It shouldn't be on the radar page, just the SA Format. It almost looks like an offboard hostile track, but the cross makes it look more like a moving surface track. Either way, you are correct in wondering why it shouldn't be there.

More likely hitting NWS with Link16 and stepping to a surveillance track, which is normal. Maltese cross on the radar says it should not be transmitting. If you get it with Link16 off, that would be different. Although it should not say RDR in the HUD as a contributor

If you can find a clear picture, you will see a white rectangle/square looking piece of metal that is just above the top part of the gear handle. This is the mechanical lock that drops down when WOW occurs, no need to pull up on the handle to check.

Any interrogations that respond positively should appear on the AZ/EL and Radar format. It is done a little artificially in DCS, but the options exist. The question was why limit the range, and the answer is to filter out returns of transponders that you don't want to see. It is purely a filter, does not do anything with the distance of the signal, which I think was potentially a source of the question.

Consider if you are interrogating Mode 3/C as well as other modes in an area where there might be civilian traffic. You may want to limit the range to 40 or 80 to avoid cluttering the AZ/EL or radar page with too many symbols. This is more of a filtering option, as the interrogation signals continue to travel regardless of the range you set. 80 is a good number as you rarely care about track files that will respond to an interrogation beyond that. Width-wise is as you describe, keep it wide and in auto unless EMCON is a concern.

Might have something to do with going manual TWS - that will normally terminate data link to the missile (not sure how it is implemented). It still has a chance to fly to where it last heard about the target and go active to find it. If you are taking shots outside Rmax and then terminating DL to the missile, I don't think it will have a very good chance of making it. So it seems to not be to far off. I guess the question is what have they implemented for data link termination, if anything - Manual TWS, RMEM, ACM mode, possibly other things.

I think it would just add another layer of unnecessary ground servicing issues - it would be abnormal to zero-ize the crypto unless compromised or landing in an unsecure location. It is nice to always have Link 16 work, not always the case.

Ai is your Airborne Interrogator, so in theory you colonize which modes you want to interrogate, and RX is the transponder, so what modes and codes you want to transmit. AI codes are more for searching for Correct Code, the one you specify next to colonized mode if you are looking for something specific - not sure if CC is implemented or not.