[supercarrier yellow shirts will not guide into catapults]

We also have this now every SC launch since the patch. Inefficient ground crew! 

[MIssion Scripting Tools (Mist)- enhancing mission scripting Lua]

Ah I see :) shit happens, thanks for the quick fix!

[MIssion Scripting Tools (Mist)- enhancing mission scripting Lua]

I'm probably missing something basic but I can't get 4.5.95 to load. "attempt to index global 'mist'" no matter when I load. What am I missing?

Simple test included (should display unit heading 2 sec after start) and works with 4.4.90.

TEST.miz

[MIssion Scripting Tools (Mist)- enhancing mission scripting Lua]

Can't reproduce on my end. Can you attach a miz that generates the error? Would be extremely helpful.

 

Found it, somehow adding a 'invisible farp' makes the function stop working. I have no idea how.. I've attached a cleaned version of my mission.

Start, choose random slot, within a couple of seconds the script runs as a AI enters the zone and I only get the "TRIGGER" text.

Remove the 'Invisible farp' (near Kutaisi) and re-run, now it should work.

?

TEST.miz

[MIssion Scripting Tools (Mist)- enhancing mission scripting Lua]

https://wiki.hoggitworld.com/view/DCS_func_isActive

I'm getting the error ':2568: attempt to call method 'isActive' (a nil value)'

Something broke after latest patch or two (incl hotfix).

Used by: https://wiki.hoggitworld.com/view/MIST_getUnitsInZones

Just me or..? Tried a re-save and to isolate the code.. Alternatives?

[[BUG] Countermeasure Rearm in MP]

Still an issue for us, although we're on 2.5.5 because of all the other bugs so. Are you guys in 2.5.6 and are still having this issue?

[[DCS BUG] Thank you Heatblur -- Radio Problems in Multiplayer - Bug or stupid? :-)]

I posted the queation on reddit as well and got the following answer from Cobra:

 

"This was an issue pre-launch that we worked with ED to fix (it's in the core engine). It was corrected, but obviously there still seem to be issues :(

 

We'll prod this issue a bit more and fix it."

 

So we will have to wait for a fix obviously.

 

Is this still a thing? I can't get this to work, same procedure with me as server - works every time.

Sounds like a multicrew "not counting the "other guy" as a player/client"-problem..

[MOOSE - Mission Object Oriented Scripting Framework]

I’m struggling with the same issue. It would be convenient if spawned aircraft could be made to disappear on landing or parking by a command :VanishOnLand() or :VanishOnEngineShutdown()

 

I use the landing event as follows:

 

_USAFAGGRESSORS = 1
_USA = 2

air1:HandleEvent(EVENTS.Land)
function air1:OnEventLand(EventData)
   if EventData.IniUnit:GetCoalition() == _USAFAGGRESSORS then
       Unit.destroy(EventData.IniDCSUnit)
       trigger.action.outText("Enemy landed", 10)
   end
end

air2:HandleEvent(EVENTS.Land)
function air2:OnEventLand(EventData)
   if EventData.IniUnit:GetCoalition() == _USAFAGGRESSORS then
       Unit.destroy(EventData.IniDCSUnit)
       trigger.action.outText("Enemy landed", 10)
   end
end

 

If the coalition in this case is red (0 = neutral, 1 = red, 2 = blue), the unit will despawn on landing keeping it clear :) 'air1' is the globally saved spawned group.

[MOOSE - Mission Object Oriented Scripting Framework]

Save the spawned group in a global variable, then the Destroy() works as it knows it's "name". Should work!

i.e.

Group1 = SPAWN:New( "GRP1-1" ):InitKeepUnitNames():Spawn()
Group1:Destroy()

[MOOSE - Mission Object Oriented Scripting Framework]

It seems to be working fine on my end.

 

Thanks for the check guys, it was something as dumb as not using the latest version of Moose. Apparently my Moose.lua from 2018-04-24 had a problem with that function..

 

