kira_mikamy

yeah the attribute are manager very wild. null never understand what this means ["IFV"] = {"Infantry carriers","Armored vehicles","Armed vehicles","AntiAir Armed Vehicles","LightArmoredUnits",}, ["APC"] = {"Infantry carriers","Armored vehicles","Armed vehicles","AntiAir Armed Vehicles","LightArmoredUnits",},

mumbling maybe with moose have to try that https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Wrapper.Scenery.html##(SCENERY).FindByName

i have never do that, didnt explore the various command id but i guess if you have to press a button for doing that, that thread can probably be usefull

i dont believe so cause theres no event related to the missile lock itself, as far as i know. the only related event you can use is On Event Shot, i imagine server doesnt need to know that lock event so its probably client side coded inside the plane itself, the only event the server manage is the shot one. source for events managed by sim: https://wiki.hoggitworld.com/view/Category:Events

would be annoying setting up trough mission editor. you can look at moose class autfrag that do that very well https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Ops.Auftrag.html##(AUFTRAG).NewCAP if you cannot script you had to deal with a bunch of flag and ai tasking. when enemy coalition is in zone (flag1) the ai tasking (condition: flag1 on) should be a repetitive loop between two identical wp1 and 2 separate by some nm, both with search then engane in zone when no enemy is in zone (flag1 off) the ai task should be hold\orbit on a wp and may in weapon hold to avoid they to follow untill the end of the map. all trigger and flag had to be settet as switched condition, so they can looping everytime planes eneter the trigger zone and let the flag change.

ive see youre using "rookie" AI as skill, have you tried with Ace or almost Veteran? we see lot of difference with AI behaviour changing that more than trick the task itself, that looks good. the only thing i "know" for experience is the "search then engage" task, is a 1 time call, the group need to be in a reasonable finding range when the trigger start otherwise they didnt found nothing and skip the task. we usually make a bunch of waypoint really near each other with the same identical task so if they miss at the first waypoint they try again and again. as example: waypoint 3 -> search then engage group waypoint 4 -> return to waypoint 3

we have a server with around 1000+ units in it, douring years of testing we found that the biggest and demanding resource for the server are moving units. especially if they move offroad, but also on road have similar impact. it is better to have a single moving group formed by 10 units, than 2 group formed by 5. another big impact on perfomance are the sam shorad , if there multiple sam shorad (or sam tracking\search radar), each radar need to be managed by server. also i think manpad act as well. this is un-scientific and just based on our experience with large server! we have 1000+ units and just 5\6 movable convoy in the entire map as maximum. and usually not more than a cuople of shorad every 20\30nm

i wont use default trigger mission by a while, prefearing script, but if i remember correctly the ON SHOT eventy means every shot in every place so, if you enter the zone with Blu1 and "blu4" somewhere in the map shot, it will trigger the event and red1 break away, because blu1 has triggered the FLAG 10 and blue4 triggered the shot event. theres a condition called UNITS HITS SUCCEFUL and you can use that to trigger the flag10 when blue1 hit the target, removing the on shot event, but if you dont hit him nothing happen. i think without lua can be tricky, can be simple manage that with moose EVENT:OnEventShot(EventData) using event.initiator to make sure that blu1 is the initiator, then UNIT.IsInZone() using the initiator as unit to check if in the moving zone so at this point the trigger only set the flag when blu 1 is in the moving zone and blu1 has shoot something. if blu4 shot but isnt in the moving zone nothing happen. also about the animation i think without lua scripting theres no way to change the argument. but, i never have myself try that so i cannot say

save feature is cool but is waaaay far for be accomotated in a 24\h persistent server, at the moment, as i read is more dedicated to a single player that want to fly a simple home made mission, or maybe a co-op one with a bunch of friends. tha fact airplane in flight stay in flight after the save its a big NO for me, or i had to make a script to remove it at the start of the mission every time. some plane can only spawn douring certains conditions, if playerbase in the server is enough etc. the time saving also is cool but is better to give an option to create the next mission in a selected time interval as start, like already DSMC do: new mission will be generated the next day , from 6 am to 15 pm (for example) in that way, a 24\24 server is better for the player base, otherwise if people log in every time at the same real life hours, will be the same hours every day in the server too, if my mission in mission editor start at 10AM and i start the server at 10AM also in real lifee, people who play at night wil aways flight at night. The server i administrate have a restart every 6 hours, that means 4 at days and that means in one days will be 4 days in the mission editor mission file, each restart have the day shifted by one more and the started time casually setted from 6 am to 15pm, that offer the player base to enter the server and always found a different time condition. That also simulate very weel the season change, every one real like week it will be a month in the dynaimc mission, and weather accomodate itself to fit the actual month. expect reain on spring and snow on winter also the weather update every restart with a new preset, this is default by DSMC. it will be difficult to accomodate persistent 24\24 server. but it will be funny for solo player or little co-op enjoyer trough local server. Anyway, im really happy ED start to move forward to that feature. Of course this is just a post tha explain some light behavious, i can judge nothing about that. I wish you a good work about it!

add a flag to the trigger condition that add the menu to activate the sam: ex Flag X = false (all flag are false at dcs start if not declared true by mission editor) then , when you active the sam for the first time you declare the sam spawn and: Flag X = true untill Flag X dont return on false status, the menu doesnt reappear.

i also make mission, my rules is: be the gamemaster in my mission be the pilot in other friends\community mission

glad to help hope it works for you!

not sure about but may you need to use Call_Me() without space or remove the "local" or maybe both

" local BFM_F5 = missionCommands.addCommand ("BFM F5", Menu_A2A) " thers no command in that string, it should be ("BFM F5", Menu_A2A, COMMAND_FUNC) you are try to add a command without set wich comand it have to call. function COMMAND_FUNC() ..your script here.. end

ive test it and it remove the submenus when triggered, probably there something incorrect in some group naming or so