foxwxl

Yep, wish our bind date master have time to finish a more complete manual.:D

Static object DL problem already been notified internally, and it is likely to be removed(except the static ship from SEA1/SEA2 or target under FTT) in the future.

Centeral tank have a G limit of 5.5G which is just not covered by AG1. And AG2 config checks for the wing tanks. But this is how it is, like the F-16 CATIII can still pull 9G and destory all this AG weapon pylon and fuel tanks, and it is still the only CAT III F-16 have.

U already did, once a ground target is sighted by AG radar, the infomation is now passed through the newwork. You will see a boat like symol on HSD(your JF17 teammate will see it too). (Note. AG datalink is still WIP, its function/behavior may change in later version.)

Our engineer has coded the FP-B for experimentation, but it has caused some bugs for FP-A and WPT copy/pst function, so FP-B is currently disabled.

Personally I would say, there is no much difference whether you have an HMD or not, if the jeff is still carrying PL5E II as its main SRM. It's very reasonable that PAF did not order HMD for current block of jeff.

Red pylons means either the station is damaged or the payload configuration in SMS dismatch what you have actually loaded. I think you met the second one. Upon reload you should reseting the SMS by loading in new DTC profiles or manually select the payload of the station and input the quantity.

Fixed internally and waiting the testing build to update to verify.

OK, I've further tested the BRM, and the rocket range/speed is somehow lower again. If you fire over 4NM, the rocket will pull very high pitch in the roll at terminal phase. If you fired at 4.8nm+, the rocket will roll ridiculous and likely to miss. The problem has been reported to the team, the engineer will look into it. Thx for the report.

I've done the test again on MP server with a different axis(warthog joystick main X/Y axis with a switch modifier). And the axis has no problem controlling the TGP in MP. And from your video, I see the axis do move the TGP, but was inconsistency. I think you may focus the problem on your windows or logitech software. You should try other axis hardware or configuration to confirm if it is a logitech software problem. And if you simulate the axis with logitech software,you should check whether the CPU usage is too high in MP or logitech software conflict with other software. Also, logitech software can simulate the mini mouse to a mouse or keyboard settings(in my old X52,I set mini mouse as keyboard input to work as TD), if you can not find the problem, you can try these layout.

G limiter only protect airframe not stores/pylons. So max G under limiter may still break something on the pylon, especially with AG1.

I don't know why you think this as "unrealistic", since the radar has pickup these contact, you've got a X band fire control radar which mean to be precise. If the radar can pick them up, the radar can get their position and coordinates, there is no problem to broadcast these data into DL newwork. If you know the f-16 well, the IDM can datalink AG radar cursor position or waypoint data as well.

Sorry, I can't tell the difference, I'm using the raw axis of XBOX 360 GAMEPAD.

Watch out your speed and G pulling. Remember this is a beam riding wpn, and it is only a 90mm rocket, not a big missile like S-25,even the vikhr has a diameter of 130mm. These means: 1. BRM won't have a very long range(in fact, quite short, 5-8km in RL), if you shoot too far away(when JEFF was released, it can shoot 8nm), the rocket will lose all its energy to track and fly. 2.Beam riding need the missile stay INSIDE the laser beam. If you fired and pull up, the laser beam(the LOS of your plane and target) is greatly changed. thus the rocket has to follow the beam to pull up, it can not fly a straight line to the target like a SALH missile. Now think again the small rocket's initial speed, the BRM will miss, if you fired too far / pull up too hard.

There is SALH scheme in DCS, but the rocket won't spin for this scheme. And the wpn should be spining in filght, so VIKHR's scheme is used after considering all these adv. and disadv.

Futher test was done just now in an MP server, my axis can control the TGP without problem. Plz check your joystick and SST settings.

The current scheme for BRM is based on VIKHR, which is laser beam riding. So buddy laser may not work well in most scenario.

IE. If you are diving down to shoot the RBM, and you pull up hard and fast right after the launch, Rocket may lose guidance because the laser beam is too fast for the rocket to catch up with.

I think you are describing something BEFORE the patch which EL compensation is wrong calculated.

In DCS controls configuration, look down below, see the button "Modifiers", press ADD, then select a device and select the key you want to use as a modifier/switch. After all set, back to axis command, set the TDC axis, but plus the modifier/switch you just set, and press ok. Modifier is that you should HOLD the button to change the function, Switch is that U press the button the toggle between function. My test was done with the latest OB build, last night.

The basic coding for HMD/IRST has already been done when the aircraft is released, but since no JEFF is currently equiping HMD or IRST, they will stay at the engineer's laboratory.

If U do want to change TGP between points, best to mark them first, the TGP can then be slave to the current SPI(selecting the MARK points).

No, do not dive, just ingress with low altitude and high speed(ie. 500ft 550kt), align with the runway, release all the bomb on the pass and get the hell out of there before getting shot down.

The BRM has a short range compare to the initial release, a safe range is below 5nm for a sure hit. If you fired too far away or manoeuver too hard(it use laser beam riding scheme at now), the rocket will lose the track.

Ok, I've viewed the video. The problem is the MODE you are trying to use the HUD designate. Hud designating SPI is current working in AUTO(CCRP) mode, so it is behavior strangely when you select the BRM rocket. I'll confirm whether it should be used in DIR launch mode. THX for the report.