MIssion Scripting Tools (Mist)- enhancing mission scripting Lua

So maybe it is something with time counter because command mist.respawnGroup('Spawnable', 10) did not work but mist.respawnGroup('Spawnable', true) is ok. Can you check if does it work for you, I mean time, mist.respawnGroup('xxx', 10)

And the documentation was missing a variable. There is an optional variable that defines whether or not the task data is retrieved.

 

Fixed the documentation.

You save my day!!!

An easy one.

I am doing a table with mist. Makunittable with units SAM, like {'[sAM] '} but i need to use only radar sam units.

Anyone knows the how?

I tryed to filter the results with unit:hasSensors(Unit. Sensor. RADAR)... Unsuccesfully.

Any help?

An easy one.

 

I am doing a table with mist. Makunittable with units SAM, like {'[sAM] '} but i need to use only radar sam units.

 

Anyone knows the how?

 

I tryed to filter the results with unit:hasSensors(Unit. Sensor. RADAR)... Unsuccesfully.

 

Any help?

I'm attaching a file that produce a table that log groups, not units, but you might get what you need from this code.

the key for you is this line, I believe:

if unit_Table:hasAttribute("EWR") or unit_Table:hasAttribute("AWACS") or unit_Table:hasAttribute("SAM SR") or unit_Table:hasAttribute("SAM TR") then

PS: "unit_Table" isn't a table, is the result of Unit.getByName func.

samlog.lua

I'm attaching a file that produce a table that log groups, not units, but you might get what you need from this code.

the key for you is this line, I believe:

 

if unit_Table:hasAttribute("EWR") or unit_Table:hasAttribute("AWACS") or unit_Table:hasAttribute("SAM SR") or unit_Table:hasAttribute("SAM TR") then

 

PS: "unit_Table" isn't a table, is the result of Unit.getByName func.

Thanks, it might work. Does it work for groups? It will make my life easier!

Thanks, it might work. Does it work for groups? It will make my life easier!

It produces (on my side) a table that log this info for every group:

1. If some unit has a radar, the max radar range;

2. If some unit has weapons (like sam missile), the weapon range & ceiling;

3. The group position intended as unit #1 position

4. If the group is "movable" or non (i.e. SA-8 vs SA-3)

You might need small modification to get it work by your side, but you can.

PS:

I believe it's so similar to what you need cause we both are writing a simplified IADS code... I need it for the next DAWS release.

PS2:

This should work at mission start only, cause It doesn't check if the units are alive. Therefore, I will send you the final code (launchable when you need to update the table) as soon it is done.

It produces (on my side) a table that log this info for every group:

 

1. If some unit has a radar, the max radar range;

2. If some unit has weapons (like sam missile), the weapon range & ceiling;

3. The group position intended as unit #1 position

4. If the group is "movable" or non (i.e. SA-8 vs SA-3)

 

You might need small modification to get it work by your side, but you can.

 

PS:

I believe it's so similar to what you need cause we both are writing a simplified IADS code... I need it for the next DAWS release.

 

PS2:

This should work at mission start only, cause It doesn't check if the units are alive. Therefore, I will send you the final code (launchable when you need to update the table) as soon it is done.

I am just doing a simple Radar Jamming... By switching off some sams but I am having problems with things, that I dont really understand why with getByName things and the stuff.

Can't understand last sentence, can you repeat?

Sorry.

I mean... I dont know why the function i am doing doesnt work... Lol. The function obtain a group. And I used it to get locations etc. And if i put...

Sam = Group:getname(group) it works...

But if i do

unitleader = Group. getByName(Sam) :getUnit(1):getName() it doesnt work... What i am doing wrong?

Sorry.

 

I mean... I dont know why the function i am doing doesnt work... Lol. The function obtain a group. And I used it to get locations etc. And if i put...

 

Sam = Group:getname(group) it works...

But if i do

 

unitleader = Group. getByName(Sam) :getUnit(1):getName() it doesnt work... What i am doing wrong?

Why don't you do

group:getUnit(1):getName() ?

Anyway don't know, I think you removed the space between (Sam) and :getUnit. Don't know...

Why don't you do

group:getUnit(1):getName() ?

 

Anyway don't know, I think you removed the space between (Sam) and :getUnit. Don't know...

Thanks, problem solved.

My probblem is, that i am learing programming for the first time and i dont know when should i call getByName()... I do trial and error... Hahahh any suggestion or lead?.

I'm learning too that way :)

I'm not that good (you can see that looking into DAWS code), but if you need try to ask what you want to get, and I'll try to answer (better via PM to do not spam MIST thread)

Thanks, but I finally got it!! The EW jammer is functional now... pretty funny!

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

Hoggit Documentation is down?

I get a 502 bad gateway error.

Hope not!

Oh no.... :'(

Its back.

Its back.

That is great! :thumbup:

Thx my friend! :smilewink:

MIST broken in 2.0.4.59188? Just updated and nothing is working, (Mist scripts that is)

Sierra

Works fine for me. Is it an old or new mission? Try deleting and recreating the trigger to load it? Checked DCS.log for scripting error messages?

MIST is working... the GCI CAP script is not functioning. Old mission but I deleted Mist, GCI, range and missile scripts and readied each. I then went through and rebuilt each component of the script as far as individual units etc.

Same script works in 1.5. I'll mess with it more tomorrow.

Sierra

Mist First Post

Hello Everyone;

In the first post is that the lastest version of MIST.v1_1.zip??? :music_whistling:

Invisibull made the same comment that GCICAP has stopped working on NTTR. I haven't got time to follow up on it at the moment due to work stuff but the obvious change is the additional air bases. A lot of stuff hangs on the script getting the details of airbases into a table so possibly something is going wrong there. Perhaps the returned values from coalition.getAirbases are different somehow and the script can't deal with it??? That's just a guess anyway. Invisibull was PMing lukrop so perhaps he'll look at it.

Hello Everyone;

 

In the first post is that the lastest version of MIST.v1_1.zip??? :music_whistling:

Speed hasn't been active for a while. I can't edit his posts. Just follow the links regarding mist in my signature and my first post in the thread.

Invisibull made the same comment that GCICAP has stopped working on NTTR. I haven't got time to follow up on it at the moment due to work stuff but the obvious change is the additional air bases. A lot of stuff hangs on the script getting the details of airbases into a table so possibly something is going wrong there. Perhaps the returned values from coalition.getAirbases are different somehow and the script can't deal with it??? That's just a guess anyway. Invisibull was PMing lukrop so perhaps he'll look at it.

Whatever is the issue, if its related to the NTTR and scripting engine let me know. I checked several different scripts on the updated map, but not everything. Any idea what might be breaking it would be helpful.

Really don't have much time as I said, however I squeezed in a quick test a bit before heading off to sleep after a long day at work. Don't know for sure if this is the issue but perhaps someone can try a quick test set up of lukrop's script using the names in the attached pic or set up a little script to dump the airbase names for NTTR. I think that the issue may be that the map names for bases do not match internal names so there is a disconnect between the zone names people enter and the actual airbase names. They need to match for the script to use the base for spawning GCI&CAP groups. The zone designates the base as a GCICAP capable base if you will.

Ideally it would be nice from a scripting viewpoint if the internal names match the map names but if they don't or can't then that's how it is and we'll need to adjust. If it was an easy change however for the dev team to make at this point in time then it would definitely make life easier in the long run. Probably for everyone actually, not just the non ED scripters.

Anyway test results below along with the test mission.

Best wishes,

Stonehouse

testgetairbases.miz