—-
—-
This is an old revision of the document!
I guess the easiest way to get hang of the tool is with some “practical” examples as done with the attribute emitters. I’m going jump right into the deep end and use as many of the features the tool has as possible.
Load some of the vanilla terrains. I’m using Malden on this sample, at pos ASL [7195.34, 8076.05, 210]; so open debug console and exec the following code:
get3DENCamera setPosASL [7195.34, 8076.05, 180]; get3DENCamera setVectorDirandUp [[-0.484988,0.714168,-0.504743], [-0.283566,0.417564,0.863268]]
and you can see the stone building with the broken oven (or whatever it is):
Select the particle editor (ALT + F1), go to the tool Prefs leaf (CTRL + 8) and check the Use default emitter set box. Move to the baking oven, disable Eden Surface Snapping, point the mouse cursor somewhere near the oven and press SHIFT + INSERT. The default emitter set appears, maneuver it into the baking oven using the translation widget and you now have a fire in the oven:
Let's add smoke coming from the chimney.
Move camera outside and position it so that you can see/access the chimney, press INSERT to insert a single emitter and select SmallDestructionSmoke class for it:
Go to the Basic Params leaf and change lifetime to 20.
IMPORTANT NOTE:
When you change the lifetime param you can see how shortly after you have typed 20 the parameter field changes color briefly to yellow. This means the input is being validated and only after the field turns back to white is the input validated successfully and applied to the emitter. In case of faulty input you get a red Eden notification, the field turns red for a moment and then the field gets applied with either the default datatype for that field or the last known validated input.
You have to wait for the validation to finish until you can change a value in any other param field.
This makes things annoyingly slow but if there wasn’t such a validation faulty data could be “injected” into the emitter causing errors which in turn could cause tools database corruption which would mean the scenario would most likely be FUBAR….