Whisper

Try manual prop pitch and cruise at 1.15 ATA for 2000RPM, or 1.35 ATA for 2400 RPM. Perhaps placebo but to me it eases up on the necessary trim

Maybe it's not an error but the actual height of the INS system inside the airframe, counting the height of the aircraft? :) I don't know, I don't know if height correction is part of alignment procedure

Well, I may be an exception, but like Little D, I find the 109 easier to take off and land than the 190. Not so for taxi, though, the 109 is complicated on ground :)

I don't get that last part WP 00 is your current postion, why would you want to update it? During align procedure? For your other Qs, I'm on 1.55 unfortunately, can't tell for 2.04

Your selected waypoint must be the IP one, with offset configured. Without offset on the currently active waypoint, the IP option does not appear.

See here for technicalities : https://forums.eagle.ru/showthread.php?t=176514 They removed the disembark task and the embark task, while existing, has no effect. CTLD is a solution.

Ditto. I verified in my mission file, the task "disembarkFromTransport" is still there in the text file, but disappeared in the editor and cannot be selected anymore..... This : ["tasks"] = { [1] = { ["number"] = 1, ["auto"] = false, ["id"] = "DisembarkFromTransport", ["enabled"] = true, ["params"] = { ["y"] = 462509.42857142, ["x"] = -164367.42857143, ["zoneRadius"] = 200, }, -- end of ["params"] }, -- end of [1] }, -- end of ["tasks"]is not interpreted by the Mission Editor anymore...

In an ideal world, the Stable version should be updated to the last bugfree Beta version, 1 week later to give time for "bugfree" state confirmation, without a single change done to it, not a single addition, changes and addition which could be incorporated to OB the same day the Stable is updated to previous OB. Ie, OB vers 1.5.59994 is seen as being bugfree enough for Stable, 1 week after its release. Stable can be upgraded then to 1.5.59994, the same day new things are introduced into OB 1.5.59996. All these changes will be incorporated into Stable X weeks later when introduced bugs are squashed. My issue really comes when things are introduced into Stable when they have not been beta tested, while we have a Beta version just for that! (and I'm a pure Beta user, I never launch stable). Releasing a patch to Stable is kind of a "no return" operation, when it's done right now, some people (non Nevada owners) are forced to this version without alternative, so it really must be a Stable version. And since we have OB for development, I don't really see how this would slow down development.

That's the point. I'm not sure the S_EVENT_DEAD even has a "initiator" value. So you're perhaps setting init to an unexisting value. I'd suggest to move local tgt = event.target local init = event.initiatorinto the specific S_EVENT_HIT part : function groupIsDead(groupName) if (Group.getByName(groupName) and Group.getByName(groupName):isExist() == false) or (Group.getByName(groupName) and #Group.getByName(groupName):getUnits() < 1) or not Group.getByName(groupName) then return true end return false end CollHandler = {} function CollHandler:onEvent(event) if event.id == world.event.S_EVENT_HIT then local tgt = event.target local init = event.initiator if tgt then if tgt:getCountry()==16 and init:getCoalition()==2 then --Georgia trigger.action.outText("Don't shoot at civilians!", 10, true) end end elseif event.id == world.event.S_EVENT_DEAD then --if a unit dies, check if the group is still alive local t = {'CIV_Traffic1', 'CIV_Traffic2', 'CIV_Traffic3', 'CIV_Traffic4'} --Civilian vehicles (one per group) to monitor for k, v in pairs(t) do -- iterate through the groups in table t if groupIsDead(k) == true then mist.respawnGroup(k, true) end end end end world.addEventHandler(CollHandler)

No doc ag hand, but is there both target and initiator for a dead event?

Currently my startup checklist includes the realignment of GMK1 to geographic north and it works everytime. 1) proceed with startup 2) get your current geographic heading (F2 or F10 map view) 3) switch to GPK mode, assert your heading on UGR-4UK is actually not your geographic heading 4) click on SK switch until heading is aligned with your geographic heading 5) go on your merry way, you'll have accurate heading on your UGR-4UK and your Doppler Nav.

I works now.

Look, they make a new entry for each version, this time they didn't... Conclusion, it's the same version as last week, easy :) It's actually not the case, so all good, got my answers. You understand that potentially removing a module for users is triggering reactions, right?

They pointed to the SAME update status page, that meant to me that the version was the same as current beta, which meant that they were killing Gazelle module for non Nevada owners. Since update is actually not out yet, it's better to point out a flaw BEFORE it's actually live, isn't it?

If gazelle is not amongst the fixed things, this is a royal screwup

Gazelle not working, Mirage IFF bugs and many others => let's get that out in Stable!! Why?

Errr ......

Judging by the reaction to this thread, it's better than not having it :) So yes, it works.

Belsimtek allowed it in Mi8, there's a little bit more render to be done, but it works

I don't think he is :) What he means :

DIRAV (Nose Wheel Steering) button in flight will initiate an IFF interrogation. Friendly targets on VTB will have a diamond symbol added in search/PID mode, and friendly locked target will appear with 2 vertical lines in PIC mode.

I'm afraid the "FBW off" myth will never die :(

That would be bad news for Gazelle owners

You mean this ? :

Of course!