Whisper

As much as I agree with The M that it is possible to simply do everything in Gazelle with the X-55 twist axis, because I've done it before quite lengthly, I just cannot recommend sticking with only X-55 twist. Pedals are a game changer for choppers, so go for it.

whatever, they implemented an option as some asked, they then had to make a choice between 2 options, that means supporters of 1 are going to be happy, supporters of the other are not. There are arguments for both sides, so people will have to deal with the choice. You want Razbam to run a poll for each and every choice they make?? Why do people absolutely want to be right ? :) No one is right here, it's a question of choice, and that choice has been made by the people actually DOING the product. Let's go past it.

Because it's a mission-wide decision. Exactly like the INS auto alignment that can be forced by ME.

And a grip of steel, you'll end up with a sore wrist pretty fast, that damn bird requires a lot of rudder in low speed ;)

What joystick/hotas/rudder do you have?

As long as it's an ME option, thanks to Zeus hard work, there is no problem, certainly nothing to warrant 10 pages of rants, to which I add my own ... :P @everyone : please, re-read from the beginning, it's bordering ridiculous. Zeus announces the feature, someone ask if it could be a ME option, and BOOM, tons of rants appear. An ME option, is it THAT hard to accept??? oO

Thanks for the info!! Gotta do that

Nope, I was just investigating the fact that the tower answers the first time COULD BE the bug .... simple

ICS switch on "Radio" ? Actually, just make sure the title of the Radio Menu appearing when pushing the trigger is "R-863"

As far as I've seen it, Moose uses DCS detection mecanism through use of getDetectedTargets (http://wiki.hoggit.us/view/DCS_func_getDetectedTargets). Integrating MBot script would require quite some changes.

Allright, I was searching for Alarm State on the wrong type of units (I had a plane selected), I found it back :) Thanks!

Hello, Since 1.5.5, I'm under the impression that a ton of options have changed or appeared in the unit behavior control options. The whole troop transport system seems to have been overhauled (no more "disembarkFromCargo" on troops, but a new "disembarking" command for vehicles) to the point of being non functionnal. The "Options" and "Command" available in advanced options of waypoint seem to have changed a lot. I can't find ROE "Green" or "Red" anywhere, ROE options have changed, and I found a lot of new possible options/commands. Has ED released ANY comment or documentation about this? Or am I dreaming and nothing changed? :) Have people experimented on these changes?

I hacked my way into it already ;) (ugly static kind of reference to Moose libraries, but it works, and I promise to not open any ticket on it before official ;) )

Trying to use Spawn-Randomization branch, but the new Moose.lua script loading puzzles me :) Where to put Scripts/Moose directory?

AFAIK the FBW reset button puts trims back to neutral. It's below the AA/Charge switch, left front panel

I use the lazy approach and land near the cargo to attach :)

Extract it anywhere. What is important is to locate the "Moose.lua" file inside this folder. Once inside mission editor, you'll have to have this file executed through a trigger and point the trigger to this location. The Mission Editor will take the file and embed a copy of it into the mission file, so its original location doesn't matter

Nope, that's a 1/3 (33%) chance there :) if math.random(1,2) >1 would give 50%

Holy necro!! :D

You'll find charts on Kurfurst's page, I believe : http://www.kurfurst.org/#engines Economy settings are actually 1.15ata for 2000rpm, normal cruise 1.35ata at 2400rpm, combat & climbing 1.45 ata at 2600rpm and emergency is 1.8ata at 2800rpm with mw50 EDIT : actual chart : http://www.kurfurst.org/Engine/DB60x/DB605_datasheets_DB.html , at bottom

Probably got it a little. You modified TAKS object to include a STATEMACHINE_TASK (derived from STATEMACHINE_CONTROLLABLE, so includes all the functions you listed in the second example for FSM control) to control the state of the task. I've been having a tough time getting a sure definition of "Controllable" in Moose, since I've not seen a definition of a "Controllable" in DCS environment, only "Controller", which refers to AI entity, and Moose doesn't seem to refer to Controllable as AIs only. All this definitely looks like the generic implementation needed for having various tasks handled in a mission. Really looks like what I needed :)

I got most of it, I guess, just missing how to catch or trigger events Or simply how initial fsm state is declared

FC , I'll need several hours to get into what you just wrote, but that's potentially hours saved, if that's what I imagine :)

It works, but the safest way is probably using INS and that would be what is used IRL, wouldn't it?

Well, if you have a lase on target, it means that you have a FAC that should be able to provide you with everything needed to set up an INS attack, in theory. In practice in game, if said lase is AI, that's another story :)