Current Ivy Engine limitations, regressions, and workarounds.
Safari support is not ready
Status: Open
Area: Browser Compatibility
WebGPU and related rendering features are not fully supported or optimized in Safari yet.
Workaround
Use a Chromium-based browser while Safari coverage is still being expanded.
Updated:
Custom shader loading is not fully connected through the renderer yet
Status: Open
Area: Rendering
Shader graph to renderer integration is still incomplete and needs more production coverage.
Workaround
Prefer the existing shipped shader paths until the broader custom-shader flow is completed.
Updated:
Standalone export still needs broader real-world testing
Status: Open
Area: Export
Edge cases across devices, browsers, and project layouts still need broader validation.
Workaround
Use the default project layout while export testing coverage is still being expanded.
Updated:
Play Mode startup and physics synchronization remain active focus areas
Status: In Progress
Area: Play Mode
Startup behavior and physics synchronization are improving, but they still receive ongoing stability work.
Workaround
Re-test first-run Play flows after larger scene or startup changes until the flow is fully hardened.
Updated:
Documentation is still incomplete
Status: Planned
Area: Documentation
Guides and references are expanding, but several important areas are still in draft or missing.
Workaround
Use the development pages, weekly notes, and source browser alongside documentation pages when a topic is not fully covered yet.
Updated:
Project Summary
Ivy Engine is an early browser-native 3D engine and editor. It is usable for experiments and internal projects, but it is still under active development. The project is source-available, WebGPU-based, and designed for direct project control through TypeScript, JSON project data, and explicit documentation.