[TEC] Mystery of mission related CTDs solved!

tater · 07-01-07, 03:26 PM

A note to people creating missions with random groups:

Columns in random groups must be equal or less than the lowest possible number of ships in the group.

The formation allows a number of columns, and a spacing to be set. The number of columns can never be less than the number of ships or it CTDs every time.

I have this in my layers because I attempted to create a wide variety of random formations with a single group. I mad them with many many ships listed in some cases, with each ship of a low order of probability. So you might well see a TF with 20+ ships, but 5 might be more likely, and as few as 2 might be possible (if extremely unlikely).

I let the automated campaign editor pick random spacing and columns to mix things up.

If a convoy generates 2 ships, and is set to 3 columns, BOOM!

Version 0.68 will be out shortly with all of this fixed.

Thanks to Jace11 (yet again). He actually pointed out this as a possible problem a few days ago, somehow I missed it.

07-01-07, 03:26 PM	#1
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	[TEC] Mystery of mission related CTDs solved! A note to people creating missions with random groups: Columns in random groups must be equal or less than the lowest possible number of ships in the group. The formation allows a number of columns, and a spacing to be set. The number of columns can never be less than the number of ships or it CTDs every time. I have this in my layers because I attempted to create a wide variety of random formations with a single group. I mad them with many many ships listed in some cases, with each ship of a low order of probability. So you might well see a TF with 20+ ships, but 5 might be more likely, and as few as 2 might be possible (if extremely unlikely). I let the automated campaign editor pick random spacing and columns to mix things up. If a convoy generates 2 ships, and is set to 3 columns, BOOM! Version 0.68 will be out shortly with all of this fixed. Thanks to Jace11 (yet again). He actually pointed out this as a possible problem a few days ago, somehow I missed it. Last edited by tater; 07-03-07 at 09:19 AM.