Thu Apr 13, 2006 10:16 am by Accushot
It's not quite as simple as that. An example entry from SolarFormations.ini:
<pre><font size=1 face=Courier>[SolarFormation
nickname = BigSolar_01
type = Big_Solar_Formation
pos = mandatory, Big_Solar, 0, 0, 0, 1, 0, 0, 0
pos = optional, Defensive_Solar, 150, 0, 350, 1, 0, 0, 0
pos = optional, Defensive_Solar, -150, 0, -350, 1, 0, 0, 0
pos = optional, Defensive_Solar, -150, 0, 350, 1, 0, 0, 0
pos = optional, Defensive_Solar, 150, 0, -350, 1, 0, 0, 0
pos = optional, Defensive_Solar, 0, 0, 500, 1, 0, 0, 0
pos = optional, Defensive_Solar, 0, 0, -500, 1, 0, 0, 0 </font></pre>
Each "pos = " line corresponds to an object in the formation. The first argument can be either "mandatory" or "optional" and the second argument is the desired solar type, but note that the first entry must be declared as mandatory and (AFAIK) of type "Big_Solar" if you're going for a standard solar-killing mission.
The next seven numbers correspond to the position and orientation of the object, in the form "x, y, z, a, b, c, d". Note that all positions and orientations are relative values, not absolute ones that you'd declare in the system files. If you're unsure of the quaternion orientation format just use "1, 0, 0, 0" for a standard orientation.
To solve your problem you need to simply increase the position offsets of each additonal solar so that they'll appear further from the main solar, e.g. change
<pre><font size=1 face=Courier>pos = optional, Defensive_Solar, 150, 0, 350, 1, 0, 0, 0 </font></pre>
to
<pre><font size=1 face=Courier>pos = optional, Defensive_Solar, 600, 0, 950, 1, 0, 0, 0 </font></pre>
Edited by - Accushot on 4/13/2006 11:19:36 AM