It means that (native) code is looping over a set of ships – looks like an escort group – and changing it during the traversal, which is not allowed. This is happening during the simulation step of the Armoured Transport Type1, which is probably the mothership of the escort group.
Edit: After some searching through the code, it seems unlikely that it’s actually an escort group.
it seems unlikely that it’s actually an escort group.
The official escorts of the "Armoured Transport Type1" ship should be all the same and have the name: "Armoured Transport Viper". And there should only be 4 escorts maximum.
I wonder if these two are other aspects of https://bb.oolite.space/viewtopic.php?f=3&t=13480 , which also appears to be some Mac-only memory corruption problem. There's certainly no obvious code path for either.
Do you still get the carrier oddities in the latest Mac nightly?
I wonder if these two are other aspects of https://bb.oolite.space/viewtopic.php?f=3&t=13480 , which also appears to be some Mac-only memory corruption problem. There's certainly no obvious code path for either.
Do you still get the carrier oddities in the latest Mac nightly?
I haven't got around to installing the nightly, but I'm going to try over the weekend.
I tested the "Urutu MkIV" after the error message and the shipGroup and escortGroup were empty. This "Urutu MkIV" is always spawned as trader without escorts.