Summary
Unreal Engine currently requires launching the full engine or using the CLI (UE4Editor-Cmd.exe
) to import FBX files and convert them into UAssets. This process is resource-intensive and inefficient for large-scale automated workflows.
I propose a lightweight standalone FBX to UAsset converter that would allow developers to generate UAssets without launching Unreal Engine. This would significantly improve automation, asset pipeline efficiency, and scalability for studios processing thousands of assets.
Why This is Needed
- Performance & Automation
- Running Unreal in CLI mode for simple FBX imports consumes unnecessary resources.
- A standalone tool would allow faster batch processing without Unreal overhead.
- Scalability for Large Studios & Pipelines
- Asset-heavy projects (e.g., automotive, simulation, VFX) require automated asset processing pipelines.
- A direct FBX โ UAsset converter would allow parallel processing on multiple machines, even without Unreal installed.
- Reducing Engine Dependency for Asset Processing
- Unreal must be loaded to generate UAssets, slowing down automated workflows.
- A direct converter would allow assets to be prepped before Unreal is even installed.
Technical Considerations & Challenges
I understand that UAsset is a proprietary, version-dependent format, making a fully external converter complex. However, possible solutions include:
- Exposing Unrealโs FBX import logic as a standalone CLI tool.
- Providing a lightweight Unreal Asset SDK that allows third-party applications to generate UAssets.
- Allowing an Unreal build mode that runs only the import subsystem (without UI, rendering, physics, etc.).
- Modularizing the asset import pipeline so it can run independently of the full Unreal Engine.
Proposed Features
- Command-line execution (no UI, lightweight).
- Direct FBX import to UAsset conversion (without launching full Unreal).
- Supports essential Unreal features (meshes, materials, skeletal meshes, LODs).
- Modular design for future Unreal updates (avoid version-locking).
- Optional API integration for advanced workflows (Python/C++ support).
Conclusion
This request acknowledges the complexity of UAsset serialization but proposes a minimal, lightweight solution that would greatly benefit Unreal-based pipelines. Even a stripped-down CLI tool that only runs the import process would be a major improvement.
Would Epic consider exposing a minimal UAsset conversion tool or SDK for advanced automation workflows?