PravusJSB

I don't think so but I'm not an expert on pre-coded features. It is possible and would be fairly easy to script though. Are you OK with Lua scripting?

Hey, I can help to create something for you to do the job if you like. Drop me a line.

Only AI sensors can paint onto F10, human sensors don't sadly. If you want to cheat and allow a reveal of the FoW in certain area's I posted up my simple and very cheaty method for doing that on someones similar post a few months back. I think maybe I included code, idk.

There's no currently visible method in Lua scripting to query current task's. Your best bet is to write a little tracker class that holds info of what you've sent/pushed yourself, assuming you're tasking yourself in script rather than the ME.

Keep it up!

If you have any overclocks remove them? Update your GPU driver and do any win updates, maybe try optional too. Then see how you go.

How are you spawning the second one and what are the both, player or AI or both?

If you sleep the Lua mission thread then you'll pause the simulation, but for future thought when I do need to make Lua sleep I have a function that solves some complex math in a for loop and i've roughly got it to take a float to determine how long the loop should run (keep solving) and thus pause the thread, in seconds.

good job.

you could visualise it by setting off flares on along the edges of a box to answer that I have no clue, never used other than sphere.

When it comes to tasking, however you can get it to play ball is a win.

I guess if you just clear tasks it will RTB to the closest base as it has no instructions or waypoints.

In terms of performance, I'm passing the whole Syria map into the function and the end to end execution time is 0.001, so the performance seems great.

No, theyre StaticObjects I think.

There's little control you can do on AI landing shenanigans and you'll maybe find that they act like cats if you try to to get specific things to happen lols. Getting them to the location at a specific time should be doable though.

I dont fully understand your issue, could you clarify and I'll try to help?

Im not sure the new preset clouds allows base setting? Certainly its there in the mission part of the miz file once saved, you could try amend there post save. Or fallback to the old clouds.

I think timer.getAbsTime will already return the time of day in seconds, 0 being midnight. You can use a doscript to return timer.getAbsTime() > n as the trigger.

The ETA on the waypoint will also make the AI time their arrival with the ETA time.

I'm not aware of any methods to respawn map objects. It would be better if you made the target a static object, which you can respawn if needed.

Rudel has the right solution there. That attribute is only relevant in the MissionEditor itself.

Set them to uncontrolled and visible maybe, then make an F10 command that wakes them up when youre ready, or I like to let them do what they want but give them a task to keep them above the airfield until youre up and then F10 command to engage them as wingman.

Yea, I mean it's not all relevant to your needs but the way I build my task and the expectations you should be able to extract, if not happy to help further. My code is normally for me only so some of the older stuff I'd yet to figure out the importance of naming conventions and readability so its a bit tougher than it should be. The PointTask func you should be able to copy paste, just replace the function that names it with your own, and theres some duplication because of overloads with the 'ASTAR' that you can stop reading from. So that last task with the looped waypoints is important and the rest you should be OK with. Does not need to be in a coroutine either (sorry if thats obvious), I just copied my live implementation straight out of my AI so its just how its setup but not needed here for you.

Feel free to drop me a discord if you need any more help integrating.