Unreal Engine 5 assets in Cyberpunk 2077: research

Status: research. Asked for by the owner on 2026-10-25 (written in a REDnode session, moved here the same day). Nothing is built. This work belongs to EDGEfab: mainly its phase F8, with U4 in F7, in the build plan. The goal is to bring free and royalty-free Unreal Engine assets into the game. This page asks how feasible it is to take Unreal Engine 5.x assets (props, NPCs, their materials, rigs and animations) into Cyberpunk 2077 through the EDGE tools, how much work it is, and what it costs in quality. Facts not checked against the game or the tools are marked unverified.

The short answer

Props are the strong case: high feasibility and a clear path to automation. NPCs work if the mesh is moved onto Cyberpunk’s body rig and keeps the game’s animations. Talking faces and new skeletons are where it gets expensive.

Rights come first

Converting is the easy part. What may be shipped in a mod is set by each asset’s license, so the EDGE tools should ask about it and record it at import.

So the input is always the UE editor with the project open, never a cooked .pak/.utoc. That also helps the work: the editor exports clean FBX, keeps the source textures and can bake materials, so there is no need to read Epic’s cooked formats.

The pipeline

UE 5.x editor ──export──► FBX + textures + manifest ──► Blender (headless) ──► glTF ──► REDbridge (WolvenKit) ──► .mesh .xbm .mi .ent .app .anims ──► archive
   (UE Python:              (units, axes,                 (rig moves,                     (import over a                    │
    export, bake,            names, LODs)                  weights, LODs)                  template file)                   ▼
    retarget)                                                                                                    EDGEbuilder places it,
                                                                                                                 REDnode swaps it in

Driving Unreal: headless and MCP

Unreal can be driven like Blender, in two ways. They match the two layers EDGEfab uses for Blender (build plan).

Unverified until the U0 spike: whether Merge Actors baking runs headless (it probably needs a renderer, so no -nullrhi), and whether FBX export works in a commandlet run.

Meshes

What WolvenKit’s importer asks for (its wiki, checked 2026-10-25):

Also needed, from general knowledge, unverified for Cyberpunk in detail:

Materials

A UE material is a shader graph. Cyberpunk materials are instances of fixed templates. No general translation exists, so there are two routes:

Special cases:

Normal maps: UE uses the DirectX convention (green down). Which one Cyberpunk’s importer expects is unverified. Check with one test texture and flip the green channel if needed.

Rigs: the decision that sets the cost

Cyberpunk’s NPCs run on a handful of body rigs (man, woman, big man, child and so on), each with its own facial rig. Its animations, animation graphs, AI behaviours, workspots and scenes all assume those rigs. That gives two paths:

Path A is the realistic one for “NPCs primarily”. Automating it is the largest part of the work:

1. A bone map per source skeleton: UE5 Mannequin (Manny, Quinn), MetaHuman body, and generic Mixamo-style. Cyberpunk’s bone names and rest poses come from its .rig files (read with REDbridge).
2. Fitting: scale and pose the source onto the target rig’s bind pose. Mannequin and MetaHuman bodies are close to human proportions, so this mostly works. The rest needs a person.
3. Weights: copy from the matching game body, then let the source’s own weights win where they agree (hands, fingers). Clamp to 8, normalize.
4. Split into the parts a game appearance expects (head, torso, arms, legs, feet, hair) where the asset allows it. One whole-body part also works, but loses mixing with game clothes.

Faces

The face is the weak point.

Recommendation: start with the first or second option. Treat speaking UE faces as research.

Animations

Doing the retarget inside UE is the key choice: its IK Retargeter is better than Blender’s options and is scriptable. The wiki warns that arm bones often don’t carry over cleanly between rigs, so expect a check pass.

What EDGEfab would build

One step at a time, each with an in-game test. In the build plan, U0 runs in F0 as a check, U1 to U3 are F8, U4 is part of F7, and U5 stays research. U1 reuses F1’s prop path (REDbridge import, collision, LODs, materials from EDGEmat), and U3 reuses F5 and F6’s character path, so both are smaller by then.

U0 to U2 are low risk and give the most value per hour. U3 is where the time goes. U5 should wait until the rest proves worth it.

Tradeoffs in one place

Sources

• WolvenKit wiki, Import/Export: Mesh: import rules.
• RED Modding wiki: Poses/Animations: make your own, Retargeting poses and animations, Replace player clothes with an NPC garment (weight transfer), Fixing eye clipping by replacing facial rigs, Other facial expressions, Play animations with workspots.
• Epic: Unreal MCP in Unreal Editor (UE 5.8); Scripting the Unreal Editor using Python (-run=pythonscript).
• Epic: Fab launch (Standard License, any engine); Merging actors; UE-341753 (Substrate baking).
• CG Channel, June 2025: MetaHumans in other engines.
• Simplygon: material baking in UE5: nodes that bake black.