Changing how an existing item, surface, or character looks by editing its texture. This is where everyone should start.

1. Open FModel. Set Archive Directory to your game root (the folder containing OblivionRemastered.exe), UE Version to GAME_UE5_3, and load your .usmap mappings file.
2. Browse the Folders tab to find your texture. Right-click → Save Texture. Always use TGA format, not PNG - TGA preserves all channels including alpha, which PNG discards.
3. Edit the image in Photoshop, GIMP, or Substance. The game uses DirectX normal map format - if you’re working with normal maps, the Y channel is not inverted (unlike OpenGL).
4. Import into your UE project at the exact same folder path as the original. Check FModel to match the original’s Texture Group and Compression Settings.
5. Assign to a chunk. Package. Rename output files with _P suffix. Drop all three files (.pak/.ucas/.utoc) in ~mods.

ffmpeg -i input.png -filter_complex "[0]geq=r='r(X,Y)':g='g(X,Y)':b='b(X,Y)':a='255'" out.png

Making an NNRM in Photoshop

1. Open your Normal, Roughness, and Metallic maps.
2. In the Channels panel of a new document: paste Roughness → Blue · Metallic → Alpha · Normal R → Red · Normal G → Green.
3. Save as .TGA 32-bit - PNG will discard the alpha channel.

NNRM ffmpeg Split Scripts (c0bra5)

Split an NNRM into component images

# Normal XY channels (produces a blueish image - that's correct)
ffmpeg -hide_banner -v error -i "%1" -filter_complex "[0]geq=r='r(X,Y)':g='g(X,Y)':b='255':a='255'" "%~n1_n.png"
# Roughness (from B channel)
ffmpeg -hide_banner -v error -i "%1" -filter_complex "[0]geq=r='b(X,Y)':g='b(X,Y)':b='b(X,Y)':a='255'" "%~n1_r.png"
# Metallic (from Alpha channel)
ffmpeg -hide_banner -v error -i "%1" -filter_complex "[0]geq=r='255':g='255':b='255':a='p(X,Y)'" "%~n1_m.png"

For a model with no normal map detail, create a flat NNRM: set R=128, G=128 (neutral normal), fill B with your roughness value, fill Alpha with your metallic value.

Skin materials use SubsurfaceProfile (SP_SkinBase). Diffuse/BaseColor format: RGB = color, A = emissive mask. Hair textures use the _RAUD suffix multi-channel format - always export TGA from FModel, the alpha channel contains the opacity/strand mask.

The game uses Audiokinetic Wwise for all audio. Sounds are stored as .wem files (Wwise Encoded Media) inside .bnk soundbank containers.

1. Use FModel + retoc to unpack the .wem audio file you want to replace.
2. Convert your replacement audio to .wem format using sound2wem. Alternatively, use older Wwise installer tools; see the RE Modding forum guide.
3. Swap in your audio keeping the exact same filename. Repack with retoc into a _P pak. Drop in ~mods.

Finding a Specific Voice Line

1. In FModel, browse to Localization/String Tables. Find the line you want and copy its event name number (looks like 00047660).
2. Browse to WWise/Event/English. Find the .bnk bank file matching the NPC race and dialogue category.
3. Open that bank in wwiser and navigate the tree to find your number in a CAkSound node. That node’s value is the SOURCE ID - the number matching the corresponding .wem file.
4. Extract that .wem, replace with your converted audio, repack.

Dialogue Timing Without Voice

Placing .mp3 files in the legacy Sound/Voice/ folder matching the vanilla dialogue filename convention controls subtitle display duration, even though no audio plays. The mp3 file duration equals the subtitle display time - useful for localization subtitle syncing.

The game’s files are sealed in the IO Store container format. Pull one out, change it, seal it back. This underlies almost every visual mod.

Extracting with retoc

retoc.exe to-legacy --filter "OblivionRemastered/Content/YourPath/YourFile" ^
  "[GameDir]\Content\Paks" "C:\Output"

Use forward slashes in the filter path. To extract multiple files at once, add multiple --filter arguments.

Editing with UAssetGUI

UAssetGUI needs both the .uasset and .uexp files in the same folder. Set the version dropdown to 5.3. Load your .usmap mappings file via Utils → Import Mappings. If you get “Failed to Parse X Exports”, extract the referenced dependency files alongside the main asset in the same directory structure.

Repacking with retoc

retoc.exe to-zen --version=UE5_3 "OblivionRemastered" "MyMod_P.utoc"

Input directory must be the OblivionRemastered folder (not deeper). This produces all three files (.pak, .ucas, .utoc) at once.

You can combine art assets and form assets in the same retoc folder before packing to produce one single pak for your entire mod.

Making a sword hit harder, armor weigh less, or adding enchantments. Uses xEdit to edit game data records on the Gamebryo side.

Launch xEdit with the correct flags

TES4R64.exe -D:"[GameDir]\Content\Dev\ObvData\Data" -I:"[GameDir]\Content\Dev\ObvData\Oblivion.ini"

