sLYFa

Louder ECS pleaseee

That would be awesome, thanks! Its the little things that (also) count

The F-14 had a bunch of maneuvering limits in the supersonic speed range. These were not due to a performance or control authoritiy limitation but for stability reasons. The glove vanes helped a little with that as they countered the center of lift shift occuring at supersonic speeds.

Well they did it right for the B so there is still hope...

Could that be changed? The reason is that if you use hand controllers in VR, you have to turn your hand upside down for a right click, physically performing a switch up movement while the switch actually moves down.

Well during takeoff its not much of an issue since the INS will still indicate the correct direction towards your waypoints and Tacan radials are also unaffacted by this (they are in DCS though). The AHRS will eventually sync to the correct magnetic heading and keep it until you trap, where it would probably sync to some wrong heading but thats not an issue since you already landed.

Flying the correct heading on downwind is absolutely critical if you are far back in the queue (i.e. have to break late). Thats why you crosscheck the boats heading with reported BRC as you fly over the boat in the stack. If you are doing touch and goes (or full stop landings and goes), put the AHRS in DG mode before you land, this will make it insensible to magnetic distortions on the boat, but heading may still drift over time.

The director also signals "launch bar up" which he shouldn't (and doesnt for the B)

Which is now impossible in DCS (at with PD) since an AS-4 flies well above 1800. Hence the original question whether the current implemention is really correct. Or is there another way to pick up fast targets head on in a look down situation?

yes, if yours and your targets groundspeed add up to above 1200kts (flying straight towards each other), you wont see the contact with the aspect switch set to BEAM, which is the default settinflg.

Default setting is 1200kts closure. Jester never changes that

last patch (16.06), its in the changelog

Its true that eliminating the launch platform is the primary goal but IIRC the capability to target the missiles themselves was also there. I've read somewhere that one of the benefits of the 54C was improved fusing which greatly improved pk against missiles. Anyway, a Jester command for the target aspect switch would be much appreciated.

But wasnt the F-14 specifically designed to also intercept supersonic ASM?

So the target aspect switch is now affecting radar tracking.I wonder though if the current implementation is really correct. Even in "nose", the fastest closure rate you can get is 1800kts. This can easily be exceeded when intercepting fast targets (e.g. ASM) and/or going fast yourself. Is that really how it worked? Stay below 1800kts closure or you loose your radar contacts. Also, the switch does affect PDSTT, meaning lock will break of you dont stay within the respective closure gate. From how I understand the manual that should not be the case.

A or B? The A calls "hornet ball" ever since release, B should be correct though.

While the burble itself doesnt change with the aircraft flying through it, its effects can be very different depending on airframe. Making the burble aircraft specific (i.e. part of its FM) is more reasonable IMO than having a global effect for all AC.

While the keybind for increasing rotor rpm does work (the switch on the collective moves and rotor rpm increases), the keybind for decreasing rotor rpm does not.

Must be a joystick input issue. Never had this in god knows how many hours in the DCS Tomcat. FFB is known to cause issues with the Tomcat

approach button is not ICLS but the comm channel you have to switch to for the approach controller (not modelled in DCS)

There is a discount if you buy two licenses at once but if you already have one that won't help either. Btw its the same if you want to use the Supercarriers (both a license to spawn on the boat)

no

pleaseeeee

А треки мой смотрели? Посты мои читали? Ещё раз, когда вертолёт висит, ДИСС показывает правильную скорость снижения и с входом в режим ВК тоже всё правильно. А на скоросте 30км/ч слишком рано входит в режим ВК (3.5 место 5).И вы уж извините, но 30 полётов я вам записывать не буду. Те три точки, который я записал (0, 20 и 30кмч), вполне достаточно, чтобы показать проблему.

Про реал не знаю, а в ДКС как раз так, как я писал. Запаздывание есть да, но в снижении с постоянной вертикальной скорости вар. пудет показывать правильную скорость а ДИСС с ошибкой. Проверьте сами, уважаемый.