POM etc

Author: jankrassnigg

pages/docs/animation/skeletal-animation/animation-clip-asset.md

@@ -24,6 +24,8 @@ Animation clips can also be imported automatically when [importing an animated m
 
 * `PreviewMesh`: The [animated mesh](animated-mesh-asset.md) to use for previewing this animation clip. This has to be set to see any preview.
 
+* `PreviewAnim`: For additive animation clips, this optionally selects another animation clip to use as the reference pose in the editor preview. The first keyframe of that clip is used to reconstruct the base pose, and the additive animation is layered on top. This makes the preview more representative of how the clip will look in practice. If left empty, the rest pose is used instead.
+
 * `UseAnimationClip`: The (case sensitive) name of the animation clip to import from the file. *Transform* the asset once to populate the list of `AvailableClips`. Then type the name of the desired clip into this field and transform the asset again. If a clip doesn't show up in the list, make sure it is correctly exported. See the chapter [Authoring and Exporting Animations with Blender](blender-export.md) for known issues.
 
 * `FirstFrame`, `NumFrames`: It is best to put every animation into a separate clip and export them that way. However, sometimes files contain only a single animation and each clip is found at another interval. By specifying the index of the first frame and the number of frames to use, you can extract individual clips from such data. Note that setting NumFrames to zero always means to use all the remaining frames after the first frame.
@@ -36,7 +38,7 @@ Animation clips can also be imported automatically when [importing an animated m
 
   > **Important**
   >
-  > Additive animations usually only work well, if they are applied to a skeleton that is in a similar pose as the reference pose of the additive animation. The animation clip window always displays the animation on top of the *rest pose*. This can look very broken, especially when the rest pose is a proper *T-pose* or *A-pose*.
+  > Additive animations usually only work well, if they are applied to a skeleton that is in a similar pose as the reference pose of the additive animation. By default the animation clip window displays the animation on top of the *rest pose*. This can look very broken, especially when the rest pose is a proper *T-pose* or *A-pose*. Use the `PreviewAnim` property to select a more representative reference animation for the editor preview.
 
 * `RootMotion`: If the animation clip should be able to move the [game object](../../runtime/world/game-objects.md), this can be achieved through [root motion](root-motion.md). This option allows you to select how root motion should be incorporated into the animation clip.
 

pages/docs/custom-code/visual-script/nodes/vscript-nodes-game-object.md

@@ -10,6 +10,7 @@ Common game object operations:
 * **Hierarchy navigation** - Find parent and child objects, search by name
 * **Component access** - Get components attached to game objects
 * **Object state** - Check if objects are active, valid, or tagged
+* **Tag management** - Set and remove tags on game objects with `SetTag` and `RemoveTag`
 * **Object creation** - Spawn and destroy game objects dynamically
 
 Game object nodes are fundamental to most visual scripts, as they allow you to locate and manipulate objects in the scene. Use them together with [component nodes](vscript-nodes-component.md) to access specific functionality, and [prefab nodes](vscript-nodes-prefabs.md) to instantiate new objects.

pages/docs/custom-code/visual-script/visual-script-class-asset.md

@@ -34,7 +34,7 @@ Through the general script properties you can add *variables* to your script. Th
 
 ### Variable Types
 
-Variables support various data types including numbers, strings, vectors, and more. Additionally, you can create:
+Variables support various data types including numbers, strings, and vectors. The available vector types are `Vec2`, `Vec3`, and `Vec4`. Additionally, you can create:
 
 * **Array Variables:** Set the variable category to *Array* to create a typed array. On the component side, arrays are displayed with their element type for better readability. Note that internally within visual scripts, arrays store variants and are not strictly typed.
 

pages/docs/materials/materials-overview.md

@@ -76,6 +76,14 @@ For testing transparent materials it may be useful to create an object in a scen
 
 **UseEmissiveTexture:** If enabled, the *Emissive Texture* is used to define per pixel where the material will *glow*. This is multiplied with the *EmissiveColor*, so make sure that is not set to black (its default).
 
+**UseHeightTexture:** If enabled, a *Height Texture* (also called a heightmap) is used to apply *Parallax Occlusion Mapping (POM)*. This technique offsets texture coordinates based on the viewing angle and the stored height values, giving flat surfaces an apparent depth without additional geometry. All other textures (base color, normal, roughness, etc.) are sampled from the offset coordinates, so the entire surface appears to have relief.
+
+The height texture should store height values in the red channel. Brighter values represent raised areas, darker values represent recessed areas.
+
+**HeightScale:** Controls the strength of the parallax effect. The range is `-0.3` to `0.3`, with a default of `0.05`. Negative values invert the depth direction. Larger absolute values produce a stronger apparent depth but can introduce artifacts at grazing angles.
+
+**PomMaxSteps:** The maximum number of raymarching iterations used to resolve the parallax offset. Higher values produce more accurate results at grazing angles but increase the per-pixel cost. The range is `4` to `64`, with a default of `16`.
+
 ## Material Preview
 
 The 3D viewport of the material editor allows you to switch the [render mode](../editor/editor-views.md#render-modes) to inspect only specific aspects of the material.

pages/docs/terrain/procedural/procgen-graph-output-vertexcolor.md

@@ -4,7 +4,7 @@ The *Vertex Color Output* node defines what procedurally computed color values g
 
 A [ProcGen graph](procgen-graph-asset.md) can contain multiple vertex color output nodes. Each one represents an independent RGBA layer of vertex color data. They are consumed by the [Procedural Vertex Color Component](procgen-vertex-color-component.md), which applies them to a mesh at runtime.
 
-<!-- ![ProcGen vertex color output node](media/procgen-vertexcolor-output-node.jpg) -->
+<!-- !ProcGen vertex color output node media/procgen-vertexcolor-output-node.jpg -->
 
 ## How It Works
 

pages/docs/terrain/procedural/procgen-vertex-color-component.md

@@ -2,7 +2,7 @@
 
 The *Procedural Vertex Color Component* applies procedurally computed vertex colors to a mesh at runtime. It uses a [ProcGen graph](procgen-graph-asset.md) containing one or more [Vertex Color Output](procgen-graph-output-vertexcolor.md) nodes, and writes the resulting per-vertex RGBA data into a GPU buffer that the mesh's material shader can sample.
 
-<!-- ![Procedural vertex colors applied to a mesh](media/procgen-vertexcolor-component.jpg) -->
+<!-- Procedural vertex colors applied to a mesh media/procgen-vertexcolor-component.jpg -->
 
 This is the vertex-color equivalent of the [Procedural Placement Component](procgen-placement-component.md). It is what connects the graph's vertex color outputs to an actual mesh in the scene.
 

pages/docs/terrain/terrain-overview.md

@@ -12,7 +12,7 @@ A popular method to represent terrain are heightmaps - 2D grayscale images, wher
 
 Vegetation can be created with standard meshes. Using custom [visual shaders](../materials/visual-shaders.md), a basic per-vertex wind animation can be applied.
 
-Additionally, ezEngine has built in support for [Kraut](kraut-overview.md), a tool that allows you to procedurally generate tree meshes.
+Additionally, ezEngine has built in support for [Kraut](kraut-overview.md), a system for procedurally generating tree meshes directly inside the editor.
 
 Finally, there is a system to procedurally place objects, typically plants, around the current player position. This system is currently undocumented, but the [Testing Chambers](../../samples/testing-chambers.md) project contains scenes which show basic usage.