Ticket logged

I will have a look. Just wanted to make sure there wasn't 2 different things astray in the cloning as we did have some issues around items actually getting duplicated at one stage

They are not in same order which is understandable as it processes the lists as what is in DB, and then adds and deletes any changes.
But are there any duplicates or missing items between the original and cloned? I didn't notice any.

Should be addressed in build 1827

I think it has to do with the posture of "Downed Pilots" side in the scenario. They only show up when the a 'downed pilot' is created when the P3 is killed. In one replay from the save, the 'downed pilot' was not created, and the civ and nature units didn't show up.
And if I kill the 'downed pilot ...

The expected date format is 'DDMMYYYY' for the wrapper.

However, we have added some override formats to help with the various ways the date can be shown. The character ! after the timestamp tells program how to interpret the string.

m.starttime = "2027-06-09 1:30:00!yyyy-MM-dd H:mm:ss"
m.starttime ...

The database being used by scenario might not have the values. '0' usually means there is no values for that loadout.
I tried it on a scenario based on a DB from 12 months ago and it showed the '0's, but when I migrated it to the latest DB, the expected values showed up

My understanding is that 'solid' means that the type/id of emitter is know which is not related to the AOU.

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&gt;&lt;P&gt;After months of ...

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 ...

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 ...

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.