Zayets

Quickly glancing over script it looks like return values are hardcoded in the script itself so you will probably have to modify the script itself

Here, a quick and dirty function to return true if group is dead or false if it's still alive [color=#d3af86][font=Consolas][color=#a57a4c]--Check if group can be discarded from the books. If sum(Units lives) less than 1 the group is dead for me[/color] [color=#98676a]function[/color][color=#8ab1b0] groupIsDead[/color][color=#d3af86]([/color][color=#d3af86]inGroupName)[/color] [color=#98676a]local[/color][color=#d3af86] groupHealth [/color][color=#d3af86]=[/color][color=#f79a32]0[/color] [color=#98676a]local[/color][color=#d3af86] groupDead [/color][color=#d3af86]=[/color][color=#f79a32]false[/color] [color=#98676a]for[/color][color=#d3af86] index, unitData [/color][color=#98676a]in[/color][color=#7e602c]pairs[/color][color=#d3af86](Group.[/color][color=#8ab1b0]getByName[/color][color=#d3af86](inGroupName):[/color][color=#8ab1b0]getUnits[/color][color=#d3af86]()) [/color][color=#98676a]do[/color] [color=#d3af86] groupHealth [/color][color=#d3af86]=[/color][color=#d3af86] groupHealth [/color][color=#d3af86]+[/color][color=#d3af86] unitData:[/color][color=#8ab1b0]getLife[/color][color=#d3af86]()[/color] [color=#98676a]end[/color] [color=#98676a]if[/color][color=#d3af86] groupHealth [/color][color=#d3af86]<[/color][color=#f79a32]1[/color][color=#98676a]then[/color] [color=#d3af86] groupDead [/color][color=#d3af86]=[/color][color=#f79a32]true[/color] [color=#98676a]end[/color] [color=#98676a]return[/color][color=#d3af86] groupDead[/color] [color=#98676a]end[/color] [/font][/color] EDIT: btw, you can also try this (but most probably even if the group is dead it will return true, didn't tried it but you can give it a shot) : Group.getByName('MyGroupName'):isExist()

UPDATE: I have tested a new mission, worked flawlessly. Then went into my mission and checked, the issue still there. Deleted the unit, added a new Hornet client controlled this time. Worked like a charm. No bug. Also, could it be that it was a failure? If so, that would be neat.

Alright, so basically there is an issue. I am trying this on a new mission so it should not be a problem. Also, this is single player.

Can't seem to make COM2 move from guard channel. The COM2 knob rotates showing the channels but UFC display stays on G with a G U A R D shown on the stacked displays to the right of the keypad. Anything changed or is this a bug?

Is this something already decided by ED? It's intriguing because Microsoft is pushing the Linux subsystem in their Windows desktop OS for quite a while now. Which means that a non-graphical 64 bit Linux program will most probably run without major modification (if any). Whoever runs a dedicated server will most probably do so on a different box (sometimes even a laptop). A Linux box which does not need an X11 server would be really low in specs but if you'd like to have the same box opening Windows (even Home edition) you would need a system having a graphics card (not sure if DCS today opens up on a system having an onboard graphic card like Intel, that may be very well the case). In any case, just the news of having a dedicated server makes me very happy (actually even more happier). Don't exactly care if this would be Windows or Linux as long as it works as expected. Linux is a bit more stable than Windows simply because it strips lots of unnecessary $h!t in order to be up and running and it doesn't nags you when you want to remove features deemed as "core" (like sending your personal details to Redmond). Yep, looking forward to this feature, whatever ED chose as long as it works.

Change Coalitions mod. Download and install (manually or via any mod installer). Here's the link : https://www.digitalcombatsimulator.com/en/files/1970350/ EDIT: remember, this will only re-arrange coalitions.

In the same waypoint you have Search and Engage in zone, before this very task, give your flight the task to Orbit for a given time. What happens is that your flight arrives in the zone, finds nothing yet and leaves as probably the Migs are not there yet. You should make them stay a while there.

https://wiki.hoggitworld.com/view/DCS_func_getWind

Short answer : no. Wingman is just an AI plane and the only thing you can do to play with bingo fuel call is to setOption for the group as RTB on bingo in advanced waypoint actions. But then if he behaves like you say then this is no solution, obviously. Long answer : yes. You can script it quite easily using getFuel() function. You build a waypoint right before landing and once getFuel is at the level you set then you send him to the waypoint just before landing. From there on, your wingman should go landing. https://wiki.hoggitworld.com/view/DCS_func_getFuel

Just send him home when you hit bingo.

Sure there is :atmosphere.getWind(table vec3 ) and atmosphere.getWindWithTurbulence(table vec3 )

Every mission will have units renamed as DirectKey_XXXX

This is a question for the MIST creators or MIST experts. Here is the scenario. I am adding a new group with dynAdd. This works a treat, no issues so far. Group spawns exactly in the point(s) defined in the units table. After the group is spawned, I can get the group details through the table returned by function dynAdd. However, it looks like it is not a proper group as I can't use Group.getByName() for example. Log is saying group is not in the MIST database. Is there a way to interrogate the groups spawned with MIST?

Not really difficult I assume but it needs a new set of recordings and hook them to the game engine to make it possible.

It should be possible. I believe command should work. https://wiki.hoggitworld.com/view/DCS_command_script

I believe is much more productive to think of a workaround than ranting about known limitations. If you were around here when LOMAC was launched you would probably understand how huge leap ME has made during these years. Not to mention the fact that ED gave us the posibillity to access the internals through Lua. It is not perfect but then again, what is?

Try mist.DB.missionData

Actually it is gone now in Beta 2.5.2.19273. No more top down views in ME. I can't see the top down view. I can however see the neutral coalition bullseye. test_topdown_view_models = true Uncommented all three lines in the beginning of the MissionEditor.lua. No joy EDIT: disregard. I just seen the little button in ME doing just that.

You can also try MOOSE, it looks a bit easier to play with static objects there.

I don't think you can access the function definitions themselves. DCS is exposing its internals through these lua functions. They could have chosen any language for this. Imagine these lua functions as some knobs to operate your washing machine. You can play with them to alter the state of the machine but they are hardwired and you can't change their function unless you rewire the whole stuff.

local staticObj = {... your_object_data ...} coalition.addStaticObject(1,staticObj) https://wiki.hoggitworld.com/view/DCS_func_addStaticObject dynAddStatic in MIST should work as well.

I believe the OP wanted to know if he has any access to modify the functions exposed by DCS and not only calling them.

Add one aircraft circling the AAA and make it immortal

Here's a quick and dirty script I just made drinking my coffee at work. You will need to load MIST before executing this script. Mind you, this will not tell you exactly when Texaco will actually RTB but it will warn you that it is low on fuel. Change 0.25 for a lower value if you want. function callLowFuel() remainFuel = Unit.getByName('Texaco'):getFuel() if remainFuel < 0.25 then trigger.action.outText('Texaco low on fuel', 10, true) end end do mist.scheduleFunction(callLowFuel,{},timer.getTime() + 60, 120) end You can refine it further by unloading the function from memory if you need that. Remember to change the unit name or the fuel qty as desired. Fuel qty is a number between 0 and 1 unless that particular unit does not carry external fuel tanks in which case the qty is bigger than 1