funkyfranky

Did we? We had a system to (dis-)credit a person for a specific post but not a post itself. I think it would be useful to rate good/bad posts independent of who actually posted. There are simply too many to read them all. If I could read though the best posts of a day/week/month I would save a lot of time and probably not miss a lot of good info (or read a lot of rubbish).

Easter egg

Could simply be that the valid airports don't have any parking spots specifically for helos? Many airports actually have not.

Alte Moose.lua Datei! Du brauchst die aus dem Development branch https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop/Moose_Include_Static Pass auf, dass Du wirklich die lua Datei und nicht die html Datei runterlädst. Ach ja, die Sound files fehlen in der Mission auch. Ohne ist es langweilig ;) Du bekommst alles auch aus der Beispielmission von oben. Einfach mit 7-zip öffnen.

Jup!

Drückst Du zwei mal ESC bevor Du in den Flieger steigst. Wenn nicht, erkennt das Skript nicht, dass Du in der Maschine bist und die Menüs werden nicht erstellt. Ist leider ein uralter DCS bug. Wäre jedenfalls meine erste Vermutung - kann auch was anderes seien. Häng ansonsten mal Deine miz Datei an. E: Sniped :gun_sniper:

Dein Skript sieht erst mal gut aus. Wo hakt es denn?

Schau dir erst mal die Beispielmission an https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Airboss/Caucasus/BOS-100%20-%20Stennis%20Hornet%20and%20Tomcat Und die Dokumentation https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Ops.Airboss.html

You can use the OnSpawnGroup callback function to get the spawned group and its name: https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Spawn.html##(SPAWN).OnSpawnGroup

Here we go again... Same problem, same fix. Looks like it happens to me every 2-3 months now.

Just tested again, it's working fine. Try this mission https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Airboss/Caucasus/BOS-100%20-%20Stennis%20Hornet%20and%20Tomcat But give the helo enough time to take off if you do an air start.

There was some (undocumented) change in DCS that caused trouble with the ejection event. Try the Moose development lua from https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop/Moose_Include_Static PS: Make sure you really downloaded the lua (right click, safe as) and not the html file. This is a bit tricky with the github link, sorry.

Which Moose version are you running?

Yeah, I have it set up and it's pretty cool. You need to import the F10. It's briefly described in the VAICOM manual. However, there is one catch. The F10 airboss menu has to be always in the same place as you have exported it, i.e. it requires always same F-key sequence so to speak.

Cooles feature. Im Moment brechen bei mir nur die FPS dramatisch ein, sobald mehrere Flugzeuge in der Nähe sind. WWII und sich einem etwas größeren Bomberverband nähern führt zum Daumenkino. Aber die Skalierung kriegen sie hoffentlich noch in den Griff :)

How is the performance scaling (or will scale) with the number of AC in the vicinity? Currently, I find that it leads to severe FPS decrease if you approach multiple AC let alone larger formations of bombers.

Du sagtest aber ausdrücklich, dass das Problem auftritt, wenn Du in der Luft bist und das Fahrwerk eingezogen ist. Wat denn nu?

You have that script in a scheduler function and call it every X seconds? If not, it is only executed once and if at that time, the target is not detected, the flag will never be raised.

So here is the miz (PG map unfortunately). Tasks are pretty trivial and straight forward. FollowTask.miz

Sounds interesting. I did not set any stop condition as I wanted the escort on the whole way. I did play around with the last waypoint option quite a bit (on/off). Result was always the same. I also tried a task for the B-52 to orbit before the bombing run. There the fighter stayed in formation, i.e. the follow task was working as expected. Funny thing is that the "Follow" task must still be active during the bombing run as the fighter resumes the formation as soon as the bombing run is over. (Not sure if I had mentioned that explicitly earlier.) I'll attach a little test mission later or tomorrow. That gives us a more solid foundation for the discussion :)

Situation: Fighter (F/A-18C) gets task to "Follow" or "Escort" a B-52 bomber. The bomber has task "Bombing" a location on the map. Result: Fighter follows bomber as expected. Once the bomber starts the "Bombing" task, the fighter stops the follow/escort task and proceeds to its next waypoint where it orbits until the bombing task is accomplished. Question: Maybe this is intended but I see no reason why the fighter would stop the escort when the bombing task is active. So is the the intended behaviour and if so, is there a way that the escort task is not "paused" while the bomber attacks?

Well, not surprised you figured it out given your knowledge :thumbup:

Hmm, unless you monitor which units enters/leaves a zone, there is no way to determine whether it is inside/outside the zone other than iterating over all units in question. The trigger function will probably do the same internally. I'd check https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Set.html##(SET_GROUP).AnyInZone That looks like the most convenient way :)

I guess, then the only option is to first perform a scan in the zone area. Would that be a viable solution for you? Is it a circular or more complex zone?

Cool, danke!