I think the top mining mission is suffering from the slack given to when it decides if it has reached the mining area; may not be catering for a single point-point 'area'.
Will check it out.

Don't know much about the new cargo system but ...
For the airbase, you were unloading from the airbase, and not the aircraft?
I would have expected that the same would happen, unloading from the port base rather than the ship.

Open up the RS1.scen file with a text editor like Notepad++. <?xml version="1.0"?> <ScenContainer xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ScenTitle>RS1: Morning Recon</ScenTitle> <ScenDescription>&lt;BODY&...

1 - Spawning the ship with LUA isn't an issue, but is there a way to get the new unit's GUID via LUA? When I do my mods at the moment, I have to copy/paste the GUID in manually like below, which obviously isn't really doable for releasable scenarios. local u = SE_GetUnit({guid='xxx'}) Depending on ...

Thanks, I will check them out.

There seems to be an empty row in the expenditures from look of it. It is crashing on trying to get the weapon name.

As suspected, it is out of fuel. Checked start of scenario, and its fuel is about 50% full. Probably needs fill-up from the AO before completing the mission.

To continue I suggest getting the AO to move to the transport and fill it up.

Never mind. I ran the scenario again this time just activating it and I got what you see. The target is 'lost', and the planes just circle the pre-launch point. They actually seem to be launching in 'Mission over' state with 'no target' defined even though there is a flight plan to the target. Defin...

The mission shows 'no targets' in the autosave.
When I run the 'carrier strike' scenario setting the target as the enemy carrier, it plays out and all planes returned to base.

Did you manually drop the target from the mission after the planes were launched?

If you correct the Lua script, does it lock up later?

Trying to eliminate known errors to get to a solution.

The script to turn off 'Bear Island' zone has an error in it; the zone type parameter is a number as shown in the Docs, but the script has it as a string. That is failing every 15 seconds and writing to the logs. It should be ScenEdit_SetZone('NATO', 0, {description='Bear Island', isactive='false'})...

Are there any errors showing in the ExceptionLog.txt during the run??

I was showing Lua exceptions; continual errors could slow the game down while running.

morphin wrote: ↑Wed Aug 23, 2023 4:39 am Thank you very much

You can verify that it will manually drop them by deleting that sonobuoy from one of the MQ-8's

Okay, you found another DB issue!!!
There are no sensors on the AN/SSQ-36 which is blocking the manual release of the other sonobuoys.

Added a safety check to ignore this issue in the next build so it won't block dropping other buoys.

morphin wrote: ↑Tue Aug 22, 2023 9:30 am Ok. After adding a sonobuoy comms link the V-247 drops.

But if i unassign and try to manually drop sonobuoys that doesn't seems to work.....

That seems to be an issue with the current build as stated. I think it has been fixed for the next build but will verify..

I don't think the cargo editing can be done on a 'group' as the cargo is stored in specific units within the group. It doesn't work like the shared magazines does from memory. It might be nice to have that but there will overheads in telling it each time which specific platform to put the cargo into...

I will be retrofitting support for the new cargo types into UpdateUnitCargo() for the next build. local u = ScenEdit_GetUnit({name='Yokosuka Building 14 (Large)', guid='29541903-93d0-436b-9f08-a4696f12a4fc'}) print(u.cargo) local a = ScenEdit_UpdateUnitCargo({guid='29541903-93d0-436b-9f08-a4696f12a4...

The new cargo method uses a different way to add cargo. It is run off the unit wrapper as a method. There is a 'delete' method too: u:deleteUnitCargo(cargo_guid) local u = ScenEdit_GetUnit({name='Single-Unit Airfield (4x 4000m+ Runways)', guid='CY41MA-0HMT2K1IOQ76K'}) print(u.cargo) u:createUnitCarg...

An issue with 'buddy store' refueling has been addressed for next build. This is probably related to the above.

The V-247 doesn't have a sonobuoy comms link. Added one to a V-247 and it started dropping them.

DB issue