1. Let xEdit fully load Oblivion.esm and the DLC files.
2. Find your item inside AltarESPMain.esp. Right-click it → “Copy as new record into…” a new mod file. Never edit the originals directly.
3. Give it a fresh EditorID so it can’t conflict with anything, then edit the numbers in the DATA section - damage, weight, value, enchantments.
4. Add your new .esp to Plugins.txt and test.

Finding Your FormIDs In-Game

Your mod’s load order index determines the first two hex digits of all FormIDs it creates. Formula: (line number in plugins.txt minus the comment lines) → convert to hex. Example: your mod is the 23rd line → index 21 → hex 15 → your FormIDs start with 15XXXXXX. Install the Runtime EditorIDs mod (mods/1331) to surface EditorIDs directly in the console.

Game Settings (GMSTs) via GameSettings Loader

Use the Game Settings Loader (mods/833) to override game settings from a config file without touching ESPs:

[GameSettings]
fJumpHeightMin = 64
fJumpHeightMax = 128
fHealthRegenDelay = 999999

Creating a genuinely new item - your own named, custom-stat weapon or armor - while reusing a model the game already has. No Blender or UE required thanks to TesSyncMapInjector.

1. In xEdit, create your new item record (new EditorID, set your stats). In the model/mesh field, point it at an existing in-game model path you found in FModel.
2. Run the Smart Mapper xEdit script. It reads your ESP and automatically writes a .ini link file to xEdit\SyncMap\.
3. Copy that .ini file to [GameDir]\Content\Dev\ObvData\Data\SyncMap\.
4. Put your .esp in ObvData\Data and add it to Plugins.txt.
5. Critical load order rule: your plugin must appear above AltarDeluxe.esp in Plugins.txt. Below it, new items go invisible or crash on cell entry.

[Meshes]
; DecimalFormID = /Game/path/to/UEasset.UEasset
002350=/Game/Forms/items/armor/BP_DaedricCuirass.BP_DaedricCuirass

1. In the Construction Set, load MagicLoader’s example file (IntTestMod.esp) and click Set As Active File.
2. Duplicate an existing chest or container, give it a new EditorID, say “Yes” to creating a new object. Place it in the world, save, close.
3. Open the mod in xEdit (with all Altar files loaded) and run Haphestia’s Fix and Port Script (fixmod). This fixes the two missing parameters that the Remaster requires but the CS doesn’t add.
4. Run the Smart Mapper xEdit script. Copy the resulting .ini to Data\SyncMap.
5. Run MagicLoader → “Do Magic!” once to register the new cell entries.
6. Enable your esp in Plugins.txt - above AltarDeluxe.esp.

Asset Structure - What You Need to Create

Each armor piece in OBR consists of 7 components. For a mesh replacer you only need to swap the skeletal mesh. For a standalone new item you need all of them:

A - Blender Setup

1. Import SK_HumanoidFull (extracted from FModel via Save Model as PSK) as your body reference mesh. Color body yellow and head red for visual clarity.
2. Import your armor mesh PSK. On PSK import in Blender: set Linear Color, scale 3m, scale factor 0.01.
3. Rename the armature object to Armature in Blender’s Outliner. PSK meshes from FModel carry an extra root bone; this naming tells UE to skip that extra bone on import. Exception: do NOT rename NBO (New Body Options) skeletons - they are already set up correctly.
4. For static meshes (SM_ prefix, like ground models): remove the armature entirely before exporting.

B - Material Slots (Control First-Person Visibility)

C - Weight Painting

1. Parent your clothing mesh to the armature: select mesh, Shift-click armature, Ctrl+P → Object. For NBO armors: first un-parent with Alt+P → Keep Transformations.
2. Transfer weights using the Data Transfer modifier: Source = Humanoid/NBO mesh, Mapping = “Nearest Face Interpolated” → click Generate Data Layers → Apply.
3. Add an Armature modifier - do NOT apply this one.
4. Delete unused vertex groups (use a Blender plugin for bulk cleanup - vanilla body meshes ship with 407 vertex groups). Hand-paint any problem areas in Pose mode.

Blender Sculpt Mode Tips

• Use Sculpt Mode instead of Edit Mode for mesh fitting adjustments - prevents accidental backface selection.
• Grab and Smooth tools are most useful for fine-tuned fitting to the body.
• Enable Backface Culling in Viewport Shading to catch normal direction issues early.

Fixing Blade Mesh Shadow Issues

• Don’t use Merge by Distance on blade edges - it breaks the sharp normals that give blades their edge.
• Fix: in Edit Mode, select the sharp edges → Mark as Sharp (turns blue).
• Or: Mesh → Normals → Average Vectors → Face Area.
• To reset normals entirely: Mesh → Normals → Reset Vectors.

D - FBX Export Settings from Blender

Name skeletal meshes with SK_SetName_PieceName_m convention (_m for male, _f for female variants).

