AliasAlToJt

Purpose

AlToJt translates Alias wire files to JT format files.

Description

AlToJt [ options ] -i<input Wire file> -o<output Jt file> -f <scm file>  
-h outputs online help, then exits
-f <scm> specifies the name of the Alias User Option scm file (see below)
-g converts the wire file in a single DirectModel (.jt) file
-l creates a logfile (with .alias2jt extension) containing Alias to DirectModel translation messages
-p creates a file (with .sg extension) containing an indented representation of the scene graph
-ta tessellates all Alias surface geometry using accurate tessellator
-to tessellates all Alias surface geometry using fast tessellator
-tl# sets number of Alias tessellation LODs. # must be between [1,3] (default = 1)
-t <tol> sets the tolerance for LOD 0 (in centimeters, default = 0.1) for Alias accurate or fast tessellator
-t1t<tol> sets the tolerance for LOD 1 (in centimeters, default = 0.25) for Alias accurate or fast tessellator
-t2t<tol> sets the tolerance for LOD 2 (in centimeters, default = 1.0) for Alias accurate or fast tessellator
-wc outputs curves
-wi outputs invisible entities
-wk outputs cameras
-wt outputs templated entities
-ws outputs layer symmetry (merged)
-wsu outputs layer symmetry (unmerged)
-m0 exports geometry type – polygon only
-m1 exports geometry type – polygon and brep
-wx brep type JtkXTBrep
-wb brep type JtkBrep
-xs doesn't output shaders
-xt doesn't output textures
-xl doesn't output lights
-xk doesn't output cameras
-e1g organizes data first by geometry
-e1s organizes data first by shader (default)
-e1l organizes data first by layer
-e1b organizes data first by SBD structure
-e2s organizes data second by shader; does not work with e1g
-e2l organizes data second by layer; does not work with e1g
-es sorts data by name; works with either primary or secondary ordering by shader or layer.
-q sews surfaces together
-s <scale> specifies geometry scale factor (default = 1.0)
-u <image res> specifies texture file image resolution used during 3D (solid or environment) texture conversion. Valid resolutions are 8 ... 8192. Default = 128.
Texture blending mode: (see notes below)
-bmb BLEND mode
-bmd DECAL mode
-bmm MODULATE mode
-bmr REPLACE mode
Where:  
-i <infile> specifies an Alias wire file to use as input. If not specified, input comes from stdin.
-o <outfile> specifies a JT file to write output to. If it is not specified, the output is written to stdout.

Texture blending mode

The texture blending mode options are only available through the AlToJt command line interface (no equivalent exists in the option window). They specify which texture blending mode will be used when exporting the file. The blending mode controls how the material color and the texture color of the part interact. Only one of the four options should be specified at a time. See table above.

If a blending mode is specified and a texture is mapped to the color channel, then both the material color and texture properties will be available in the JT file, and the blending mode will be set accordingly. If no blending mode is specified, no blending will be performed in the JT file, and only the texture will be set for the part.

Alias User Option (scm) file

The Alias User Option file is a text configuration file in a scheme format. A template is located in your local Alias installation under:

Program Files\Autodesk\Alias2010\Scheme\Modeling\dt_jt.v.scm.

It contains all the configuration parameters with their description. This file lets systems administrators edit the export parameters (options) then specify the filename in the command line instead of the individual parameters. For example:

AltoJt.exe -f "r:\directory name\dt_jt.v.scm"

This way the parameters can be changed while the command line always remains the same.

Note: The file should be copied into a directory with write permission, and made writeable before editing.

The scheme format has simple editing rules:

LOD labels

Labels for the tessellation levels of detail (LODs) can be set through the scheme configuration file (described above), but not as individual command-line arguments.

If you are not using a configuration file, you can set the labels by setting these environment variables:

For example: ALIAS_JT_LOD0_LABEL=Fine

Allowed characters are letters (upper and lower case), numbers, underscore ("_") and white spaces.

Note: Labels specified through the scheme configuration file override the environment variables.