CEX ship configuration files reference

From SWS Wiki
Jump to navigation Jump to search

Back to the SDK main page

COMMENTS

Comments can be written using a // before the text. If a line does not have // in front then it will not be seen as a comment and may crash the application. Examples:
//I am a single-line comment

//I am a comment that continues
//to the next line

//I look like a multiline comment
but I am not and I will crash the program

Back to top | Back to the SDK main page

[TITLE_X]

Use TITLE_X sections to add ships to this class. You can have multiple [TITLE_X] entries in the CEX configuration file. All ships added will share the properties described in this file.

[TITLE_0] Numbered header. Starts with number 0
title=CVA-43 USS Coral Sea 1965 Title as referenced in the sim.cfg or aircraft.cfg file
LvarPrefix=cv43_ The prefix of the variables used for custom animations. In this case, all the animations that will be triggered by CEX start with cv43_. The variable names are declared in the [VISIBILITIES] section.
UIshortName=CV-43 65 A short name for the carrier, displayed in-sim to the user.

Back to top | Back to the SDK main page

Carrier specific

[CARRIER]

Denotes that the simobject is an aircraft carrier. This section should only exist once. All of the features listed here are shared by the [TITLE_X] simobjects.

[CARRIER] Header. Cannot exist twice in the file.
numWires=4 Number of arrestor cables available on the deck.
numCats=3 Number of catapults available on the deck.
numTractors=1 Number of drivable tow tractor types available to the user. See [[#[TRACTOR_X]| [TRACTOR_X] section]]
deckAngle= 13.051 Landing deck angle from ship centerline, in degrees.

Back to top | Back to the SDK main page

[OLS]

The OLS section is used to position the "meatball" and is only used when a [CARRIER] section is present. This is used by CEX to adjust the glideslope light's position based on distance and hook-to-eye distance.

[OLS] Header. Cannot exist twice in the file.
type=1 Type of "meatball". 1=FLOLS mk.1
offset= -39.057,13.418,-30.937 Coordinates of meatball centre light from the model's origin in meters. Positive values are for Right, Up, Forward.

Back to top | Back to the SDK main page

[AIMPOINT]

The aimpoint is where you want the hook of the airplane to touchdown when approaching the carrier. This is on the centerline of the landing strip, between the 2 and 3-wire, so that the hook will catch the 3-wire moving forward.

[AIMPOINT] Header
offset= 0.8,14.164,-98.0 Offset of the optimum hook touchdown point from model center, in meters. Positive values indicate Right, Up, Forward. Used by the OLS and LSO to guide the plane on approach

Back to top | Back to the SDK main page

[WIRE_X]

These sections describe each arrestor cable's properties. There can be any number of arrestor cables you wish on a carrier. For example, you can do a WWII carrier with 15 independently working cables.

[WIRE_X] Header. Numbering starts at 1.
offset=1.673,14.253,-103.058 The arrestor cable's center point. Offset in meters from the carrier origin. Positive values indicate Right, Up Forward.
runout= 152.88378,100 The first number indicates the distance from the cable's center pulled all the way to the deck's edge, in meters. The second value indicates the number of keyframes used in the animation.
left= 18.755,-100 The first number is the distance from the center of the cable to the left spool, in meters. The second number (-100) is the minimum value used by the Lvar that animates the cable's side-to-side pull.
right= 17.054,100 The first number is the distance from the center of the cable to the right spool, in meters. The second number (100) is the maximum value used by the Lvar that animates the cable's side-to-side pull.
height=5.0,5.0 The first number is distance from the cable's center to the maximum height it can be pulled above the deck, in meters. The second number is the maximumvalue,used by the Lvar that animates the cable's vertical pull.

Back to top | Back to the SDK main page

[CATAPULT_X]

This section contains each catapult's start and end point, the type of catapult and how many JBD doors it has.

[CATAPULT_X] Header. Numbering starts at 1.
Type=1 1=Steam catapult. Other types to be added.
startOffset= 10.959, 14.164, 64.487 Coordinates of the shuttle run starting position in meters. Positive values indicate Right, Up, Forward.
endOffset= 7.521, 14.164, 130.106 Coordinates of the shuttle run end position in meters. Positive values indicate Right, Up, Forward.
numJBDs= Number of JBD shields available on this catapult. Unused.

Back to top | Back to the SDK main page

[TRACTOR_X]

The [TRACTOR_X] sections must be as many as the numTractors line denotes in the [[#[CARRIER]|[CARRIER]]] section. Each section describes the geometry of the deck tracktors used to manouever aircraft on the deck of the ship.

The deck tractors can either be default FSX/P3D vehicles or custom-built by you. Hint: don't let the word tractor limit you. You may want to create a drivable forklift or pickup truck to tow your aircraft. Its interpretation is up to you.

[TRACTOR_1] Numbered header. Starts with number 0
deckTractorName=MD3_pushback_tug_cv43 Title as referenced in the sim.cfg or aircraft.cfg file of the tractor.
type=3 Denotes how many towbars and where the vehicle has them. 1=towbar in front only, 2=towbar in rear only, 3=towbars front and back.
towbarLength=4.666 The length of the towbar in meters.
towbarAttachForward=0,0.25,2.296 Coordinates of where the towbar attaches to the truck.Positive values indicate Right, Up, Forward. Meters.
towbarAttachAft=0,0.25,-2.262 Coordinates of where the towbar attaches to the truck. Positive values indicate Right, Up, Forward. Meters.
Axles= 1.231,-0.631 Axle offsets from the center of the model. Steerable axle first, non-steerable second.
ExcludeNums=15,16,13,10,9,5,12,18 Used if your towbar uses a decal system to display random numbers on the vehicle. Numbers in this list will be excluded from the random number generator.

Back to top | Back to the SDK main page

[VISIBILITIES]

Contains the list of animation and visibility variables that can be triggered through CEX. These variables are of the format prefic_variablename. The prefix_ has been declared in the [[#[TITLE_X]| [TITLE_x]]] sections above, so you should only declare the variable names here. This list can grow for as many animations/visibilities you want to control through CEX. These can be visibility conditions or animations. You do not have to declare the animation length (keyframes) in CEX.

[VISIBILITIES] Header. Should not be repeated in the file.
var_1=genvis1 Variable listing. Variable 2 is cv43_genvis1. Only the genvis1 part is declared here, because the 'cv43_prefix has been registered in the [[#[TITLE_X]| [TITLE_X]]] section.
var_2=genvis2 Variable listing. Variable 2 is cv43_genvis2. Only the genvis1,part is declared here, because the 'cv43_prefix has been registered,in the [[#[TITLE_X]| [TITLE_X]]] section.

Back to top | Back to the SDK main page

[FOUL_DECK_SCRIPTS] =

This section allows you to script conditions that will render the deck foul, thus unsuitable for landing. An example is having aircraft parked on the landing area of a carrier. Another example would be the existence of people on a cruise ship's helipad. If you have built-in static models in these areas which are controlled through visibility or animations, you can script the conditions here.

Scripts are listed as Script_X="SCRIPT EXPRESSION". X numbering starts at 1 and the script_expression is in XML.

Variable names used in the script_expression must be used without a prefix and be declared in the [VISIBILITIES] section in order to work.

[FOUL_DECK_SCRIPTS] Header. Should not be repeated in the file.
script_1="(L:park8,bool)" If cv43_park8 evaluates to true, the deck will be considered foul and all approaching planes will be waved off.
script_2="(L:park10,bool)" If cv43_park10 evaluates to true, the deck will be considered foul and all approaching planes will be waved off.
script_3="(L:park8, bool) (L:park10,bool) or (L:park11, bool) or" If one of the three variables evaluates to true, the deck will be considered foul and all approaching planes will be waved off.

Back to top | Back to the SDK main page