E - Import into UE 5.3.2

1. Replicate the game’s exact directory structure in your UE Content folder. This is non-negotiable - the game resolves paths at runtime.
2. For Skeletal Meshes: assign the correct skeleton on import:
   • Regular clothing/armor → SKEL_HumanoidSkeleton
   • NBO-specific female armor → SKEL_HumanoidFemaleAdd
   • Helmets → usually SKEL_HumanoidSkeleton or HumanoidHeadRig
3. Set Import Normals and Tangents to preserve your custom normals (not Compute Normals).
4. Enable Import Morph Targets if you’re editing head/face meshes.
5. For Static Ground Meshes: set Collision preset to Custom. Enable Allow CPU Access (required for enchantment Niagara VFX on weapons). Set Collision Complexity to “Simple As Complex” and check Customized Collision.

F - Vertex Colors & Body Part Hiding System

Vertex colors on the body mesh control which parts disappear when armor is worn, via material function MF_HideByVertexColorInt3. They must be linear - the game crashes if exported as sRGB.

G - Bitmask Calculator (BP_BDP Body Section Hidden)

1. Extract the item’s BP_BDP blueprint with retoc. Open in UAssetGUI. View → Expand All. Find MaleBodySectionHidden and FemaleBodySectionHidden. Add them if not present (add as 0 first, save, then change).
2. Copy the current number into Windows Calculator → Programmer mode → Bit Toggling Keyboard.
3. Using the body part color table above, set each bit to 1 (hidden) or 0 (visible).
4. Copy the resulting number back into UAssetGUI. Save. Repack. Test.

H - Materials in UE 5.3.2

You cannot create fully custom materials from scratch in UE - they crash on load. You can only inherit from vanilla base materials. The authoritative workflow from c0bra5:

1. Pick a MIC from the game (inspect it in FModel → Export Properties JSON to see its parent chain).
2. Create a new material in your UE project at the exact same path as the vanilla parent (e.g. /Game/Art/Character/Imperial/MIC_HumanUnderwear_M). Make it inherit from M_Base_Char.
3. Create a new MIC (the location doesn’t matter) inheriting from that stub in step 2. Set up your textures only in this new MIC.
4. Files to include in your mod pak: your own MICs + the skeletal mesh + your textures. Everything else (stubs, vanilla materials) stays out of the chunk - it’s reference-only.

I - BP_BDP Blueprint Parent Chains

Your armor blueprint must inherit from the correct parent chain. Create dummy parent blueprints in Dev/clothing/GenericChild/ - they just need to exist with no content. Weapons do NOT require BDP blueprints.

J - Ground Models (GND Assets)

When armor is dropped on the ground, it uses a separate static mesh (SM_ prefix, _gnd suffix convention). Where the GND reference is declared varies - Virtuos was inconsistent. Check both the main form asset (e.g. EbonyCuirass.uasset) and the BP_ form. To add a GND reference via UAssetGUI, add a NewWorldModels ArrayProperty of SoftObjectProperty to the BP form, then View → Recalculate Nodes. GND meshes must have proper collision or they fall through the floor. Object Channels must all be set; Complex Collision set to Default.

K - Forms with C.A.F.E., ESP, SyncMap & Packaging

1. Use C.A.F.E. (mods/4891) to create armor forms. The form name must match the name in the asset path exactly.
2. Create your ESP in xEdit with item records. Run Smart Mapper to generate Data\SyncMap\YourMod.ini.
3. Place your ESP above AltarDeluxe.esp in Plugins.txt.

Additional Field Notes

• Eye color editing is possible (discovered by _trungus) - method still being fully documented as of mid-2025. Check the OBR modding Discord #research-modeling for the current workflow.
• Amulet biped slot preserves hair and ears - useful for items like head accessories or circlets that shouldn’t hide hair. Note the mesh will be positioned for the neck, so clipping adjustments may be needed.
• Tail biped slot makes armor invisible regardless of BDP settings - don’t use it for regular armor.
• Weapons do NOT require BDP blueprints - they are not assigned to body parts. Only armor/clothing needs them.
• Vertex weight limits: too many bones deforming the same area produces warped/jagged edges. Delete unused vertex groups. Body meshes ship with 407 vertex groups - use a Blender plugin for bulk cleanup.

Beast Race Armor Compatibility

• Import all skeletal meshes with SKEL_HumanoidSkeleton. Never include the skeleton in your pak chunk.
• Never include physics assets - delete them from your project before packaging.
• Khajiit material slot order must be preserved - procedural overlays depend on it.
• Wrong skeleton assignment = “origami” deformed character model in-game.

Override Material via Blueprint (No Mesh Edit)

