import-carla-ue58-walker

Imports skinned FBX pedestrians into CARLA on UE 5.8 as spawnable, animating walkers.

3|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/carla-simulator/carla-agentic-tools --skill import-carla-ue58-walker-carla-simulator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: import-carla-ue58-walker
Source: https://github.com/carla-simulator/carla-agentic-tools/tree/main/skills/ue58/import-carla-ue58-walker
Command: npx skills add https://github.com/carla-simulator/carla-agentic-tools --skill import-carla-ue58-walker-carla-simulator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Adding a custom pedestrian to CARLA on Unreal Engine 5.8 requires three coordinated artefacts — a SkeletalMesh bound to CARLA's shared pedestrian skeleton, a blueprint duplicated from a donor walker, and a WalkerParameters.json registry entry — and missing any one produces a walker that never appears or spawns but stands still with no warning. ## Core Features & Use Cases - End-to-end walker import: stages a correctly named FBX, imports it bound to the shared Skel_Pedestrian_G2/G3 skeleton, duplicates a donor blueprint, repoints its mesh, and registers the result as walker.pedestrian.<id>. - Rig-conforming FBX export: exports any shipped walker to FBX so you have a correctly skinned mesh to edit, which also validates the pipeline round-trip. - Live verification: after a server restart, spawns the walker, drives it with WalkerControl, and asserts a non-zero peak speed — the only proof the shared skeleton's animations drive the mesh. - Use Case: Clone shipped walker 0015, edit its appearance in a DCC tool while keeping skin weights, re-import it as walker.pedestrian.0090, and verify it walks at the commanded 1.4 m/s. ## Quick Start Ask the agent to import your rigged pedestrian FBX into CARLA on UE 5.8 as a new walker and verify that it spawns and animates.

Frequently Asked Questions about import-carla-ue58-walker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import a custom pedestrian into CARLA on Unreal Engine 5.8?▼

Run the import script with a skinned FBX and a name: it binds the mesh to CARLA's shared pedestrian skeleton, duplicates a donor walker blueprint, repoints its mesh, and registers the result in WalkerParameters.json. Restart the server, then verify with the spawn check.

Why does my imported CARLA walker spawn but not move?▼

The mesh was bound to a private skeleton created by the FBX importer instead of CARLA's shared Skel_Pedestrian_G2/G3, so the pedestrian animation set cannot drive it. This fails silently; the verify command catches it by asserting a non-zero peak speed under WalkerControl.

How do I get an FBX rigged for CARLA's pedestrian skeleton?▼

Export a shipped walker to FBX using the export command, for example walker 0015. That file is skinned to the shared pedestrian rig and can be edited in a DCC tool as long as the skin weights are preserved, then re-imported.

Can CARLA walker FBX export run headless in a commandlet?▼

No. Skeletal mesh export asserts in SkinnedMeshComponent and segfaults under -run=pythonscript with both -nullrhi and -RenderOffScreen. Both export and import require a full UnrealEditor with a DISPLAY set.

Why does a newly registered walker not appear in CARLA?▼

Walker definitions load once at server startup, so a walker registered against a running server does not appear until the server restarts. After restarting, the new walker.pedestrian.<id> appears in the blueprint library.

What are the limitations of importing walkers into CARLA UE 5.8?▼

The workflow covers pedestrians only, not vehicles, and does not import new animations, semantic tags, or LODs. It requires Linux with a built ue58-dev checkout, cloned content, and a display for the full editor.