kira_mikamy

the number after / is the number of days. 0 is today, 1 is tomorrow, etc. Almost useless, never need it.

CAZ is the moose capture zone, allow you to set some zome to be dinamically pass trough blue or red control https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Functional.ZoneCaptureCoalition.html

for the future i suggest you to setup the group with only 1 aircraft, when you complete the setup, setting it on client, waypont and what else, add the others and they are an exact copy of the first one

ive use to make mission on my pc and then move on the server that had different path and reload mission trigger always working with no problem, but you have another one folder inside missions one, i think nothing change using only the missions folder in the server, but you have to try both options

Hi! cannot help about the radio, but, about the group to stop call the waypoint, you need to set an advanced waypoint actions. you can found that menu when selecting the group to mute and clicking in the bottom right side under the waypoint settings in the "advanced (waypoints actions)" button, that pop up a little window and you need to press "ADD" to add one actions, it will ad a "no task" one but another window pop up on left and you need to choose "set option" for first menu, then "No report waypoint pass" in the second menu, then ckeck the box, need to put that in the waypoint 0 hope that can help you

in my persistent server i use DSMC script for state saving, also some moose module like a2a dispatcher, caz, are pretty ready to go for persistent mission. others like ctld or skynet need personalization to aquire persistence working good

put thoose aircraft on "hidden" in the mission editor in the right checkbox when selecting the group, so you cant see they in f10 map.

should be intersting to have the possibility to manualy set the engage distance without script. Anyway, a workaround to do that at the moment is using trigger zone and group ai on\off. part of coalition out of zone -> group ai off, so they dont shoot. when part of colation inside zone -> group ai on, so they start to shot only if theres plane\ground or heli in the zone both in switched condition so the group can switch from ai on\off for the entire match.

cannot imagine how to manage my group missions and training server without moose, also a dynamic server. Thank you for the effort

thank you again. i didnt know why the same code work with an airplane but dont work with ground unit, make me sick. When im coming at pc i will upload here a test mission with a red ground being shooted by a blue tank and the red one with the mist respawn on it, but didnt work, may i am crazy and blind to dont see some evidence mistake. i work around the problem using moose with initlimit but require a little more effort. PS, i always activate the mist respawn not trough a lua file but with a simple "do script" using the text boxt, first the main mist.lua after 1 second and then the little respawn script after 2 second, tryed both once and repetitive, it always worked like that but who know, may you use a single lua file to load the respawn script?

thank you so much! i will try if work as you suggest, i have to use it with ground vehicle but not the static one.

Hello everybody! I have some trouble to understanding why in my server a mist function stop to work, apparently about a week ago, didnt know the exact day, just noticed it now douring some test cause some players report me the issue. I have a simple utilization for mist, a simple respawn after death for some static unit we use for aiming training. of course the Mist (last version available on Github) have a trigger to load at mission start. then after 2 second a "do script" file with the follow: --- if not Group.getByName('groupname') then mist.respawnGroup('groupname', true) end -- thats all, always work from months but stopped, ive try some different options as indicated in Hoggit wiki about it, but doesnt work. https://wiki.hoggitworld.com/view/MIST_respawnGroup thanks in advice for any help, blueskies my friends!

i have problem with TADS when i open it in the pilot seat i loose half of my fps and my gpu loose 15\20% of usage, never see nothing like it before. if i turn off the vsync the fps dont drop to 30 but stop at 40, theres something wrong in the way the tads image has render, like the system have to render 2 time all the scenery you have in front, its terrible weird and result in an unplayable module without a low end pc, i says unplayable because the performance are the same with every grapchis setting, i try to put everything low and lower the resolution witthout no difference, i have no problem of fps play in high with f18 or a10c and their camera system to acquire the targhet. i think we all know is an early access but should be really glad know something has moving to resolve this in the future.

come in the forum to open a post about it, but i see the problem is already noticed. In my case, i play with vsync on, cause putting it off cause me lot of tearing, anyway, i got solid 60fps in the apache, but when i open the tads view in the pilot seat (or also in the copilot seat in single player) my refresh rate got halved, from 60 to 30. heres the pic, with the rivatuner statistic diffrence between tads on\off