1. Extract the item’s BP_BDP with retoc. Open in UAssetGUI → Import Data tab.
2. In the bottom empty row, add: ClassPackage = Script/CoreUObject · ClassName = Package · OuterIndex = 0 · ObjectName = full game path of your material · BImportOptional = False. Click away and back to make it stick. A new empty row appears below.
3. Fill the new row: ClassPackage = /Script/Engine · ClassName = MaterialInstanceConstant · OuterIndex = negative row number from step 2 · ObjectName = material name only.
4. Go to Export Data tab → find the ChaosClothComponent (or appropriate mesh component) → look for or add OverrideMaterials ArrayProperty of ObjectProperty. Inside it, map slot numbers to your import rows.
5. Save → repack with retoc → test.

JsonAsAsset (Import Vanilla Materials)

1. Install the JAA plugin into Plugins/JsonAsAsset in your Altar project. Enable, restart, configure the export directory and mappings file path in plugin settings. Launch j0.dev.exe.
2. In FModel, right-click a material → Export Properties (.json). Keep the export path short with no spaces, close to the root drive (e.g. C:\FModelExports).
3. In UE, click the JAA plugin button → select the JSON → wait. Enable the Stubs checkbox (new in 1.4.1) for crash-free import of any material without a pre-made material store.
4. MIC parents are not automatically assigned in 1.4.1 - set the parent manually after import. If the imported material is missing layers (the MIC Layers tab), edit that material in UAssetGUI instead - JAA doesn’t import the Layers tab.
5. If JAA isn’t working: close FModel before running JAA; restart UE and re-check plugin settings.

Transparent / Masked Materials

Custom Inventory Icons

1. In UE: create folder Content/Art/UI/Icons/Dynamic_Icons/menus/Icons/armor/YourFolderName/
2. Import your 256×256 PNG. In UE, prefix it with T_ (e.g. T_MyCuirass). Without the prefix, the game won’t detect the asset.
3. In xEdit, set the Icon Image path to: Art/UI/Icons/.../YourFolderName/MyCuirass.dds - with .dds at the end even though there’s no .dds file. Do NOT include the T_ prefix in the xEdit path.

Blueprint Behavior Mods (ModActor Entry Point)

1. Create Content\Mods\YourModName_P\ in your UE project. The folder name must match your final pak filenames exactly.
2. Create a Blueprint of type Actor and name it exactly ModActor. UE4SS BPModLoaderMod auto-discovers and injects this on game load.
3. Add a Widget Blueprint (WBP_ModHud) as your mod’s UI layer. In ModActor’s Event Graph, on Event BeginPlay: Create Widget → Add to Viewport. This persists across level changes.
4. Use Event Tick + Was Input Key Just Pressed on the ModActor (not on a hidden widget - hidden widgets don’t tick) for keypress detection.
5. Save mod data using SaveGame to slot "Mods/YourModName" (not the root, to prevent crashes when the mod is removed).
6. Package and place files in Paks\LogicMods\YourModName_P\.

UE Editor Steps (Apply Cloth Physics)

1. Import your cloth mesh separately from the armor body. They’ll be re-attached via blueprints.
2. Open the skeletal mesh → right-click the section to simulate → Create Clothing Data from Section. Name the asset, leave Physics Asset as None for now.
3. Right-click again → Apply Clothing Data.
4. Click Activate Cloth Paint: white = simulated (moves freely), black = anchored (fixed to skeleton). Top edge = black, bottom hangs free.
5. Tune ClothConfigs for physics behavior: stiffness, damping, gravity scale. Reference: UE cloth painting tutorial.
6. Right-click mesh → Create Physics Asset. Name it PA_YourMod_Cloak.
7. Open the Physics Asset → replace auto-generated capsules with hand-placed ones on the bones that matter. Set all capsule Physics Type to Kinematic.
8. In the clothing config, assign your physics asset.

Physics Proxy Mesh

A low-poly duplicate mesh called “PhysicsProxy” is often included in OBR meshes. Physics is calculated on the low-poly version and then interpolated to the actual mesh. If your armor doesn’t need cloth physics: right-click the PhysicsProxy section in LOD 0 → Disable. Or delete the slot entirely. A material assigned to the proxy causes z-fighting and clipping artifacts.

Blueprint Setup for Cuirass + Cape

1. Create Content/Mods/YourName/. Folder name must match pak filenames exactly.
2. Create a blueprint named exactly ModActor (parent: Actor). UE4SS looks for this specific name.
3. Create dummy parent blueprints for your armor type (see Lesson 7 parent chain table).
4. Create your main blueprint (parent = deepest appropriate dummy). Set Male Mesh and Female Mesh to the armor body mesh (without cloth). Configure Material Slots Hidden In First Person.
5. Add two Skeletal Mesh components as children of Root (one male cape, one female cape).
6. Event graph: Event BeginPlay → Branch → Get Female Mesh → Is Valid Soft Object Reference → Set Leader Pose Component → Set Hidden In Game (male cape, check Hidden). Compile.
7. Assign blueprint + ModActor to a different chunk number from your mesh assets. Package. Drop into Paks\LogicMods\YourName\.
8. In UAssetGUI, update the BP_BDP path in your biped model form to point to your new blueprint.

