Vatikus

Azumuth and bar selection works incorrectly in TWS While in TWS mode, pressing either OBS17 or 18 should change both settings as they are fixed pair: 60/2, 25/3, 10/4. Also, when we have TOI as is now, no A/B setting can be changed - it stays locked to 25/3. This should not be the case, 10/4 should be available as well.

Currently if you enter from SAM to TWS the bugged target does not translate to TWS.. it actually drops from system target list. The other way around, TWS to SAM does translate correctly, the target stays bugged.

While I understand the current TWS is still WIP, I would just like to express wish that its implementation would carry the downsides vs STT and SAM spotlighting a bit better... The motive is that DCS M2K new radar implementation showed it is possible.. So... it would been nice that designator box and overall position accuracy would reflect the energy and resolution difference vs STT for example. This means that especially altitude information would reflect the wider radar beam and no monopulse processing which cannot pinpoint target inside the beam and place designator box dead on center around the track. Thus the further away the target is the more error it should have.

+1 .. this is new w/ this update

Set SetKBRate higher... I have seen you are using TEMPO command and 32ms pulse is too short for DCS to register keystroke. I am using 200ms and I do not have problems anymore.

+1 this feature has been broken for far too long already. Two flys in one.

What I wanted to point out is that if ED re-adjusts some values per request or whatever is the reason, if these are not synced across the modules, one ends with totally skewed relative performance. I.e. if thrust is altered in one and not the other you end in situation that does not reflect reality at all and end result can be even worse than some fsims that do not advertise themself to be as realsims because while numbers are off there, they still achive proper relative difference which is present in real life.

Ok that is fine as long as relative performance between the planes is preserved. If it is not, then it is pointless to have these modules at first place. (and we have seen that f18 vs f16 currently are not in such sync)

That would been nice indeed... like some mechanical "thumb" sound as throttle reaches full MIL at which time it hits the AB detent.

<64A> Vati F5

A active, yes F time of flight E kinematical evasion N notch

I worked with radars in real life with MTI/TWS and I know quite well how things work.

37.Sqn Vati - mig21

What I meant was that DCS' TWS in current form is overall too good - especially with maneuvering targets and ecm. And of course, it is then logical step that some people are wondering why not have SAHR compatible with it as it is so good. Fact is STT is used in real life more than it is usually percived in time when we have ARH & TWS...

Real life TWS is a far cry from games like DCS and that is the reason that most of the times one uses STT for ARH missiles as well. Once contacts are sorted, flight goes to STT as it is the only way to have highest quality tracking. Of course the newest AESA radars can do "stt in multi target" situation, but that is beyond the scope of DCS' radar generations.

This principle is nicely illustrated in the following video (~5:40)...

My squad noticed that aim54 ghosts stay on the map forever when using f6 view. The missile is not visible, however f6 will still track it... so server can end up with quite a list of ghosts when cycling thru with f6.

Not really. Please look at the video mvsgas had posted where the pilot is explaining what he is doing. He is using his left hand to help with pulling and keeping stick in the desired max deflection. Real control stick has much greater force needed than what we use in games (most joystick have max force what is the breakout force in a real plane :) ) and to go beyond the soft stop it requires excees of 10kgf.

to add what has already been written regarding advantage of center stick.. there is also this:

It would help at plane state feedback to have more pronounced airflow sound around the canopy for G/AoA/Beta Example:

up

To reproduce: - start cold - load HE bombs + fuel + 24j - startup engine and load F10 plan (5 wpts) - switch from BER to NAV - scroll walk fwd & bck weapon selector (it might take few walks) - CTD there is no log information or track because of CTD

Will we see a proper interference for pulse radar modes? DDD should show ecm, chaff, dense clouds... since you are already simulating various DDD controls these should be put to use ;)

I've asked Chizh on all mentioned bullet points when we got new FM... the answer was definite NO. He hinted that any change could only happen if 29 goes into FF from FC3.

MDI flir screen can be selected even w/o activated tgp As title says... to reproduce, simply click on tac mdi page button 6 (top leftest) when there is no indication for flir option