FixieRider

@Polychop SimulationsI noticed a comment on Barundus' latest video on the Kiowa that I found interesting: null That's a fairly substantial change from the last official statements on the matter. Did ED change the SDK to make MC easier to implement for you? And does this mean the MC aspect of the Gazelle may also finally be fixed so it works?

I have a fused spine, and much like the physical contortions required to boresight the IHAADS in the apache, there are just as many awkward contortions required to pause track ir, re-center the camera, then adjust the camera using the keyboard binds to get the IHAADS aligned properly. While this is, no doubt, very realistic, I'd be greatly appreciative if there was a "cheat" or some other way to force an accurate boresight on the IHAADS so I'm not spending two or three times as long boresighting than my buddies who all haven't been betrayed by their bodies.

Did this function get removed from the tomcat at some point, or is it a bug that it's missing/been swapped with GND MAP? I cannot find any mention of it in the changelogs, and the web-based manual still references it in the text of the TWS section of Weapons & Weapons Employment Overview, but no where else.

sinuos, check here: https://github.com/ciribob/DCS-CTLD#create-radio-beacon-at-zone You need a zone, and then you put a 'do script' trigger to create the beacon.

L̶o̶o̶k̶s̶ ̶l̶i̶k̶e̶ ̶R̶a̶d̶i̶o̶ ̶B̶e̶a̶c̶o̶n̶s̶ ̶a̶r̶e̶ ̶b̶r̶o̶k̶e̶n̶ ̶i̶n̶ ̶2̶.̶5̶.̶6̶.̶ ̶ ̶S̶c̶r̶i̶p̶t̶ ̶t̶o̶ ̶c̶r̶e̶a̶t̶e̶ ̶t̶h̶e̶m̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶,̶ ̶a̶n̶d̶ ̶t̶h̶e̶r̶e̶ ̶a̶r̶e̶ ̶n̶o̶ ̶e̶r̶r̶o̶r̶s̶ ̶i̶n̶ ̶t̶h̶e̶ ̶l̶o̶g̶ ̶f̶i̶l̶e̶ ̶t̶o̶ ̶s̶a̶y̶ ̶w̶h̶y̶.̶ ̶ ̶C̶T̶L̶D̶ ̶r̶e̶p̶o̶r̶t̶s̶ ̶a̶s̶ ̶l̶o̶a̶d̶e̶d̶,̶ ̶a̶n̶d̶ ̶n̶o̶t̶h̶i̶n̶g̶ ̶e̶l̶s̶e̶.̶ EDIT: i'm a dolt -- i renamed a trigger zone and didn't change my lua to match. derp. carry on, nothing to see here! CSAR_miz_log.zip

I had this as well. Uninstalling the Jeff completely, then re-installing it fixed the issue. Worth a try, since it's not a huge download right now.

This doesn't really answer the question though. If I don't pay for the new Ka-50 paid module, will my original Ka-50's lighting, and other textures be updated/fixed?

Why on EARTH is this not natively supported in the DCS World client!? Works great, thanks Grimes, you're a life saver!

I own several SP campaigns, and I almost *exclusively* play MP. You're using a forum thread nestled 3 levels deep as a basis for gathering metrics for this reply of yours? I have no words. Edit: MP NEEDS HELP. Felt like I should at least voice support directly to the OP, since so many replies are being removed as OT.

RWR displays F/A-18 and M2000C as U instead of their custom icons enumerated in the manual. Have only tested in MP so far.

Interesting, we could see him on the F10 map, and others could F2 view his aircraft in flight. We'll try to recreate, but sounds like it might be a strange DCS export bug more than a LotATC issue.

It was a human player. I'm going to test the mission again and see if i can get it to do it again before I send it to you.

DArt, any idea what might cause an A-10C to not appear in LotATC at all, despite flying well within the detection envelope of multipe radar sources, and at 5k feet AGL, and 190kias? He shows up on the game map just fine, but LotATC refuses to pick him up.

DArt, I also noticed today that the Runways with ILS are incorrect for Senaki. RWY 09 is the ILS runway in-game, but it shows as 27 in LotATC. I think it's just mislabled in LotATC, since aircraft show up to be on approach to the correct runways on the glideslope approach graphs. After some checking, ILS appears to be reversed on all airfields in LotATC. In game Airfield info: Active Approach Windows:

Right on, thanks for the quick reply, Devrim!