Standalone Capes (Amulet Slot)

Route standalone capes through the amulet slot only - amulets are the only item type that accepts physics meshes directly without the CCA issue. Blueprint parent: VAmuletModularBodyPart. In xEdit, ensure the item uses the Amulet biped flag. Use the Hair mesh slot as an alternative if you don’t mind the workaround. Performance: cloth simulation is CPU-bound and varies significantly between systems. Use a proxy mesh (simplified low-poly version) for high-poly capes: proxy mesh guide.

Step 1 - Import SKEL_HumanoidSkeleton via JsonAsAsset (Critical First Step)

Use JAA 1.3.7 or newer. This imports the skeleton with virtual bones (IK targets) intact. Virtual bones cannot be recovered from a PSK export - JAA is the only reliable method. The correct skeleton has 378–379 bones (without sockets exported as bones).

Step 2 - Export SK_HumanoidFull from FModel Correctly

In FModel: Settings → Models → Socket Format → “Don’t Export Bone Sockets”. This prevents sockets from being exported as bones, which adds ~28 extra bones and breaks all IK at runtime.

Step 3 - Fix the Extra Root Bone in Blender

The PSK importer adds a root bone named after the mesh file (e.g. SK_HumanoidFull). Fix: rename the armature object to Armature in Blender’s Outliner. This makes UE skip the extra root, and the bone index order matches correctly.

Retargeting Animations from Other Games

Any animation from any source (Elden Ring, The Witcher 3, Skyrim, Paragon, stock UE Mannequin, Mixamo, CMU mocap library, Fab marketplace free tier) can be retargeted to the OBR skeleton.

Recommended UE 5.4 bridge method (krasuepisac):

1. In your 5.3.2 modding project, migrate the OBR skeleton to a UE 5.4 project via Content → Migrate.
2. In 5.4: create an IK Rig and IK Retargeter for the OBR skeleton. UE 5.4’s retargeting tools are 1–3 clicks vs. building an entire IK rig manually in 5.3.2.
3. Retarget your source animations onto the OBR skeleton in 5.4. Export the retargeted animations as FBX.
4. Re-import FBX into your 5.3.2 modding project. (Assets can’t be migrated back from 5.4 to 5.3.2, but FBX as an intermediate works perfectly.)

For Skyrim animations specifically: import NIF animations into Blender using the NIF importer plugin, export as FBX, then use the retargeter method above.

Animation Notifies - Combat Combo Chaining

Simply importing notifies via JAA is often insufficient - they may need to be added manually. For combat combos to chain correctly, both of the following notifies are required:

BP_ActionNotifyState_ChainWindow
  Begin Action Event Tag: ActionEvent.Attack.ChainingWindow.Enter
  End Action Event Tag:   ActionEvent.Attack.ChainingWindow.Exit

VAnimNotify_ActionNotifyState
  Begin Action Event Tag: ActionEvent.Attack.InputWindow.Enter
  (no End tag)

Removing either one breaks chaining. Confirmed by kei7855 on their shortsword animation replacer mod (mods/2489).

For block to interrupt an attack mid-swing, the start time of this notify must fall within both VAnim_ActionMeleeHitWindow and VAnimNotifyState_ImpactSystem:

BP_ActionNotifyState_TagContainer
  Tags To Transmit: [Input.Action.Combat.Block]
  BeginActionEventTag: ActionEvent.Attack.CancelTags.Add
  EndActionEventTag:   ActionEvent.Attack.CancelTags.Remove

Replacing Locomotion Blendspaces Persistently

Injecting a blendspace via AnimSet gets reset when the player equips or unequips a weapon, because the game stores all valid blendspaces in a TMap keyed by GameplayTags. Solution (krasuepisac’s discovery):

1. Find the TMap that maps GameplayTags to blendspaces inside the AnimBP.
2. Swap the entry for the relevant tag directly. Tag the actor after modification to avoid re-applying every frame.
3. This persists through cell transitions - the player actor reference survives cell loads (unusual for UE games but intentional here).

Velocity reference values: Walk ~155 · Run (blendspace activates) ~509. Sprint uses a plain AnimSequence, not a blendspace. Root motion appears fully disabled - everything is root-locked; set root lock to zero on import.

Playing Animations at Runtime (Lua/Blueprint)

Triggering PlayAnimation from Lua works for the first play, but after the animation completes the character stops playing all normal animations permanently (frozen on last frame or T-pose). Use PlayMontage instead - montages blend in and out automatically via UE’s montage system and return the character to ABP-controlled state after finishing. The FullBody animation slot overwrites all other blending when active - use it for full-character override animations like emotes or cutscene poses.

ABP Architecture - Template & Linked Layers

The game uses a template ABP with linked layer instances. Each animation category (combat, idle, locomotion) is a separate linked layer instance within the template. Target the correct layer for the animation type you are replacing - this is why some replacements work and others break unexpectedly.

