LFCChameleon_Silk

or you could view this video of the ACMI: http://www.twitch.tv/land_force/c/5959892

They need to issue a fix for this mission. I complete 2 times now and I get RTB order without escorting em back (which why do they need an escort back to begin with) you escort them into hostile territory I understand but you shouldn't have to wait for them to return (they destroyed their targets so mission complete) Track file showing the mission was complete success and should not be rated 50. Wouldn't let me upload the ACMI for tacview though. 50 result sortie 3b.trk

local rad_option_8a = "Very Easy" GameSet = missionCommands.addSubMenu("OPFS Settings",nil) DifficultySet = missionCommands.addSubMenu("Set Difficulty", GameSet) missionCommands.addCommandForGroup(Rad_GroupID, rad_option_8a, DifficultySet, Set_Difficuty_VeryEasy, nil) -- 'Very Easy' just snippet from my own script but shows how you can create a menu from F10 radio command with another menu inside that leads to another item that runs a function. this is not working code, simply just showing you what LUA commands would look like, you would need to examine something like CTTS.lua to see how he is creating the radio items for the players and implement something similar and also do some research on the wiki as to what arguments you can pass.

thx for continuing the script Stonehouse, I just ran out of fuel with scripting for the moment especially because of my latest project.

Sorry I probably should have updated this long ago. There were a number of outstanding bugs with OPE (this miz) that were never ironed out, on top of that but the GCI script that was written by SNAFU and modified heavily by Stonehouse wasn't as matured as it is now leading to further issues. I believe 2.16 is probably the most stable of all the versions and its the one I have left up for download. However if you wish for something with some MiG-21 intercepts try this unpublished one that is in alpha status (but playable) https://github.com/chameleonsilk/Operation-Flagship-Scripts/releases/tag/v0.61 its the same motiff as OPE but using brand new script that I've been developing that solves many of the issues with OPE. check the radio menu from whatever airfield you spawn at and create intercept tasks, for MiG-21 i would recommend no higher then easy difficulty... you can set spawn range and difficulty from the OPFS menu in the radio. enjoy, feel free to post any comments you have here about the mission... unfourtanetly I cannot provide any type of support at this time for this mission given its alpha and unpublished status... hopefully within the next few weeks it will have its own thread here and an inital 1.0 release. it actually has more task types the OPE had. anyways getting longwinded here. have fun.

does this not work with a static object? if you want to mirror the ME trigger you should add support for statics to be counted.

yea grimes I'm actually watching that on github, as my mission/script is also on github now, I even referenced older versions of the same function in hopes that something changed to break it but they were all the same. thanks for the quick response.

there was a problem with the MIST function or the SSE has changed. mist.flagFunc.group_alive_less_than_modified = function(vars) local type_tbl = { [{'group', 'groupname', 'gp', 'groupName'}] = 'string', percent = 'number', flag = {'number', 'string'}, stopflag = {'number', 'string', 'nil'}, interval = {'number', 'nil'}, toggle = {'boolean', 'nil'}, } local err, errmsg = mist.utils.typeCheck('mist.flagFunc.group_alive_less_than_modified', type_tbl, vars) assert(err, errmsg) local groupName = vars.groupName or vars.group or vars.gp or vars.Groupname local flag = vars.flag local percent = vars.percent local stopflag = vars.stopflag or -1 local interval = vars.interval or 1 local toggle = vars.toggle or nil if stopflag == -1 or (type(trigger.misc.getUserFlag(stopflag)) == 'number' and trigger.misc.getUserFlag(stopflag) == 0) or (type(trigger.misc.getUserFlag(stopflag)) == 'boolean' and trigger.misc.getUserFlag(stopflag) == false) then if Group.getByName(groupName) then if Group.getByName(groupName):getSize()/Group.getByName(groupName):getInitialSize() < percent/100 then if trigger.misc.getUserFlag(flag) == 0 then trigger.action.setUserFlag(flag, 1) end else if toggle then trigger.action.setUserFlag(flag, 0) end end else if trigger.misc.getUserFlag(flag) == 0 then trigger.action.setUserFlag(flag, 1) end end end if (type(trigger.misc.getUserFlag(stopflag)) == 'number' and trigger.misc.getUserFlag(stopflag) == 0) or (type(trigger.misc.getUserFlag(stopflag)) == 'boolean' and trigger.misc.getUserFlag(stopflag) == false) then mist.scheduleFunction(mist.flagFunc.group_alive_less_than_modified, {{groupName = groupName, flag = flag, stopflag = stopflag, interval = interval, toggle = toggle, percent = percent}}, timer.getTime() + interval) end end this is the modified function by me, hence why its called mist.flagFunc.group_alive_less_than_modified, it instead of true and false sets flag to 0 or 1, I find that easier to work with... this function has the isActive part removed and does work. so anyone trying to make the default function work... if you do please tell me how you did it! but for now I will use my modified version... maybe grimes can comment about this issue (and then give me back my 8 hours last night) I kid of course, MIST library is very helpful. EDIT: awesome glad to see the problem has been found and resolved, but I gotta wonder... am I the only one using these MIST functions surely someone must have had this problem in the past, also a heads up in the wiki you have units = when that is not accepted type, this is also in the documentation for MIST.

