HoneyFox

I think that's the problem. I believe this issue doesn't exist on F-16C/A-10C, so it's probably not taking the burst height into account. Probably neither for the wind force of bomblets, as I've experienced bomblets shifting quite some distance after their parachutes are extended.

I met this issue in a SP mission as well. I also tried to move into front seat, and found that the trigger will be automatically unhold even if I've been pressing and holding the trigger: the laser designate "><" symbol only appears for a fraction of a second and then disappear, this makes it impossible to guide laser hellfires, nor to provide target track for radar hellfires. And HMD/TADS mode is also somehow automatically switched as well. But when I play this mission again later, no such issue occurs. My guess is that somehow George is running in some abnormal state of AI logic, which ignores player's slave command and also keeps giving input even when I'm in front seat.

GBU-54 works fine, similar as GBU-38. One small issue is that, in my test runs the auto-lasing often fail to work for it, but you can still manually lase the target and it will track the laser spot normally. GBU-27/28 can be dropped, but they do not track laser spot right now...

Now I would rather rely on the azimuth cue of TGP. By placing it at 12 o'clock it would ensure that I'm pointing towards the target. Wind correction is often not needed because LGB does have enough sensor FOV to pick the laser spot even if it has some wind drift.

I found that the F-15E's roll axis has its auto-center rate (when using keyboard control) reduced a lot since the recent update, this makes the plane quite hard to fly using keyboard as it's very easy to get into PIO in roll channel. Although most people use joystick to fly the plane most of the time. In case you have to use keyboard to play the game, this would be a problem. Edit: Yaw channel seems to have similar change as well, but since it's rarely used, it's not that serious.

Same here. and this probably explains a lot of cases in which LGBs dropped towards a much outdated designated point, giving them larger trajectory error to correct, sometimes too large that the actual target has already got out of the seeker FOV completely.

I wouldn't believe that the current parameters of GBU-24 in DCS is reflecting the real guidance, unless the engineers in Raytheon that designed the guidance law for it were really that dumb + the military that would receive the weapon were extremely tolerant of such high probability of missing targets. Reflecting real guidance & steering in both capabilities & limits is the ultimate target of realistic simulation, that doesn't mean you can/have to reach that target in one step only, even ED couldn't achieve or haven't achieved that yet in many cases (JDAM, JSOW, lots of AAM and other weapons, etc). The current situation is, you would prefer using GBU-10 instead of GBU-24 to achieve high probability of kill, which is simply embarrassing. Since we don't have the source of the real guidance parameters (I'd suspect if ED has real guidance parameters/control diagrams for any other guided weapons as well), the next best thing to do is, to update the weapons with another set of parameters that also has no real source but at least shows closer combat performance to the real counterpart. Anyway it's kinda off the topic so let it just be some info sharing post.

No idea, I either play single-player mission locally with modifications, or restore the game to be vanilla when playing online. Never tried playing with modification in server that does not enforce ic before. I don't know how DCS deals with the movement/impact+damage sync for these weapons.

Small update (probably a bit off-topic though): For GBU-24 control law issue mentioned above, I made some tests and I think I've found a better set of autopilot parameters as follows: Knav = 6, -- was 4, Kbias = 3.0, -- was 0, Kpitch = 2, Tf = 0.2, Kd = 3.5, -- was 2, Ki = 15, -- was 10, The bomb will have less oscillation at terminal distance (<100m), higher probability of hitting target directly, and is more likely to have a steeper impact angle (55+ deg or so, likely due to the increased Kbias value). While modifying these would definitely make it not passing the server validation, I think it's still worthwhile sharing them. (probably ED could also do some more tests based on these values and further improve the bomb performance?)

I have a question about the trajectory of AGM-114L in LOAL mode. It makes sense to fly a little bit sideway to make the active-radar sensor "feel more comfortable" detecting ground targets. But the missile still keeps this off-boresight angle when it's reaching target pretty close, which often causes difficulty at the terminal phase of the trajectory. (shown as the first case in the picture below) My question is: since the missile should be able to lock on target when it's close enough (just like how LOBL mode works), why doesn't the missile stop flying side-way and go straight towards the target so that it will have a more straight terminal trajectory? (shown as the second case in the picture below)

One thing to add: the GBU-24 actually has some guidance issue as well, it uses insufficient gravity compensation in the mid-phase of the trajectory and this leads to trajectory being too shallow, causing the guidance law to do pull-up when getting to the final ~80m distance to the target. However. this pull-up is over-done and the bomb would fly right over the target and impact the terrain 5~10 meters farther. GBU-10/12 however, despite using more primitive bang-bang control law, has good terminal accuracy hitting target. Edit: By checking the autopilot parameters of GBU-24, I found that the parameter "Ki" (likely to be the coefficient of integral part in some PID controller) is set to 10, which seems ridiculously large (especially compared to Knav=4 & Kd=2), and is suspicious to be the culprit of the "over-done" pull-up. I might try tuning down this parameter a bit (and increase Knav for compensation as well, don't know what Kpitch does though...) and see if that could mitigate the problem. Edit2: Seems like GBU-24 is really heavy which means it heavily relies on Ki to compensate the gravity. Perhaps a better way is to keep Ki and tune up Knav & Kd? Keep testing...

In this single-player mission, I try to use GBU-28 at the center pylon to engage the bunker. With TPOD autolasing the target and using either DIRECT or AUTO mode, the GBU seems to ignore the laser spot completely and flies in a straight line (instead of going ballistic) towards some open space nearby. I then go to the mission editor and check if its laser code is not matching, it is 1688, matching the TPOD's. Finally I try to change the GBU-28 to GBU-24, and GBU-24 works. So probably there is something wrong with GBU-28? (btw, GBU-28 doesn't seem to be an available weapon for F-15E, I cannot find it in the payload editor so if I change it to GBU-24 I can no longer switch it back)

I found that the gun's laser ranging result would slowly change with time even if my helicopter is landed on the ground with wheel brakes enabled and is aiming the terrain in front of me. In the screenshot you can see the ranging result is ridiculously large and it's actually continuously increasing at a rate around 1.0/minute. (but it seems to be capped at 15.0) Another screenshot showing that the nearby vehicle being targeted. Laser ranging shouldn't be affected by INS, so I guess it's because DCS is calculating the laser ranging result between the laser point's location and helicopter's INS location instead of helicopter's actual location. BTW, I also found that the AUTO TURN TO TARGET is also affected by INS time-accumulated error so it will not be able to even roughly aim towards the target (off boresight angle could be as large as 45 degrees or even bigger).

First select HMD as sensor, (open WEP page, click GRAYSCALE for better visualization), then use TDU's Brightness rocker to turn off HMD's FLIR overlay. Finally switch back to TADS sensor and that should be done. Actions in () are optional.

JF-17's CCRP mode is slightly different from other a/c's design AFAIK. when using dumb bombs, it's same as others: you need to hold pressing the pickle and the bomb will be released when that small box moves down passing the FPM symbol. when using laser guided bombs however, it will release the bomb whenever you press the pickle just like in CCIP. The small box is just providing you with timing reference. This actually gives you a release window, which allow finer trajectory control of the bomb. (slightly early-release has better chance of seeker acquiring laser spot but will have a shallow trajectory while slightly late-release risks missing the laser spot but can achieve higher impact angle which may deal higher damage to some targets)