escaner

TDC (Throttle designation control) press for locking in BVR modes. Undesignate has many uses, one of them is dropping the lock. Rolling inverted also works right now for this...

Yes, it should mark the middle point of the stream of bombs, both in ccip and auto, as it happens in the a-10c. Even the manual bombing tables compensate for this.

The animation takes a while to disappear, but the fuel flow reading drops much faster

I would add speedbrake out at the break and check autoretract after flaps full. Also perform the before landing checklist in downwind before the 180 turn.

Your mods are compatible with TARGET software? I mean, you can e.g. map key presses to the TDC (or any Warthog axis) in TARGET, which solves the F-18 issue with the TDC. The same is possible with your mods, right?

Most HOTAS controls already have that AB detent (I have an X52 and a TH Warthog and both do), there is no need for a software emulation in these cases. I understand the point behind these AB lift keybindings and how they can be useful in some controllers, but there should be at least an option to deactivate them in the module properties as they are an artificial feature and a drawback in many cases.

Same here.

Hi, All EFIS systems that I know allow to center the COURSE and the HEADING BUG, normally by pressing their respective selection knobs. Obviously in the F-18, being a 3-way switch, it is not possible to press them, but is there some way to do that function? I know it is possible to input the heading in the CSEL and HSEL UFC registers, but when you get used to simple nice features, you get lazy... :) Thanks!

Most HOTAS controls already have that AB detent (I have an X52 and a TH Warthog and both do), there is no need for a software emulation in these cases. I understand the point behind these AB lift keybindings and how they can be useful in some controllers, but there should be at least an option to deactivate them in the module properties as they are an artificial feature and a drawback in many cases.

Same. Mk 20 were short in a dive and long in level bombing for me. Ripple also seems to have its issues in auto at least with gp bombs. Will try further...

If the position of the switch that you have selected is sending a DX input code at the start, then the module will read it and will set it to that position in the sim. If it is in the neutral position, which does not send any DX code, it will not sync. I have all the radar switches mapped in my Warthog (bars, PRF, azimuth width, projection, EM/SIL, etc) and this is how it currently behaves.

It does not work because the M2000 module does not sync the position of the switches in the peripherals with those in the sim.

I was doing a quick test with both AA yesterday and it looked like changes didn't take effect until I restarted DCS. It also seemed that the screenshots with both MSAA and SSAA inside the cockpit were darker (outside screenshots were the same), but that might be due to lighnings from the storm, will try again with more consistent wx.

You can just activate e.g. FXAA in the Nvidia control panel. It is a 2D AA and will smooth the whole image, but quick AA means lower quality. Personally, I don't like any of these postprocess AA algorithms, but this is one of the few options in the control panel that I have found to actually work with DCS. About SSAA, it was effectively phased out by MSAA years ago, the later being much more cost effective with similar results. But with the now more extended deferred rendering techniques, it no longer does such a good job.

Negative

I agree. I would first finish the aircraft systems (actually both AA and AG radar modes, RWR, bombing modes, moving map, etc) and then add external stuff more or less in chronological order maybe with reasoned compromises, eg something like: ALQ-167, TGP (even though it is not a Nitehawk), LGB, HARM, Harpoon, AMRAAM, JDAM, HMCS, AIM-9X, SLAM-ER, etc. This way we can start simulating early conflicts in this aircraft and then go on from there.

Here in chap 2 they show it. Instead of moving them together, for small power changes they move them in little alternating steps: left, right, left, right... same as walking. :)

In this screenshot the problem by the OP can be seen, with a SAM shooting and the warning just in the middle of the RWR. Actually there are 3 SAM systems in the field ahead (SA-3, SA-6 and SA-8 ) yet they all appear as UK. There is also a Snow Drift (SD at 8 o'clock further away which is correct) BTW, the Euromissile Roland is not from the United Kingdom, it is French-German.

Agree. And also many SAM systems appear as Uk. Unknown, I guess instead of their type, such as SA3, SA6...

I watched it a few months ago and enjoyed a lot. Unfortunately didn't find it in DVD and the Youtube videos are not that good quality. It has lots of nice HUD footage, there is a lot more to the eye than the narrator says. I vividly remember a sequence where one of the trainees shoots a simulated AMRAAM and then tries to follow up with an AIM-9, uncaging it up to three times but the seeker never tracks the target.

Thanks for the clarification, AndrewW!

Yes, just lean to the right until they are both aligned. I read somewhere that nowadays it is also used to check the helmet mounted display alignment, but not really sure about that.

It is and old style iron sight for backup aiming, as used in the WW1 aircraft or most small arms.

Yes, could be a typo. I see that the ALQ-167 is basically a training ECM pod but it was actually used in combat during the Gulf War. Thanks for pointing that out. We are not getting that one in DCS, right?

In this text (see attachment), "MRT" Fox explains how his Hornet flight had an ALQ-67 pod the night he shot down his MiG-21 in the 1991 Gulf War. Anyone has information about this pod or even pictures? I cannot find much about it. Will there be anything similar to this in the DCS Hornet for immersion recreating these missions?