StrideWarping (standard UE plugin node) handles foot placement based on LocomotionSpeed. Foot lock positions only update when the character starts or stops moving.

Actor Persistence Across Cell Loads

• The player actor reference persists through cell transitions (unusual for UE games). GameplayTags on the player also persist.
• NPC actor references are completely destroyed on any cell load. Store persistent NPC mod data in a widget or custom UObject with a reference loop.

Mesh Merging & Morph Targets

UE’s Merge Meshes system combines all equipped armor pieces into one SkeletalMesh at runtime. This process destroys morph targets. NBO avoids this by using bone scaling instead - bone scale survives merging.

Gamebryo Animation (Legacy)

PlayGroup and PickIdle execute on the Gamebryo side but have no visual effect since rendering moved to UE5. AI Package idles still work. NPCs can get stuck in triggered idles - cast a spell on the NPC to break the animation lock.

Reference Mods & Resources

• miken1ke Blender rig and guide (mods/2069) - community standard rig, includes articles
• kei7855 shortsword animation mod (mods/2489) - reference for notify setup
• Leaning disable mod (mods/2570) - disables forward-lean locomotion behavior
• Alpakit for UE 5.3.2 - OBR-compatible fork; enables one-click auto-deploy of BP mods
• Jake Alaimo live mocap - live mocap modded into OBR, reference implementation

Architecture

• Every voice line has its own AnimSequence stored in Content/Art/Animation/Humanoid/Facial. Warning: the sheer number of files in this folder will freeze FModel on browse - navigate by known path instead.
• Audio and face animation play independently - they start at the same time with no synchronization tracking. This means replacing either leaves the other running unchanged.
• Mouth/speech sync uses a UE function called speech2face (procedural, no per-frame data).
• TABP_FacialPose is the facial pose AnimBP.

Setup for Custom Head Facial Animation

1. Enable the RigLogic, MetaHuman, and MetaHuman Identity plugins in your Altar UE project.
2. Attach the appropriate .dna file to your face SkeletalMesh asset. DNA files are NOT standard .uasset files - they require CUE4Parse to extract from the game:

foreach (var kv in provider.Files) {
    if (kv.Key.EndsWith(".dna")) {
        var outPath = Path.Combine("extracted", Path.GetFileName(kv.Key));
        await using var stream = provider.SaveAsset(kv.Value,
            new FileStream(outPath, FileMode.Create));
    }
}

3. Create and reference a dummy ABP_HeadPostProcess blueprint. This is required for the DNA to drive the facial bones.

Community DNA Files

WSDog extracted and publicly shared DNA files for all base races and named NPCs:

• Community DNA files (mods/2592) - base races and named NPCs
• Guide: Nexus mods/625

Generating New Facial Animations from Audio (Audio2Face Workflow)

1. Use NVIDIA Audio2Face to generate blendshape/shape key animation from your audio file.
2. Pipe through MetaHuman Live Link into UE 5.3.2. Record the result as a UE AnimSequence.
3. OBR face curves share the exact same names as MetaHuman curves - they map directly with no translation needed.
4. Replace the existing AnimSequence at the matching path in Content/Art/Animation/Humanoid/Facial.
5. MetaHuman plugin supports batch processing for automating generation from multiple audio files at once.

Audio-Anim Sync for Localization

Since audio and face animation play independently, to fix out-of-sync dubbed audio (where the new audio is longer than the original): replace the AnimSequence at the correct path with a new one timed to match your audio duration.

The game uses Audiokinetic Wwise 2023.1.8.8601.3258 for all audio. UE’s built-in audio system has only two dummy assets (DummySoundClass, DummySoundCue).

What Works Without Full Wwise Integration

• Sound replacement: swap existing .wem files inside a pak (see Lesson 2)
• Posting vanilla Wwise events from Blueprints: use the VAudioHandlers subsystem and BPF_PostEvent (or PostEventAtLocation for spatial audio)
• Turning vanilla audio events on/off from Blueprints using vanilla AkAudioEvent class defaults

Full Wwise Integration Setup

1. Install Wwise from the Audiokinetic Launcher - select exactly the version above.
2. In your Altar project folder, delete the existing Wwise and WwiseNiagara plugin folders.
3. Use the Launcher: Unreal Engine → Integrate Wwise into Project.
4. Fix the compile error in Source/Altar/Public/VAltarAkPortalComponent.h: update the include to "AkAcousticPortal.h" and parent class to public UAkPortalComponent (the Altar project stubs reference the outdated name AkPortalComponent).
5. Build via Visual Studio. Name the Wwise project Altar and place it at C:\Altar-main\WwiseAltar\ to match paths in the game’s DefaultEngine.ini (not strictly required but simplifies cross-referencing).

External Sources - Custom .wem Files Without Rebuilding Soundbanks

External Sources allow specifying which .wem file Wwise loads at runtime without rebuilding soundbanks. This enables one framework mod to handle the Wwise plumbing while other mods simply ship .wem files.