As you stated, the InitLimit(1,1) is valid... But, it's unnecessary.

 

I find it useful for my training missions/spawns using switched conditions. This way there is no chance of another AI plane to spawn accidentally as I want to be able to use the trigger zone unlimited times.

 

Sharing this small example anyways, the problem was setting the skill through the f10 menu :)

Not sure if it's actually makes a difference yet though, too useless in the tomcat to be sure yet ;)

 

Is there a way to get the skill from a Moose-spawned unit or group? AI.Skill?

F-14_dogfight.miz

[MOOSE - Mission Object Oriented Scripting Framework]

Is InitSkill(String) not functional in Moose? https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Spawn.html##(SPAWN).InitSkill

 

TRMiG23 = SPAWN:New("AIMiG23"):InitLimit(1,1):InitSkill("Average")

gives

attempt to call method 'InitSkill' (a nil value)

 

Hoping it's syntax.. :|

[Need help with entering waypoints IN cockpit please?]

The N/E button should be pressed before coordinates, might be that?

Otherwise I don't think the alignment is OK if it's that far away :D (try with HOT plane?)

We use no conversion between F10 and F-14 :thumbs_up:

[F-18 pitches steeply and cannot reset trim]

Happens to me aswell - only after T/O and I fix it by going through FLAPS settings (full -> half -> auto) quickly and it's gone.

[ew]

( i hear it doesnt work at mo but this is ea so hears hoping!)

 

DCS 2.5.2.18307 Update 3

Added absolute axis for TDC.

 

timing :thumbup:

[[REPORTED]Hornet Hot Rearm question]

I never use easy comm, is that necessary with the hornet? Id like to know if I must change it.

 

No just open the canopy and it will work without easy communication.

Use the communications key and then the normal ground crew->rearm/refuel option.

(The communications menu key works on the ground, not in the air.)

 

^ :thumbup:

 

Did also work by talking to for example the carrier through COM1/2, but that was A/A weapons ofc since the stores page is "bugged".

[DCS 2.5.1 Bf 109 Kurfürst - can't start]

As a workaround - there's a command in control options for "engaging" the ground crew starter guy outside of radio comms menu. Can't assign it to keyboard for some reason, but any button on joystick will do. Tested yesterday - works OK.

 

oh! Will assign, thx. That sounds like a good solution in the future also :thumbup:

[DCS 2.5.1 Bf 109 Kurfürst - can't start]

Ground crew won't apply starter when chosen through radio menu and so I can't get it running. Tested on 2 clients and in SP & MP.

This happened after we updated to 2.5.1 yesterday.

It it just us somehow?

 

Oh and the ground crew is there, they reply on other tasks.

[Difference in AI behavior in SP vs MP]

solved I think...

 

It seems like in MP you have to give the AI tasks after spawn, using lua. Now they are killing me just fine :) Just need to figure out all task options used in the tables.

 

I.e.

mist.respawnInZone('rBanditGrp1', 'rSpawnZone1', true)

local con = Group.getByName('rBanditGrp1'):getController()

con:setOption(0, 0)

[Difference in AI behavior in SP vs MP]

Hi,

 

Could someone maybe explain why the AI behaves very different in 1.5 SP vs 1.5 MP?

Attached is the mission I'm trying to fix.

 

Mission explained:

Unlimited training, every trigger zone will trigger a group of enemy fighters (MiST random spawn) IF all enemies are dead within the conflict zone.

I wrote a kill script for the enemy groups as they apparently must have been alive for MiST to actually spawn them.

There is also some random air traffic in the area.

 

The problem:

In SP the AI will attack me as soon as they spawn, just as I wanted it.

Launched as MP server, they neither attack nor defend themselves (barely)..

 

I have tried to make them more aggressive by removing the CAP task and replacing it with my own set of options, as seen in the .miz.

Unlimited_training.miz