A plugin that allow reading and writing of ALAMO-Engine model(.alo) and animation(.ala) files.
Specifically designed to work with Empire at War: Forces of Corruption.
Works with 3.6
Added Support for automatic creation of proxy bones to make the process quicker mainly for damage_emitters for proxies
Tested with Blender 2.82. Download the repository. Put the "io_alamo_tools" folder into "Blender 2.82/2.82/scripts/addons/".
The plugin has to be enabled in Blender. See the official documentation.
If everything worked the Import and Export menus now list options for .ALO and .ALA files.
The exporter supports the .alo model format used in both Empire at War and it's addon Forces of Corruption.
The animation format differs between the base game and the addon. Only the latter is supported.
If necessary animations can be converted with an external tool.
When exporting or importing it's a good idea to open the Blender console.
Warnings and errors are displayed here.
Common issues when exporting include missing UVs or vertex weights when using shaders that need them and not assigning a material.
Every object should remain without an object level transformation, so the origin should remain at the center without rotation
and scaling.
Object transforms will be ignored when exporting. To move an object to a specific location it has to be attached to a bone.
This is done by using a child of constraint.
To automate this process the 'Create Constraint Bone' button can be used. An active armature has to be selected and the selected
object must not have a child of constraint. This will create a new bone in the active skeleton at using the transform of the object. The object will be constrained to the bone and the transform will be reset. As a result the object should remain at the same position and rotation.
Shadow meshes are used ingame to render shadows using shadow volumes.
A mesh is considered a shadow mesh when it uses the corresponding shader: 'MeshShadowVolume.fx' or 'RSkinShadowVolume.fx'.
Shadow volumes have strict requirements. They need to be water tight, otherwise artifacts will occur.
Furthermore the exporter requires the mesh to
be non-manifold.
When trying to export a non manifold shadow mesh the exporter will fail
with an appropriate error message and automatically select the problematic geometry.
The problematic geometry can be manually selected using a Blender
function.
Note that the exporter is stricter than the game when it comes to shadow meshes.
That means imported models might not be exportable without manually fixing the shadow mesh.
However it also means that an exported shadow mesh should not be able to cause artifacts ingame.
The sidebar(default hotkey: 'N') offers an ALAMO properties option. This lists the file format specific properties of the active object.
Validate:
- Check for any problems that would cause an export to fail.
Object tools (Mesh in object-mode):
- HasCollision: treated as collider ingame
- Hidden: invisible ingame
Armature Settings (always avaible):
- ActiveSkeleton: Files can only contain a single skeleton. Choose the skeleton that is used when exporting
Bone Tools (Bone in edit-mode):
- billboardMode: Sets the billboard mode. Can only be set on individually-selected bones.
- Visible: Visibility of attached object
- EnableProxy: bone is a proxy to spawn effects ingame, enables additional options:
- proxyIsHidden: flag that determines if the proxy is initially hidden
- altDecreaseStayHidden: prevents proxies to become visible when the alt level decreases
- ProxyName: name of the effect to be attached to the proxy. Can only be set on individually-selected bones.
Bone properties (Bone in pose-mode):
- proxyIsHiddenAnimation: animated visibility of the proxy
- Action End Frames: per action, length of the animation
Debug:
- Unmodified original UI
- Any clicks on the sidebar, but not on an active control, will be treated as a click in the 3d view. This can cause you to lose your selection.
- On validation, errors only pop up briefly, and warnings don't pop up at all. Recommend opening an Info panel when validating.
Section in the Material Properties tab dedicated to shader settings, including textures.
The shader to be used ingame can be selected from the shaderList. The avaible options change depending on the shader.
Most options can be left at default values, however textures should be chosen.
To do this load the texture into Blender as an image. The texture options offer an dropdown menu with all avaible images.
Note that only the texture name is written to the file, the texture itself must be placed in the appropriate
mod directory in order to be found by the game.
When exporting an animation the current animation from the 3D-view is exported.
Multiple animations can be stored in Blender using the action editor.
Animations can be exported in bulk by checking the 'Export Animations' property when exporting a model. This will export every
action into a separate animation file.
Scaling in animations is unsupported at the moment.
All shader settings are stored in 'settings.py'.
The 'material_parameter_dict' contains a shader name as a key. The corresponding item is a list of strings.
Every string is a shader parameter. Every paramater name needs to match the shaders HLSL parameter name exactly.
If a new parameter is used that is not yet used by another shader it has to be added to Blenders material properties.
This is done in 'register()' function in 'init.py'. Adding the property is a single line of code, for reference look at the
existing code and the Blender documentation.
Every shader also needs a vertex format. This tells the engine what vertex data to pass to the vertex shader. This is implemented with a second dictionary called 'vertex_format_dict', with the key being the shader name and the item the formats name as a string.
If a shader uses normal mapping its name has to be added to the 'bumpMappingList' list.
Breakdown of the Alamo Object File Format.
Breakdown of the Alamo Animation File Format.