00098.132 ERROR SCRIPTING: [string "E:\Users\Gamer\AppData\Local\Temp\DCS\/~mis00001594"]:3196: attempt to call method 'isActive' (a nil value) stack traceback: [C]: in function 'isActive' [string "E:\Users\Gamer\AppData\Local\Temp\DCS\/~mis00001594"]:3196: in function 'group_alive_less_than' [string "E:\Users\Gamer\AppData\Local\Temp\DCS\/~mis00001A54"]:1769: in function <[string "E:\Users\Gamer\AppData\Local\Temp\DCS\/~mis00001A54"]:1608>

checkunits = { groupName = DefensesName, flag = 101, percent = 80, } mist.flagFunc.group_alive_less_than(checkunits)what am I doing wrong? flag 101 never is true, even when i kill the units that are in the string DefensesName I literally spent 8 hours on this last night and tried many different ways and still nothing.

never is with scripting! always something broken to fix up. take your time Stonehouse don't get burnt out.

its one thing to say the GUI is poop but it does allow you to do lots of neat stuff you otherwise couldn't same thing could be said about saiteks programming software... at this point I'm pretty convinced that no matter how it was designed the vast majority wouldn't understand it and then slam it because it involves thinking to do stuff and to learn how to do things. its like saying x program language is bad because you don't know how to make a sprite move across the screen, when you know its possible you just don't know how to do it... so therefore the language is poop. see whats wrong with the logic?

I'm pretty sure that its a DCS related limitation in the SSE and not something that can be scripted around (easily) I remember reading somewhere about this in the past, although I cannot remember where.

can you start adding version number to the MIST filename? I got like 8 mists laying around and its a pain to try and remember which one is the newest one. other then that great work.

lol escorts for clients, what kinda thing are you trying to get at here :lol: well I'm building a script that does kinda the reverse of this, spawns an AI plane that you have to escort to a certain area as a task to complete. take a look at the kutasi intercept script from akp, I've modified it and am gonna keep extending the functionaltiy of his and my scripts, at the moment it spawns things for interceptors to shoot down at random distance from a trigger zone and makes them orbit on CAS tasking... but I cant see it not being to hard to make a function out of it that spawns AI that escorts you or follows you. http://forums.eagle.ru/showpost.php?p=2195394&postcount=8

Modified akp Intercept Script with demo mission Usage: Make sure you load 'mist' first.. usually about 5 seconds after mission start, then a second later load 'akp intercept script.lua', you can edit 'akp intercept script.lua' for your own selection of fighters although this is the list that is in the demo mission that I included. Interceptor_Names = { [1] = 'MiG-21 #1', [2] = 'MiG-23 #1', [3] = 'MiG-29S #1', [4] = 'MiG-29A #1', [5] = 'Su-17 #1', [6] = 'F-16C bl.52d #1', [7] = 'Su-24MR #1', [8] = 'Su-27 #1', [9] = 'Su-25 #1', [10] = 'Su-25T #1', [11] = '2000-5 #1', [12] = 'F-86 #1', [13] = 'MiG-25PD #1', [14] = 'MiG-25RBT #1', [15] = 'MiG-27K #1', [16] = 'F-16A MLU #1', [17] = 'F-16C bl.50 #1', [18] = 'F-4E #1', [19] = 'F-5E #1', }edit it with the group names of the fighters you want to have spawn (see demo mission) then simply place zones down and you can then at anytime during your mission creation you can use the function in a DO SCRIPT trigger: Create_Fighter_Intercept('triggernamehere') please note that capitals are important thats it! Intecept_CSILK.miz mist.lua akp_intercept_script.lua

akp is it ok if i repost an improved version of your script? I been busy modifying it for my own purposes but would like to share the fruits of my labour with you and the rest of the community.

+1 (as option) love the module but lets make it even better.

yea most likely something I've done wrong, will take another look at my mission file and make sure there isn't something I'm doing wrong in there.

thanks for the work akp, a great piece of script that I will include in my own missions to spawn an intercept for the MiG-21s.

http://forums.eagle.ru/showpost.php?p=2178558&postcount=216 the mist and GCI script are in this mission urban posted, as far as I can tell thats the latest stuff.

MiG-21s spawning with no loadout.

updated mission file again, to version 1.20E... the blue awacs was to far out in front of the other planes and thus was a sitting duck.

try setting frequency to 124, and callsign to overlord (shouldn't matter) and then tell him to continuously use radar and make sure hes high altitude and your not low NOE flying in mountains :P and dont try to use EWR as blue faction it doesn't work... sadly enough... bug or feature I dunno but it sucks.

just wanted to say that as far as I know most of the new work was done by Stonehouse so once he gets his PC back to full health he will give you a better idea of whats been added changed. from what I remember: I had added parameters to make first flight start from ground and fix the take off from runway part, added some stuff to control CAP altitudes minimum and maximum that I think Stonehouse had added checking of terrain to as well, Stonehouse also added a 4th airfield spawn, the rest I'm not really sure... I was having some issues running the latest versions but was probably something I was doing wrong. not sure if Stonehouse got around to making it so you can have varied payloads... in my opinion that was the worst part of the script having to change multiple sections to change the plane and payloads which was tedious and error prone. but I think there is a lot of potential for the script...like a ton.