MWExp params

You can create a special dummy to contain global information on the export of the objects present in that max file.

• The name of the dummy must be $ MWExpParams.

• Only one special dummy permitted per max file.

• The dummy has two characteristics: Export parameters and defines.

Export Parameters

You can set a bExportWorldSpace parameter for the export action:

• This indicates whether the export of the objects in this max file are exported to world space.

• The bExportWorldSpace parameter value overrides the Prefer World Space Data parameter in the exporter dialog.

• The range is True/False.

Defines

Use the defines to define common parameters that the various shaders can use.

Scenario example

For example, if shaders require the parameter fEmissiveMul, normally you must define the value of this variable inside each mesh:

fEmissiveMul = 1.24

To change this value, open all the meshes and reset it.

Defines method

Using the defines method instead, you can define a variable within this dummy and then use it in many other parts.

You can define up to 128 definitions within a special dummy.

Use defines

In the mesh, write:

fEmissiveMul =% fEMISSIVE_VAL_PALAZZI \\

In the dummy, write:

fEMISSIVE_VAL_PALAZZI = 1.24

Syntax

• The syntax of the variable (such as in the shader) is % and then the name of the Define. Example: fEmissiveMul =% fEMISSIVE_VAL_PALAZZI.

• The syntax of the Define is the type of the parameter (such as f because in this case we wanted to set the float value fEmissiveMul) followed by the name of the Define and its value. Example: fEMISSIVE_VAL_PALAZZI = 1.24.

Examples

A code example for creating a Dummy called $ MWExpParams.

Write the following code in its user buffer.

Note: You do not have to include both the $ Params and $ Defines structures. Include only what you need.

$Params

{

bExportWorldSpace = false

}

$Defines

{

fEMISSIVE_A = 0.3

szCUBE_NAME = nome.dds

}