Enable External Sources by overriding the game’s DefaultEngine.ini from your mod pak:

[Audio]
WwiseFileHandlerModuleName=WwiseSimpleExternalSource

Required Setup for External Sources

1. Create a DataTable using the External Source cookie struct (provided by Wwise).
2. Populate with: cookie value, media ID, codec ID, media name (filename of your .wem).
3. Override DefaultEngine.ini to enable WwiseSimpleExternalSource.
4. Include your .wem file in the pak at the correct staging path.
5. Ensure your mod actor has a packaged static mesh component with a mesh assigned.

Getting a Free Non-Commercial Wwise License

Creating new Wwise audio events (new sound forms in the ESP with new UE audio) requires Wwise’s authoring tools to generate new .bnk soundbank files. Getting a free non-commercial license requires a manual review by Audiokinetic staff - fill out the form at audiokinetic.com/en/pricing honestly.

Current Status Table (mid-2025 community research)

Grass & Foliage

All visible grass is part of generated UE maps - painted onto landscape materials during UE map generation. TESGrass records in the CS have no in-game effect. Adding custom trees and grass:

• TESSyncMapInjector approach (most ergonomic): link a UE static mesh to a TES mesh record in the CS and place it using standard CS workflows. Demonstrated for water meshes (mods/4874) and trees (mods/4740).
• Blueprint/Lua spawn approach: a custom Blueprint spawns a mesh at dynamic coordinates from Lua. Requires manual coordinate input.
• Mad’s placement system (minuteready): spray mesh instances organically by running around in-game using Mad’s “rapid spell” + “add instance on X” system, writing positions to a text file, then importing them. Labor-intensive but gives natural placement feel.
• Removing existing UE grass: edit each .umap via UAssetGUI to remove grass foliage actors (tedious, version-sensitive), or hook the grass Blueprint creation in Lua and destroy instances on spawn (theoretical).

Heightmap

The old Gamebryo heightmap still exists in game files but does NOT drive the visible terrain. The UE side has its own heightmap. No clean extraction or re-injection workflow exists yet.

Using surf / blenderumap3: importing .umap files via surf/blenderumap3 confirms the layer-per-category structure - exporting only the umap for a specific area returns a single tree mesh, not the full scene. The layers need to be loaded together to reconstruct the full environment. Tools: search for BlenderUMap2 and surf in the UE modding community.

The “All of Tamriel” heightmap from Nexus (Skyrim mods/52675) has been discussed as a source for adding adjacent provinces. Key note from grimlock_arts: TES game heightmap data is deceptively low detail - the games rely heavily on placed rock models pushed into the ground to create the impression of complex terrain. The raw heightmap is just a flat base layer.

Heightmap tools referenced by the community:

• TESAnnwyn - CK heightmap import/export for the Gamebryo side (legacy, won’t affect UE terrain)
• Aerialod - heightmap viewer; recommended settings: scale 2.5, adjust lighting for shadow detail
• ue4parse / UnrealStuff landscape tools - for reading UE landscape data

Map Borders & Open Space

Map borders can be disabled. A large open stretch of land runs from roughly 1/3 to 1/2 the size of the main game map, fully walkable and tree-free, extending all the way to the ocean. No water in the way. This is the most viable space for exterior expansion content as of mid-2025.

Navmesh

Navmesh editing is not currently possible from the modder side. NPCs cannot be directed reliably in new areas without navmesh. Workaround: add a small gatehouse cell or confined space to prevent NPCs from wandering beyond intended areas.

Nanite & LODs

OBR uses Nanite for static mesh geometry, which handles LODs automatically. You do not need to create LOD meshes or configure LOD settings. There is no DynDOLOD equivalent. FModel exports only the fallback mesh (low-poly version for Lumen), not the full Nanite detail. For full extraction use c0bra5’s simple-nanite-parser (Python-based, exports to GLTF with vertex colors).

CK–UE Terrain Height Mismatch Workaround

When building outside the vanilla map border, CK terrain height and UE terrain height diverge. Workaround (nafnaf_95): work one cell at a time, build at CK-default height, then select all objects and shift them vertically until they sit correctly on the UE terrain surface. Tedious but workable for exterior static object placement.

Trees & SpeedTree

Trees are handled via SpeedTree assets with built-in wind animation, baked into per-cell UE umap files with foliage instancers. Map file names are hashed making systematic modification very difficult. Adding new trees as individual Blueprint actors works but incurs significant performance cost. The SpeedTree SDK (required for full authoring) has enterprise-only commercial licensing (~$100k+).

New interior cells work via MagicLoader. The tool modifies the CellsToMapPath DataTable with new entries that map Gamebryo cells to UE map files, making the game load the correct UE level when a cell is entered.

