tdk

It's a nice report, and I found the same thing in other modules such as Viper. You shoot at Rpi but it has a ridiculously high chance to hit successfully even though the bandit full gate maneuvered cold. AFAIK the Rpi assumes a non-maneuvering target, so I guess it's actually an AIM-120 bug or something.

The mark shows the current position of the knob The shortest dark bar should be placed center when the knob reaches the "off" position and the longest at the center when max, but in DCS it seems to be opposite

I found that the position marks (painted dark) of the 4 ICP knobs in DCS seem to be wrong. Most public sources show that the length of the dark bar is increasing from up to downward, while the opposite is in DCS. Here are some images (not from any manual but the manuals show the same way) that show the difference.

I dunno, the LANTIRN pod should have gone through a lot of upgrades when it reached 2007. There are some vids that actually show acceptable images of LANTIRN in combat.

...It made me confused. I'm aware the model of the pod is incorrect, maybe and the UI, but will the TV and FLIR image degrade if they change it back to LANTIRN?

Yes I just tried, no help

BTW I tried Syria, Caucasus and NTTR, free fly mission of F-16, and all ended in similar problems.

The MT preview actually performs worse than the past. My device: CPU: AMD Ryzen 7 5800H GPU: RTX3070 headset: oculus rifts I tried on instant flight, the MT preview caused more lagging and fps drops more frequently, and it also limits my fov I tried another headset which was meta quest2, and it's even worse, the fps dropped to 7 on the ground and totally unplayable dcs.log MT.trk dxdiag.txt

It indeed made me feel strange. And what made it even stranger was that it sometimes glided correctly even without laser, and sometimes didn't

According to Furiz, The issue is you need to start lasing immediately after releasing the bomb, the bomb will just turn to the ground instead of gliding further if you don't. If it's correct as is, i.e. you need to start lasing as early as possible, then no problem. But according to Frederf, it should fly according to its autopilot, which may mean that it should be trying to glide to get to the spi, but it doesn't behave like that in my tests, that's what confusing me.

We were using GBU-24 in F-16s, and we found something weird, the bomb went straightly towards to the ground after release. Then we tested it several times, it came out that if I release at 13k ft, it correctly glided, and if we released at 18k or like 25k, it went straightly towards to the ground. I don't know if it depends on the release altitude or something else, we just assumed the altitude to be the variable. I was using pre mode and other settings remained default. I was not lasing during all tests, I just released it and watched its behavior, I know it won't hit the target without laser, but some behaviors were just way too strange ,you can easily saw it turning to the ground early instead of gliding. 1-20230119-014326.trk

So we can't modify the CMS program without the IC fail now?

According to the HAF manual, EPU use hydrazine only if bleed air is insufficient.When the EPU is operating, we can maintain RPM about 80%-90% to prevent using hydrazine. But this is not how it currently works in DCS. I turned on the EPU, and changed my thrust setting, and couldn't prevent using hydrazine. Both hydrazine and air light were permanently on, which seems to be incorrect. I get it that EPU always starts with hydrazine, but it should be only using bleed air when it's sufficient, but the hydrazine light currently won't go off in flight in DCS. Oh, there's another issue, maybe not a bug. When testing EPU/GEN on the ground at idle power, it should cause problem such as blinking EPU/GEN light, but that won't happen in DCS now. Here's my track EPU IN FLIGHT.trk