All Activity

As you approach the targets and have George lase the target and then have him WAS missiles, he loads the target data to the missile and then stops lasing. This is roughly at 8600m. It's easy to miss because he was already lasing prior to you WASing missiles, so it didn't take the normal delay for the data to be loaded, but you do see it flash in white at the bottom-left of the High Action Display. And then, as mentioned elsewhere in other threads, he will not lase again until you de-WAS missiles, or fire the missile, or switch him to SAL, etc. You see the distance to the target continue to count down for a few seconds, but then it stops at 8400m, and George never never indicates he is in range (below 8km) and ready to fire. I took over after you got another few km closer to the target and when I gave George consent to fire, he said "out of range" and wouldn't rifle. I'm not sure why the distance to the target stops counting down at 8400m. Is this a bug, or is there some reason why it stops estimating the distance? Regardless, it confuses George into to thinking you are still out of range. So, the fix is either have George continue to lase even after the target data is loaded, or at least have him periodically squirt the laser to update the range so at least he is aware of when he is in range and can fire. Or if you really don't want George to lase ever again, give him some magic ability to know the distance to the target so he realizes he has crossed the magic 8km bubble and is in range.

Neither side holds any moral high ground. However one has remained consistent to their statement, the other side keeps throwing kerosene into the fire, in the hope that the more people who get burnt will flood the hospital that they start supporting the kid standing there with the box of matches. !!

I think someone new full well what the collateral damage would be, going straight to the nuke option

To my knowledge, it appears to be the samuire the F-16 to be MMC (Modular Mission Computer) compatible, e as the A-10, but on an F-16, and does not requnlike the JHMCS. This is why it is popular for ANG units to get it, as most F-16s in the ANG are not MMC-compatible. Though I do wish it was in DCS tho unfortunately, the file is encrypted so there's no good way to make it a mod

No, they're just holding the hostages instead !!

Because their not holding the gun..

Asked for a refund…lol. It’s an early access module, still in development. Try asking for these things in the wish list section and you may get more traction. These aren’t bugs.

this sounds similar, but our experience tonight (and this is on DCS 2.9.18.12899) is that in multiplayer, IAT actually causes LST to lose lock. Specifically, Apache 1 is lasing on laser code Romeo, and Apache 2 and 3 are LST on Romeo, they set LST to auto and their TADS immediately snaps to the laser spot. As soon as Apache 1 turns on his IAT, the LST of both Apache 2 and 3 immediately goes into scan mode, essentially they lost the laser. As soon as Apache 1 IAT is deleted, the LST of both Apache 2 and 3 snaps back on the laser spot again.

Can confirm. Got a nasty little surprise the other day in a MP server. No launch warning and if I recall correctly, nothing even on the RWR suggesting it was in search mode (though I cannot 100% confirm this). The most maddening thing of all is that I was actually able to reproduce this in single player a few times the other day, never saved the tracks, and have not been able to reproduce it since. As of today, still getting launched at by SA-11's with no subsequent RWR warning on the same MP server (though I know what to look for now).

У меня тоже не летят в цель. Даже по этой методике.

options-old 29Jul25.lua above is the options lua file I renamed in attempt to force DCS to create a new one. I ran DCS after I renamed to -old 29Jul25.lua and don't see another options.lua file in the same location. I'll try renaming the saved games DCS to DCS.bak and report back. Thanks for the responses so far.

Кстати да, был не точен. Как верно написали выше, Миг-15 первый полноценный модуль "красного" истребителя. По поводу Миг-21, я конечно на нём в жизни не летал, но довелось посидеть в кабине настоящего, боевого с включёнными батареями. Ощущения от модуля очень достоверны. (конечно же лично для меня) На тему его устаревания как модуля, полностью согласен со всеми авторами, кто высказался ранее. Модуль не ждёт, а просто требует своей новой итерации, с перерисовкой графики по типу F-5e, который как по мне сейчас очень классно сделан, и конечно же требует доработки систем (тот же тумблер для регулировки высоты сидения, или переключатель подачи кислорода и прочее... прочее...)

How come Razbam isnt being so forthcoming?

@BIGNEWY, et al: Here is an example of GeorgeAI lasing a target beyond 8km then not lasing afterwards. He designated the target approx 2 times from 9999+ meters. The range decreased down to ~8,400m then no more lasing. I flew up close until landing next to the target. All the while, he would not lase. I purposely did not change any settings because I wanted to see if he would lase the target. This is EXACTLY what I talked about in my previous thread here: George AI and AGM-114L Lasing and Fail to Fire Problems. See my track and MIZ file. 2025-07-31 GeorgeAI-No Lase.trk AH-64 GeorgeAI Test.miz

it turned out i had the wrong name set for the diffuse texture of the bort number in the lua file

I have absolutely loved this implementation! I currently use BogeyDope's VoiceAttack profile for my personal missions, but I really liked that your campaign actually used player inputs to play the sound files. Would you be able to share how you were able to do that? I would like to try to get that to work in my personal missions, if possible. Ever since your Arctic Thunder campaign, I can't start up my Viper without a crew chief!

I have artifacts around my bort numbers, does anyone know what causes this? null

Hello, this video covers the unintentional “Cobra maneuver” of the Mi-24 when pulling back on the cyclic, why it happens, and how to prevent and recover from it!!!!!! With this you should be able to turn and burn to its maximum performance!!!!! Enjoy the opening!!!!!!!! https://youtu.be/cxVypUj-_Lk?si=dx0trxzmsfCz_dw5

Yes, latest MOOSE version.

The wind had only a little to do with it. At ~150 knots on downwind, an 8 knot direct crosswind requires only a 3 deg wind correction angle. That makes a difference for big holding patterns, but for a fast plane in a small overhead break it's a small factor. A Cessna 150 in a 20 knot crosswind, though... FWIW, 1 nm sounds a bit too tight.

Not having become a lawyer just gets better and better every day.

Seeing a 55 percent tax would make a customer freak out just the same. I just wonder if it's legal to claim they are collecting a tax that is not actually directly payable by the customer to begin with. Again, I'm not saying wingwing wouldn't increase the price by just as much across the board to cover the tariff they already payed to import it, because I'd expect they would.

An update of all radio presets is now in internal testing. Just a bit more consistency across all missions, a fix for this issue from M01 plus named presets in the ARC-210. Yeah, I saw the exact same thing. The unit used as transmitter was trying to sneak behind a mountain. Gave him a jolt to gain good Line Of Sight, should be good now. Yup, another case of the actual transmitter unit being in the wrong place, good catch! All fixed internally and now in internal testing. I can't give an ETA for an update, hopefully soon.

thie graphic anomaly still exists as of DCS 2.9.18.12899 me and a friend will see it in multiplayer in VR, experienced on separate computers when we choose left or right gunner