dark_wood

"What does this do in the mission editor." - what can do, acrobatics, logic. Do a test mission and play with the settings.

if you set it to 50%, that will be the probability that the unit spawn in game. 100% (default) - the unit will appear in game 0% - the unit will not appear in game values between - unit will appear or not, depending on that percent this is very usefull when you play same mission again and again, it will randomize action. Put a SAM with 30% and start mission several times - you will see that it spawns only sometimes.

Thanks man, made my day :)

Wierd, just few days ago i did a mission with all three tanks and checked the central one, it was fine. I remember because when central one emptied i have jettison it.

hmmm, you can do a check after some time (estimating how long HARM can fly - in my example 60 seconds, change at will): --check if unit inside zone, SAM ON REPETITIVE ACTION > UNIT INSIDE ZONE > UNIT AI ON --check HARM inside zone, SAM OFF REPETITIVE ACTION > HARM in ZONE > UNIT AI OFF, Flag 1 true --60 seconds from HARM in zone, check again if unit is inside zone (HARM should be gone by now), if yes then SAM ON (then reset flag 1 to false) REPETITIVE ACTION > time since flag 1 - 60 seconds AND UNIT INSIDE ZONE > UNIT AI ON, Flag 1 false --unit outside zone, SAM OFF REPETITIVE ACTION > UNIT OUTSIDE ZONE > UNIT AI OFF Hope it works, like i said, i'm not home at my PC

OK, when i get home i hope i can take a look at your mission. Meanwhile, try my solution, and yes you should use flags for delay.

Attach the miz file so we can take a look

Like said before, no need for so much flags. If you want to add a time condition do: REPETITIVE ACTION > UNIT INSIDE ZONE or HARM in ZONE > UNIT AI ON, Flag 1 true REPETITIVE ACTION > UNIT OUTSIDE ZONE > UNIT AI OFF, Flag 1 false REPETITIVE ACTION > time since flag 1 - 30 seconds > do something else

First, is LUA not LAU. Second, you can also use (together with MIST) DCS functions: https://wiki.hoggitworld.com/view/Category:Functions In your case, getFuel: https://wiki.hoggitworld.com/view/DCS_func_getFuel Happy coding :)

+1

+1

Had same problem, game stuck in loading screen, starting only if i did repair. Renamed DCS.openbeta and game started OK (it creates a new folder). The difference between them was full screen (when creates a new DCS.openbeta folder it starts like default settings). So, i deleted the newly created DCS.openbeta, renamed back the old one, entered here: youruser\Saved Games\DCS.openbeta\Config and opened options.lua in notepad++. Searched for "screen", and on line 65 you should have ["fullScreen"] = true,. Changed that value to false ["fullScreen"] = false, and started again the game. Now it opens without problem, no stuck or long times to wait - and it is on fullcreen. I don't have any explanations for that, attached is the last log from DCS. dcs.zip

Hmmm, depends what trigger your flag. If you trigger by F10 comm menu, then you can do (using Hardcard's code): A) MISSION START > no condition > - Do Script File (load Moose library) - radio item add: ACTIVATE / FLAG 1 / VALUE 1 - do script: --this is needed so we can use it later Spawn_E3A = SPAWN:New("NATO E-3A Sentry") Spawn_E3A:InitLimit( 1, 0 ) B) SWITCHED CONDITION > FLAG 1 = 1 > - do script (start spawn): Spawn_E3A:InitRepeatOnEngineShutDown() Spawn_E3A:SpawnScheduled( 60, 0 ) Spawn_E3A:SpawnScheduleStart() - radio item remove: ACTIVATE - FLAG 1 = false - radio item add: DEACTIVATE / FLAG 1 / VALUE 2 C) SWITCHED CONDITION > FLAG 1 = 2 > - do script (stop spawn): Spawn_E3A:SpawnScheduleStop() - radio item remove: DEACTIVATE - FLAG 1 = false - radio item add: ACTIVATE / FLAG 1 / VALUE 1 Now let me explain: A) - we load moose, then we define the spawn plane, so it can be used in all scripts. Then, we add to F10 comm menu the option to spawn (ACTIVATE). This will set Flag 1 to value 1 B) - if Flag 1 value is 1, then: the spawn schedule will start, the option to activate another plane will be removed from F10 menu, Flag 1 will be reseted to false (so it can be reactivated later) Instead, we will add an option to stop the spawns (DEACTIVATE). If we don't use DEACTIVATE, Moose will spawn a plane each 60 seconds. If we use it, then: C) - it will stop the spawn and schedule, then it will remove DEACTIVATE option from F10 menu, reset again Flag 1, and add back ACTIVATE and the cycle will start again. Using SWITCHED CONDITION trigger, we can use it how many times we want. This can be achieved in many ways, but maybe is good for you to try learnig a bit from all: LUA, MOOSE and ME triggers :)

Alternative, you can do: MISSION START > no condition > Do Script File (load Moose library) ONCE > your flag condition > flag 1 is true ONCE > if flag 1 is true > do script (here insert your little moose script from your first post)

See some explanations here: https://forums.eagle.ru/showthread.php?t=161463 "...when first installing DCS, the intial menu is rather small and not full screen, however, you will have to first adjust the in-game resolution to match the resolution you run Windows with, and only then go full screen in DCS..." And welcome to DCS :)

Thanks for your help :)

Hi BIGNEWY, find attached the zip with the log - DCS refused to start log.zip

I have Windows 10, I7, 16Gb RAM, nvidia GTX 1050 Ti. First let me update the game with the last version, then if still happens, i will provide you a log file - i hope i won't forget :)

I had the same problem last week, DCS won't close (or taking too much to close), then it remains blocked if i want to start again.

Well, you take a HTML file who shows LUA code. In Github, click raw button (on the right side), then simply select all, copy/paste to your editor. https://github.com/FlightControl-Master/MOOSE_MISSIONS_DYNAMIC/blob/master/ABP%20-%20Airbase%20Police/ABP-001%20-%20Caucasus/ABP-001%20-%20Caucasus.lua

Try to open with Notepad++ (install LuaScript plugin) and see what you get. In LDT, i think you should first have a project.

Read this: https://forums.eagle.ru/showpost.php?p=4044273&postcount=94

Hi Surrexen, it will be possible to make the persistence script as a standalone file, so we can use it in our custom missions? Thanks!

I had the same issue - solved by opening DCS in administrator mode: right click DCS shortcut, then click "Run as administrator"