1. In the Construction Set, load MagicLoader’s example file (IntTestMod.esp) → Set As Active File.
2. In Cell view, create a new interior cell. Build the room using existing tileset pieces. Place furniture, containers, lights. Add a door and use Door Teleport to connect it to an exterior location.
3. Save the esp. Open in xEdit (all Altar files loaded) and run Haphestia’s Fix and Port Script (fixmod).
4. Run the Smart Mapper xEdit script. Copy the resulting .ini to Data\SyncMap.
5. Run MagicPatcher to build the string table patch .json for room names and door labels.
6. Run MagicLoader → “Do Magic!” once.
7. Enable your esp in Plugins.txt - above AltarDeluxe.esp.

MagicLoader Known Bug (Fixed in v1.1)

An early version of the Fix and Port Script overwrote FULL name fields on existing records, causing custom items and locations to lose their names. This was fixed in v1.1: “Fixes clearing IDs on newly added records by mistake.”

1. In FModel, find the base creature blueprint you want to modify. Note which blueprints it references.
2. Trace references upward - those BPs reference their own parents. You’ll find a hierarchy of AI, animation, skeleton, etc.
3. Duplicate only as many levels as you need. Stop at the level where you want to diverge. To replace mesh and textures while keeping vanilla AI and animations: duplicate only 2–3 levels.
4. In your duplicated top-level blueprint, swap in your new mesh, textures, or behavior values.
5. Create the ESP form for your new creature in xEdit. SyncMap it via TesSyncMapInjector. Package blueprints and form.

Adding New NPCs

1. Create the NPC record in CS or xEdit. Use an existing vanilla race for reliable results - non-vanilla races default to Imperial appearance at runtime if the UE form can’t be found.
2. For the UE side: clone an NPC form file from FModel that matches the intended race/gender.
3. Edit the cloned form in UAssetGUI to change name references.
4. Register in TesSyncMapInjector.
5. Place the NPC in a cell via CS.

Custom Races

Custom races require:

1. An ESP with the new race record.
2. A UE race form blueprint at /Game/Forms/actors/race/CustomRace.uasset.
3. Entries in the AllRaceModifications data table (edit via JsonAsAsset or retoc + UAssetGUI).
4. Phenotype and hair tables updated to include the race.

Adding fully custom playable races with all CharGen sliders is still in research as of mid-2026. Non-playable custom races (for NPCs) work when given a vanilla voice type. The race menu UI reads from UE-side data tables.

Hair Modding

Hair phenotype files live at /Game/Dev/Phenotypes/Hair/ as data tables listing available hairstyles per race.

1. Extract the existing HP_[Race]_HR_[StyleName].uasset file using retoc.
2. Inspect with UAssetGUI or JsonAsAsset.
3. Create your new hair mesh in UE project.
4. Add an entry to the race’s phenotype hair data table.
5. Use RMU (Race Menu Utility) for runtime loading: rmu set hair /Game/Dev/Phenotypes/Hair/HP_RaceName_HR_HairName.HP_RaceName_HR_HairName

Hair texture format: use the _RAUD suffix multi-channel format. Always export as TGA from FModel - the alpha channel contains the opacity/strand mask, critical for proper hair card rendering.

Facial animation compatibility: modifying head meshes (including head-attached hair) can break facial lip-sync if the mesh topology changes significantly. Blinking and face morphs may continue to work even when lip-sync breaks.

Strand hair: true strand (groom) hair via UE5’s Groom system has been partially achieved but the full binding pipeline is not documented. Hair card replacement is the stable workflow.

Text / Subtitle Changes

ESP-side text: changing dialogue text in CS/xEdit works for most dialogue. Display names use the LOC_FN prefix system - forward AltarESPMain changes or names break. Localization files: some UI strings are in UE localization tables inside the PAK and require editing the localization .uasset files. Note: only one mod’s localization table wins in case of PAK conflict.

Reusing Existing Voice Lines for New NPCs

1. Create the dialogue topic in your ESP.
2. Use TesSyncMapInjector to map your new dialogue FormID to an existing dialogue form blueprint path. Format: TOPICTYPE_espname_FormID. Example:

   GREETING_MyMod_00000ED6=/Game/Forms/miscellaneous/dialog/GREETING_Someactor_000479e1.GREETING_Someactor_000479e1

3. The NPC’s voice type (set in the race ESP record) must match the target dialogue form’s voice set. Using a non-vanilla race? Set the race to a vanilla voice type to prevent crashes.

Subtitle Display Duration Without Voice

Placing .mp3 files in the legacy Sound/Voice/ folder matching the vanilla dialogue filename convention controls subtitle display duration, even though no actual audio plays. The mp3 file’s duration equals the subtitle display time - useful for subtitle-only localization mods.

Lip Sync

Lip sync is handled by UE animation assets linked to dialogue forms. Current workaround: use an existing dialogue form that has entries for multiple races - the game will attempt to use the matching race’s lip sync animation. Fully custom voiced dialogue (new audio + new lip sync) is not yet solved end-to-end - the WEM format is figured out but BNK generation is the blocker.