mGen 0.2 ALPHA

Beschreibung: mGen User's ManualDISCLAIMER: Use at your own risk! I won't be responsible for any time lost!Table of Contents * Installation * Concepts * Importing a map * Adding Regions * Assigning Rules * Managing Rules * Exporting a map InstallationJust unzip the package in the directory of your choice. Note that the working directory is the directory in which you extract the package. It is recommended that you import maps from this directory and save layouts to this directory.ConceptsmGen is used to import a map in a form that can be used to manipulate it. This form is called a "layout". The layout contains a preview of the map, as well as any Regions defined. Rules are executed on export within these Regions (the Regions delimit where textures and objects are placed). Layouts can be saved and later retrieved.A Rule Tree is in the bottom-left corner, which shows which Rules have been defined. In the top left corner is the Rule Property window, which shows the properties of the selected Rule.Importing a MapA note on coordinates: Morrowind uses "logical" coordinates. The map you are importing probably uses "world" coordinates (i.e. meters/feet). For this reason, you will probably have to tweak the import settings until the map looks like you want it to. It is highly recommended that you make sure that you determine the appropriate import settings for your map by trial and error before adding any objects/rules. Try some settings, export, view in TES, and repeat until you find the correct settings, then save with those settings.Choose "File->New Layout" or "File->Import Map". Both do the same thing.The Import Settings dialog will appear. Note that these settings cannot be changed after a map is loaded! * Baseline Height: set the lowest point on the map. It is in logical coordinates. -2048 is the sea floor. Overridden if "Use Map's Height Limits" is checked. * Max Height: set the maximum height point on the map, in logical coordinates. Note that Morrowind does not support heights greater than 16000. Overridden if "Use Map's Height Limits" is checked. * Use Map's Height Limits: the map's "world" coordinates are directly translated into logical coordinates. The world coordinates are divided by 8 (reason: internal map handling). If the maximum height is over 16000 (or 16000/8 = 2000), the map is scaled down so that the maximum is 16000. * Invert Elevation values: inverts all elevation values. NOTE: negative elevations are not well handled by mGen at this time. * Number of Cells X: X cell size of the map. 0 will automatically size the map according to the number of data points in the imported map. * Number of Cells Y: Y cell size of map. Ignored if "Keep Aspect Ratio" is checked. * Keep Aspect Ratio: keep x and y cell sizes proportional to imported map. * Map Smoothing: reduces roughness of the map features. * Display Sea Level: Displays sea level on the preview map (blue) * Display Elevation Lines: Displays elevation lines at every 100 logical elevation points. Click Import to import the map.Click Save to save the current Layout.Adding RegionsSeveral tools can be used to add "Regions" to the map. These Regions act as delimiters for applying rules. Rules are only applied on or within the region defined by a Region.A Region can be a line, a rectangle, an ellipse, or other types. It will first appear with a white border. A white border means that the Region does not have a rule assigned to it.Assigning RulesTo assign a rule, select a Region by clicking on it and double-click on a rule in the rule window. If you click on a sub-rule, the parent rule will be assigned. The Region should turn red when assigned.If you click on assigned (red) Regions, the corresponding rule should show up as selected in the rule tree (so you can find out which rule is assigned).Z-Order is important for texture sub-rules. The bottommost Region is applied first, then the next, etc. "Lower" texture sub-rules are obscured by "Higher" sub-rules. To change the Z-Order of a Region, use the "bring forward" "move to back" etc. controls.Managing RulesThere are three basic types of Rules: Top-Level Rules, Texture Sub-Rules and Object Sub-Rules.Top-Level Rules are basically placeholders for sub-rules. Note: NAME YOUR RULES WITH A UNIQUE NAME. Otherwise, when loading a layout, some objects may not be assigned to the right rule. The only value that can be changed in the Rule Properties window is the name of the rule.Texture Sub-Rules define which textures are applied under which condition. Only the texture name can be changed (the texture value will be automatically updated), and the condition (See Rule Reference). Note that Region Z-Order is important for texture sub-rules.Object Sub-Rules define which objects are applied under which condition. All properties may be changed, except the "value" field, which is automatically updated.Rule Tree Context MenuThis menu can be used to manipulate Rules and sub-rules (note: there is no way at this time to change the order of the rules) * New->Rule: creates a new empty rule * New->Texture Sub-Rule: creates a new texture sub-rule under the selected Top-Level Rule. Default values are used * New->Object Sub-Rule: creates a new object sub-rule under the selected Top-Level Rule. Default values are used * Show: Show the Regions assigned to this rule. Visible rules have a GREEN icon. * Hide: Hide the Regions assigned to this rule. Hidden rules have a RED icon. * Show All: Show All Regions * Hide All: Hide All Regions * Copy (Ctrl-C): Copy selected Rule or sub-rule * Paste (Ctrl-V): Paste copied rule and apped to Rule Tree, or paste sub-rule into selected Top-level Rule * Delete (Del): Delete Rule (and all children) or sub-rule To change rule properties, select the rule or sub-rule. The Properties window will reflect the current values. Values may be edited, and set by pressing the "Set" button.Rule properties * type: Rule, Texture, or an object type (Tree, Flora, Terrain) * name: the name of the rule or sub-rule texture or object * value: data associated with the rule or sub-rule (auto updated) * condition: (sub-rule only) logical condition (true or false) under which a sub-rule is applied. When a map is exported, the map points within each Region are evaluated against the sub-rule conditions. If the condition resolves to TRUE, that point will have a texture or object placed there. A condition recognizes the following keywords: o NodeSlope: the slope in degrees of the map point being evaluated. May be negative o NodeAbsSlope: the absolute slope in degrees of the map point being evaluated. o NodeHeight: the height of the map point being evaluated, in logical values. o RandomPercent: a random number between 1-100 The following operators are recognized: o LT (lesser than, synonym: <) o LE (lesser or equal, synonym: <=) o EQ (equal, synonym: ==) o NE (not equal, synonym: !=, <>) o GE (greater or equal, synonym: >=) o GT (greater than, synonym: >) Expressions can be joined with AND (synonym: &&) and OR (synonym: ||) Paranthesis should be used to define each expression. Example: INCORRECT: NodeAbsSlope LT 50 AND NodeHeight LT 500 CORRECT: (NodeAbsSlope LT 50) AND (NodeHeight LT 500) The default condition is 1 (true, always apply) * spacing: (object sub-rule only) grid spacing between objects. * scale: (object sub-rule only) in-game size scaling of the objects (max 2.0) * fuzz: (object sub-rule only) a random value used to offset the X and Y coordinates of each added object. This is to prevent objects being aligned in a grid when spacing is used, and slightly randomizing their exact placement. Note that if the fuzz value is high, the objects may overflow the associated Region's defined borders. * rotationX, rotationY: rotation along the X and Y axis. The special keyword "slope" is recognized. If "slope" is defined, the object X rotation will be aligned with the Y slope, and/or the object Y rotation will be aligned with the X slope. * rotationZ: rotation around the Z axis * zadjust: height adjustment of object to be added. This is sometimes necessary with objects that have an X or Y rotation, or that have no rotation but are to be placed on steep slopes. The objects will appear to "float". A negative zdajust will lower the object by the specified value. Exporting a MapSelect File->Export MapChoose the file name to Export toThe Export Settings dialog will appear: * Cell Name: the name of the cells * X and Y origin: X and Y origin of the bottom-left cell in game coordinates