foxwxl

Though the BRM-1 is not ready for buddy laser at the monment, the GBU12/16 is now ready for JTAC lasering attack(when the patch is out).

As the team have made the statement serval times, the AG EXP/DBS1/DBS2 are just placeholders ATM, so it's meaningless to discuss if there are bugs or not.

2.5.6 introduce some new fx into the DCSW, so the whole game is affected. JF17 HUD have beee fixed internally, it will be available when the update is pushed out.

Like I posted, this is the status of target: search target(raw contact)->tank target->system target->bug target->STT target A "solid brick" is just a tank target, it needs to be upgraded to a SYSTEM target(open squares with velocity vectors) first, before it can be bugged.

Fantastic Job,Deano :thumbup:

The WMD7 does not have auto gain auto level ATM, U should adjust the level for 0 or -1 at closer range. And the IR / CCD rendering do have some problem at 2.5.6, I'm not sure if this is a DCS common problem. Suggesting U using the BHOT and CCD channel, which should give U a better view than WHOT AFTER U adjust the level settings.

Bug confirmed, Thank U.

Plz attach the ACMI to further support the investigation, thank U.

I've just fly F-18 & F-16 against JF-17 on MP server these days, the SD-10 always show up correctly on RWR with a M symbol. I've not seen any SD-10s that without RWR warnings. Plz check both of U have the same game version, enter server that need IC, and the network is good. Thank U.

Make sure you have select the correct AFB & RWY to land, since the JF17 only show the AFB WPT not name, so better cross check the F10 ILS feq. with APR page ILS channel & the kneeboard ILS channel/feq. chart.

After U have a HPT, just press uncage, the seeker will slave to HPT and begin search(assume you have PL5 ARM & READY). It do have some bug at the moment(the elevation of the slave position maybe wrongly pointed), because of the radar elevation calculation errors. This has been reported internally and waiting to be fixed.

That's depend on status of the track file , the APG-68 will update a trackfile to tank target automatically after serveral ping. If you want shoot some guy, you will need a bug target, but if the target is just popping up on radar, it will take time before the track file can be auto upgraded. TMS UP can command the radar manual update a track file, so maybe 2-3 TMS UP is required before a target can be bugged if its a new pop up contact. search target(raw contact)->tank target->system target->bug target->STT target If you want to speed up the process, RWS->SAM chould be a better choice.

It's for the AA/AG Datalink operation, currently with the LINK16 MIDS already implemented, you don't have to touch any of these. With IDM, IFF IN/OUT will be needed.

With TWS, a TMS right will update all the track files to SYSTEM target, If you wish to engage multiple targets, just bug one target(tms up), fire, TMS right to cycle to next target, fire, then TMS RIGHT again. Only 1 TMS UP needed. And although the DL will brought IFF infomation, but currently it is bugged, friendly will also shown as enemy (very often). So TMS LEFT using the MODE 4 IFF on your own A/C will be a better way to ID the target.

In the RL, U will notice most time the PAF JF-17 will carry at least 2 drop tanks no matter what mission they are executing (except the airshow). So if they DO NEED the inner hardpoints, it's basically for some LARGE/HEAVY guys. And RL airforce usually do NOT carry a full loadout onto mission, so may be small bomb on inner hardpoints is not a very big concern for real life(just guess).

I would say, add a key binding to switch the profile up&down won't make much difference. U have 5 programm on the plane, how can you call out the exact profile U want to use by just a up and down cycle key binding.:smilewink:

Default MAP mode is to draw a basic map, EXP/DBS is not correctly implemented at the moment, the one in the game is just a placeholder. Buildings, tanks, shelters will all reflect the radar signal, its hard for the radar to tell what is what if the signal is static. So if U want to AG radar to show some "contact" then its either a moving target, or a very clear target on the sea. Ground tgt may be showed as a contact in some case, but its a good idea to use TGP to ID the static targets.

The final loadout for EA has been changed several times for getting updated information.

Base on the range of AAM in current DCS, missile will only be fired AFTER burnthrough, which means, the Jammer will only act as a HOJ beacon.

Sorry mate, the forum won't allow me upload such a big file:noexpression:

If the JF-17 is only on one side, M1 could be an easy way out, since all other plane only use magic IFF. Friendly JF17 with TRS off will show as yellow, so it can still be recognized. Once JF-17 is on both side, M6 INTR should be used to prevent IFF hack, unless you are sure its not a JF-17(eg. by RWR or TGP).And all friendly JF-17 should turn on their M6 TRS.

It's not about naming a WPT to PP1. Set all your route in ME, select the TGT WPT, use the "Navigation Target Points" function(a square mark right of loadout page) to mark your PP or RP, and write the PP1 or RP1 into the Comment area. DTC will load the PP/RP, if U do all the above correctly.

WMD7 need laser ranging to establish AREA track, the MAX laser ranging distance is set to 40KM(around 21.5NM), so U can not make a area track far from 40NM away like the LANTIRN did.

Change the AZ to ±30deg RWS or ±25deg TWS will speed up the IFF result display for quite a bit. The radar sweep 65°/sec , so large scan vol can result a very slow IFF reply display. I usually hold the IFF button for more than 3sec, or just bug any target in TWS, the IFF will start auto interrogation for the whole scan volume.

No such functionality according to the team. Sorry mate, U still need to use a guided wpn for moving tgts.:joystick: