MIssion Scripting Tools (Mist)- enhancing mission scripting Lua

Wrong thread, sorry.

Question:

I have 3 different SAM groups, selected for late activation in the ME.

If I want to randomly select any 1 group to spawn at a random time, by setting a time limit range, then what will be the lua code?

Can somebody please help..... :helpsmilie:

Rephrasing the Question:

How to spawn a randomly selected group from a given group names, that spawns at a particular trigger location at a random time? :helpsmilie:

Hope I get the answer this time.....:(

Anybody care to answer my questions in the previous posts?

:helpsmilie:

Hi,

take a look here:

http://wiki.hoggit.us/view/DCS_editor_Randomization

Apolloace, assuming that you pre-defined the groups in the editor and set them all to delayed start, as well as defined the zone:

NOTE: MiST makes this stuff super easy

1) Define a list of group names.

local groupNames = {"Group1", "Group2", "Group3"}

2) Choose a random group name.

local groupName = groupNames[mist.random(#groupNames)]

3) Figure out how many seconds from now that you want it to respawn.

local randomTime = timer.getTime() + mist.random(120) // up to 120 seconds in the future

4) You will need to have something that checks the current time to trigger the spawn. A simple approach would be to create a new scheduled function that fires immediately and checks each second thereafter.

local timerNum = mist.scheduleFunction(checkTime, {groupName, randomTime}, timer.getTime(), 1)

5) Create the new function that checks the current time against the desired spawn time.

function checkTime(obj)
if timer.getTime() >= obj.randomTime then
 mist.respawnInZone(obj.groupName, "myZone")
end
end

This should work, although it is from memory and not verified. There is some extra code that could be written to stop the timer. Please let me know if you have issues with it.

Hi,

take a look here:

 

http://wiki.hoggit.us/view/DCS_editor_Randomization

I am already aware of that. Anyway thanks for your reply. :)

Apolloace, assuming that you pre-defined the groups in the editor and set them all to delayed start, as well as defined the zone:

 

NOTE: MiST makes this stuff super easy

...................................................................

.............................................................................

 

This should work, although it is from memory and not verified. There is some extra code that could be written to stop the timer. Please let me know if you have issues with it.

Thanks for your reply with the suggested codes.

I will check this out and let you know. :)

 

Originally Posted by Chump

Apolloace, assuming that you pre-defined the groups in the editor and set them all to delayed start, as well as defined the zone:

 

NOTE: MiST makes this stuff super easy

.................................................. .................

.................................................. ...........................

 

This should work, although it is from memory and not verified. There is some extra code that could be written to stop the timer. Please let me know if you have issues with it.

 

Thanks for your reply with the suggested codes.

 

I will check this out and let you know. :)

 

I have checked your codes. It works! :thumbup:

Just had to tweak the randomTime & checkTime functions a bit. Otherwise, every thing is fine. :)

Again thanks a lot for the help!!

Glad you got it working.

So my conclusion, given if i remove DAWS and use MIST run at mission time, is that its just MIST being called early that's the issue, since the code is all the same.

 

Now...I know you said Chromium, that you tested it and it was working on .73, so if nothing else has changed, its the DCS version that does something different? I'm not going to revert a version to test, as much as I love my QA job here at Eagle Dynamics :) :)

As from DAWS thread, I modified the code so that now integrated MIST version in DAWS is loaded at very first second of the mission, that should prevent the issue (it does in the attached test mission with last uploaded DAWS version).

@Grimes: I know that this is something that don't belongs to you, but I can't do nothing from DAWS to prevent the double-loading of mist caused by mission designer loading mist code in a trigger (after DAWS). I don't know a way to prevent this in DAWS code. I'm asking you, if you can, to add that "mist is loaded" check in the MIST code, so that if a mist is already loaded it won't load itself again. Do you think it's possibile?

DAWS_SM_AE_test3_teleport.miz

that worked. will look into juggling start times more

Hi all

I look for a script

plane group fires = Flag1 on

The Plane Group is Bf-109K-4

i try this, but it will not work:

local Plane = UNIT:FindByName( "Plane" )

Plane:HandleEvent( EVENTS.Shot )

---

-- @param Wrapper.Unit#UNIT self

-- @param Core.Event#EVENTDATA EventData

function Plane:OnEventShot(EventData)

if EventData.WeaponName == "weapons.MG_131" then

MESSAGE:New("Plane shot Gun",15,"Alert!"):ToAll()

local Task = EventData.IniGroup:TaskOrbitCircle( 5000, 450 )

EventData.IniGroup:pushTask( Task, 30 )

end

end

The shot event is for all non rapid fire shell based weapons. You need to use the event shooting start. This event does not return any weapon data, only the initiator, but it will occur anytime a rapid fire gun is fired. You would need to either know the aircraft type and its associated MG ammo type or use world.searchObjects in the immediate area around the initiator aircraft to find the shell and get the name type.

So take an M1 Abrams for example. The main cannon would produce a "SHOT" event with HE and AP shells. The coaxial and commander turret will create "SHOOTING START" and "SHOOTING STOP" events. In the case of aircraft that have more than one gun that can fire at a time, each one will create a shooting start/stop events.

By the way it is not ideal to post questions related to a specific scripting library in a different scripting thread. In this case posting moose code in the mist thread. So while I will answer questions specifically related to the scripting engine in general here, I can't really help you with the moose side of things.

Thx for your help

To save me from reading through 127 pages and is a daft question but does MIST need to be installed on the server or can I just install it to my local laptop create the mission and then export to a dedicated server? Apologies for my noobishness.

It is a mission script. You add it as part of a trigger, usually Once> Time Less than 10> Do Script File(mist.lua) works quite well. So by adding to execute as part of a trigger it will automatically embed the mist file into the mission file. Once the trigger runs in the mission all of the mist functions and tables are globally accessible. Its up to you to make a script that uses it.

At one point it looks like mist.respawnGroup() and related functions would return the new group name as a string, now it seems to return the group table. How can I get the new group name from this table?

It should be as simple as:

local newGroup = mist.respawnGroup([i]params[/i])
local newGroupName = newGroup.name

or

local newGroupName = mist.respawnGroup([i]params[/i]).name

http://wiki.hoggit.us/view/RespawnGroup

mist.respawnGroup('groupName', 120)

Why does my group reborn at once?

You are going to have to be more descriptive with your question. I don't understand what exactly you are asking.

You are going to have to be more descriptive with your question. I don't understand what exactly you are asking.

I have group 'g1' and uses this script:

if not Group.getByName('g1') then
 mist.respawnGroup('g1', 100)
end

Respawn after 100s.

In DCS 1.5 'g1' respawn at once.

test.miz

@Yappo, I think you are misunderstanding the parameters.

string mist.respawnGroup(string groupName, boolean/[b]number[/b] task/[b]taskDelay[/b])

The group will always respawn immediately. If the taskDelay parameter is present, it will re-assign their original route after the specified number of seconds.

@Yappo, I think you are misunderstanding the parameters.

string mist.respawnGroup(string groupName, boolean/[b]number[/b] task/[b]taskDelay[/b])

The group will always respawn immediately. If the taskDelay parameter is present, it will re-assign their original route after the specified number of seconds.

I understood. Thanks.

Is MIST working in 2.1 ATM?

Are respawnInZone and teleportInZone working for player groups? I can respawn the player using the basic respawnGroup, but when I try to use respawnInZone I get "Err: Can't execute trigger. Err: "mist.respawnInZone('PlayerGroup', 'SpawnZone', false)"

Substituting a non-player group works fine with no other changes to the syntax