Looney

Hi DArt, I hope your new update also fixes the invisibility of the airfields in LotATC, we can't select the approach radar at the moment..

A month? We have to wait a full month to get updates? Just kidding, take it easy and we'll see you return fit and ready..

The AI doesn't recognize trees in the Caucuses map at the moment, so looking for cover is not easy to implement at the moment if you ask me. I agree with the points though, having the AI do something else than move of the road and stop would be better, maybe even have a panic parameter that it will just drive wildly around or something similar..

With regards to the hardware and internet connection, can you state what machine and connection you use for the server? This in lieu of rubberbanding and lag we (132nd) experienced on our server during one of our somewhat larger missions..

There are no cockpit doors on the Mi-8, only blister windows which you can open and close.

I can look around the correct gunner view but am unable to control the gunner using trackir or mouse. It'll fire if I press the mouse button but the gun itself won't move.

Use the CTLD script, the embark function from ED is borked and I woujldn't hope for a fix anytime soon.

From the github page: You can activate and deactivate a waypoint zone as shown below. When a waypoint zone is active, and the right coalition of troops is dropped inside, the troops will attempt to head to the center of the zone. ctld.activateWaypointZone("wpzone1") So, set your trigger zone, add a trigger once with whatever trigger you like and as last action, select Do script and add the above in the text window. Now, whenever this trigger is activated by something, the waypoiny becomes active and any dropped troops will try to move to the center of the waypoint..

I use the ff2 with the mi8 and have no problems. Sure you need to fiddle with the inversion of axi but that's it, works fine once setup.

use CTLD, that works great.

Have you checked the Axis Tune function to see if you have something inverted or some other option set there that would interfere with the brake axis?

Yesterday we tried slingloading CTLD crates with a hefty 24 knots wind. Everytime we flew into the wind and IAS went above 110-120KPH, the line broke. Only when we had tail wind were we able to go above 120Kph. We're wondering if this works as intended or if some tweaking is needed?

Open regedit and check under local machine and local user if your DCS modules are listed. If yes, check that there is a folder underneath each modules named KEYS, if yes, delete this for each module and start-up DCS, it should ask you to (re)activate all your modules. I should know, after a dead moptherboard forced me to upgrade CPU, mobo and RAM last week I went through the same procedure.

Anywhere you want, if you open the draw window, select edit and than load from file. You can choose any location to load your .JSON file.

For the second question, use the very good CTLD script as currenltly embarking seems to be broken. For the third question, also look into CTLD script. If it's a player helo that needs to do the dropping, they have to use the correct buttons :lol:

If this is the first campaign of the Mi-8. You don't need to set any frequency but you do need to fly pretty precisely over the small house where the range control officer is located, only then will he talk to you.

Well, according to an Mi-17 source on the web, the maximum transport speed with a slingloaded howitzer is 200 km/h: And than the US army states:

Ciribob, are you still working together with DArt to make SRS LOTATC compatible?

Weird, all I have is uh1h_cargo and nothing else...

Are the new slinbgload cargos in? I can't find them in the mission editor?

I like it, it brings some more functionality to the KA50 without going overboard.

OK, so I've tried every combination with every script disabled and still get the same error message. I made sure I have the mods loaded and everything but the DCSlog still shows the same error. I deleted every other script and even deleted everything from the mission file and it still throws the same error. I made an exact copy of my trigger lines in the mission that does work and still it throws the error. I am stumped...

I'll try, thanks Ciribob. I do have the feeling it's related to the Automan script as the unit name is __Respawn__ or similar so the Automan script respawns these unit upon destruction. Although the unit name is transport1, I believe the two scripts are biting each other. I'll test later tonight to see how things fare when I take away the _respawn_ name. Automan script: https://forums.eagle.ru/showthread.php?t=116968&highlight=automan

Is there a third party program that will allow you to review setting of flags, flag numbers and values and such? Like a debugger for LUA script files? For instance, I'd like to see which flags are set and what their values are, does anyone know of such a program? I've got logExpert but that does't tell me which flags are set and such..

Hi Ciribob, I tried unloading with a " fresh" install of CTLD and MIST using a simple mission and it works, the troops unload after giving the radio command. I then used the "fresh" CTLD and MIST and used them in our training file but it doesn't work. MIST and CTLD load fine but upon commanding the transport to unload, I keep getting the same error message: I've added both missions for reference. The training mission does use a lot of different scripts, perhaps that has something to do with it? 132-TRMT_v10_1.miz transport-unloading test.miz