foxwxl

Try changing the weapon and fuel quantity, it might need something to trigger the action.

So why is the helo invisible below 70 kts on APG73? Because they entered the notch filter which they shouldn't. Even the helo is hoving, the fast rotating blades on their head are still creating obvious doppler shifting with patterns. This doppler shift should be detected / tracked by morden A2A radar. Can U do this now in DCS ? No, U couldn't. That's the balance to give the helo players some cover.

AKG only auto center with axis input, keyboard & DX button won't be able to auto center, that's the design for the current version. I've talked with the team on this, and the answer is there is some technical issue to make the key input auto center, so it won't be changed, for now. On the player side, there are 2 opitions for a temp solution: 1. plug a gamepad such as XBOX on to your computer, using the X/Y axis as additional TDC input. 2. Setup a switch button in DCS, make a X/Y+switch of your stick as additional TDC input. Both of this gives U an axis input and auto center. I have even shot down a AWACS with this, piece of easy cake.

For some balance reason, Helos in dcs is hard to pick up by radar if they're not moving too fast. The doppler shift of the rotor may not currently considered in DCS, the HELOs DO notch the radar. So it's not the JF17's radar problem, U can encounter the same problem with APG-73 and APG-68.

AKG has a min/max launching altitude restriction of 500m-7500m and a launching speed limit of M0.9 implemented with DEC 19th update. If U're outside these parameters, the missile won't be able to launch.

TWS 3 BAR = 6.2° EL coverage RWS 4 BAR = 6.9° EL coverage

This issue has already been reported to team. But this need some time to tweak and test so can't catch up with this update.

Yep. Go to the special page of the JF-17. U can define all the sensitivity and Deadzone of the TDC input.

Thanks for the report. For accurate locating the problem, could U plz explain the exact behavior "no RWR warning" is : 1. HSD not showing red flashing symbol? 2. HUD not showing MSL LCH or Missile (Head on aspect)? 3. No sound indication through the headset (high pitch tone of beeping)? Thank U.

Magic IFF is working only for M6 this patch and only shows friendly. It might be change to a more FC3 style IFF(direct green / red) and disregard the IFF mode at a later point (Magic IFF only). (Still under discussion)

F10 marking is currently working for SP. The MP part may go down because some API issues. Already reported.

EFCS is for the emergency situation only, and design to give pilot control of the plane and landing ASAP. Not for the dogfight G override.

Try copy the MFCD viewport definition paragraph and plus the "JF17_" before LEFT RIGHT and CENTER MFCD viewport definition in the monitor config lua. I remember they have mentioned this once.(If I remember correctly) Since JEFF is using a 3:4 SMFD, they have tired some solutions to give U better way of definition the viewport without messing up the F-16 /F -18 viewport settings.

Master Arm ON, and switch to the GB-6 should begin the alignment of the weapon. It takes about 3:30 to full alignment.

Thx~:thumbup:

These files really helps a lot, now we can get a good MFD extraction, thx.:thumbup: BTW, my main 3D MFD now looks very very dark and not very readable, is that normal for these files ?

TFR and navigation pod (and the HUD) is fit for BLOCK 40/42 not the 50/52

LSS? Not implemented for current TGP on viper

Sorry, I mean the donor HAFU that haven't been captured by onboard sensor;)

Hello guys, I've got a small question about the MSI feature. On the last update, we finally get the donor HAFU on attack RDR page , that's a great feature. But the HAFU can not show target altitude as the SA page does. Is this a real jet feature or we will get the altitude info on Attack page on the coming patchs? Thank U

I know U get your experience from another F-16 game :smilewink: , but dcs AAM will lose a lot of speed when pulling G's or fly at low altitude which bleed out the missile's energy really quick.(which in that game missile's energy bleeding is somehow too slow especially when missile pulling G) But afterall, a game is a game, R77 can be VERY deadly(very low drag that cause Very Long range) in 4.32, but can also be so weak in 4.33 (also due to the very high drag settings). phenix has less range than AIM120 in that game too(high drag setting). All just base on game settings. Just learn the rules and respect them.

23-25nm for AIM120&R77? U must be kidding mate:lol: In DCSW,actual MAR for 120&AA12 is only 5-6nm for PVP at low altitude, 10-13NM for high altitude. Long range shots can easily be dodge by any experienced pilot. The huge drag of the phenix, will decelerate the missile VERY quickly after rocket burns out. And the terminal guidance turn will consume A LOT of speed (usually a 22G turn). So the missile do not have the LONG range that U thought against fighter, especially at low altitude.(still quite long compared with AIM120 or R77)

sometimes it does CTD without any warnings. All happened in MP and I was the RIO. 16GB RAM & GTX1080Ti on Caucasus.

20nm for AI 15nm for PVP firing at that range should give U a reasonable PK

same here when using radar slave mode, the Aim9 does NOT have the correct tone (this happens more often AFTER the 1st AIM9 launched)