Looney

Halon won't kil you, it's the bromide acid that can cause damage. Although not advisable, you can stay in a room that is being filled with halon but generally not recommended :).

Where is the most left switch? On extinguish or test?

Use the MOOSE script and set the missiletrainer. This way, you can expend your ammo but you won't kill anyone. It doesn't work for bullets though, so you'll need something else for that.

We usually use a MANPAD for JTAC duties, be it human or AI controlled. Set it to invisible and it won't engage any ground targets and stay where you put it..

Yes you van use the script together with CTLD, in fact, both scripts take each other into accound already with the naming convention of units so that one unit can use both scripts. E.g. Medevac###

What was the solution?

You're getting there :) The output of S_EVENT_SHOT is a table according to http://wiki.hoggit.us/view/DCS_event_shot So, that table is filled and returned at every shot. What you need to do is check if an entry in that table matches the correct weapon. Event = { id = 1, time = 14:00:25, initiator = M109, weapon = 155HE } Up front, I'm no LUA expert but from pseudo code, you can get a good idea of where you need to go with any code. On S_EVENT_SHOT Check the line weapon in the table to see if it matches 155mmHE (or whatever code used for artillery). Alternatively, you may want to check the initiator to see if it matches any artillery unit you want to track. If that weapon or unit type matches what we want, set flag XX to YY End Alternatively, you can have the eventhandler cough up a number which you then use to set a flag so you can check wether that flag has already been set or, if you really want to, add that event to a flag via a counter.

There are at least two pages you should read up: http://wiki.hoggit.us/view/DCS_func_addEventHandler and http://wiki.hoggit.us/view/DCS_event_shot With those two, you should then find the ID which a 155mm shell has and note it down. After that, start working on (pseudo) code So, when a 155mm shell is fired, find out who fired it and if the side (blue or red) is correct, set a flag. With Wrecking_crew's example and the above pages, coupled with some .LUA tutorial should give you enough tools to come up with a basic flow of LUA scripting. If that fails, post what you have and I'm sure the people here will help you out.

Best to use a few waypoints as meeting points and using some sort of scripting to allow the convoy to regroup. Otherwise you'll end up with an ADA element engaging aircrafts where the rest of the convoy troddles onwards out of range of the ADA..... :D

The F10 menus that went missing are radio message to this specific unit, not CTLD related. So, the JTAC uses the F10 menu to "check-in" with a Ground Force Commander (GFC). The JTAC then gets a list of radio options under F10 to show GFC Intent, threats, friendlies, artillery and so on. So, before the JTAC is airlifted, these Check-in and radio messages work flawlessly. But after the JTAC MANPAD unit is picked up by a helicopter and dropped at it's new location, the Check-in and assorted radio messages are not available anymore to the JTAC player.

Use an event onlanding or something to spawn a new tanker that takes up the old one's patrol.

It's on and off with regards to the ability to carry troops in the helicopters when it comes to ED. Sometimes they fix stuff, then they break it. Using the CTLD script allows for a much wider range of options and a reliable method for troop transport. The only thing that doesn't get added is the weight of troops onboard but that's basically it.

I was in the same spot as you, ended up biting the bullet and bought the BS2 module for DCS world. Even with customer support poking around on my system via Teamviewer were they unable to remedy the situation.

In two weeks ..

Standard weather DArt, no change in QNH in the mission. We'll run some more tests and I'll make screenshots.

DArt, we're seeing the QFE calculation in LotAtc is off by quite a number. LotAtc shows QFE 721mmHg whereas the Mi-8 altimeter was on 730mmHg. Same goes for the Mirage in mBar and A10 in inHg. Even with the field elevation of Tblisi being 1521ft as opposed to my 1540ft, QFE was still off.

It's been reported and they will fix it: https://forums.eagle.ru/showpost.php?p=3108056&postcount=867

The UH1 module has a slider that allows you to set the accuracy of the door gunners. The Mi-8 doesn't have this feature. While I fully support a door gunner that isn't accurate, having a door gunner that rarely fires (back door gunner) or waists 3 full ammo boxes on 1 person of infantry from 15 meters away isn't good either. Is it possible to add the accuracy slider to the mission editor just like the UH1 module?

There are problems with the AI gunners, it's been reported a couple of times, no news yet though.

Oooh, top notch! Thank you! Can you tell us anything about the accuracy of the door gunners? Is this being looked at?

IAS is just that, it doesn't show you ground speed.

Or, your INS hasn't aligned yet because you've started up too fast or forgot to turn it on. The INS needs some time to get ticking, once it does though, your speed will show in the HUD and you know the INS is aligned and ready.

What have you tried so far?

Really nice! Can the LSLLC be a dashed or dotted line? As a colour, to not confuse it with Decision Height and altitude lines, perhaps make it Yellow or orange? Great stuff on the azimuth, love it!

Is the garbled voice comms when two frequencies are used at the same time solved now?