Palatial is accelerating spatial content creation by transforming 3D models into interactive, simulation-ready experiences. Our vision is to make it possible for anyone from professional agencies to indie developers to build expansive real-time environments and robotics simulations, and to make these experiences accessible to any audience.
The SimReady Pipeline converts raw inputs into simulation-ready assets for robotics, gaming, and real-time environments. It accepts four input types: text, image, mesh, or video. Each input passes through a pipeline that generates or reconstructs a 3D mesh, creates or optimizes textures, and builds accurate collision meshes. The pipeline then performs automated physics estimation, assigning properties such as mass and friction using the visual characteristics of the mesh. Assets are validated in a simulator to confirm accuracy and performance, and the final package is published to the dashboard with a downloadable bundle that includes OBJ files, textures, simulator wrappers, and a JSON of physics metadata.
<aside> đź’ˇ
Access the pipeline at https://dashboard.palatial.cloud/login by creating an account and starting your first project
Can’t find what you’re looking for? Ask our team directly on the :discord-icon: Community Discord
</aside>
For detailed documentation, refer to the pages below:
Physics and Collission Generation
The Palatial Plugin Suite optimizes and repairs Unreal Engine scenes and assets, enhancing performance for architectural and BIM imports, game development, simulation, virtual production, and other real-time workflows. It's a modular, customizable framework built to automate optimization tasks, reduce render times, and simplify asset management. Open the plugins in any Unreal project to analyze your scene, apply recommended optimizations, or customize operations to fit your needs.
<aside> đź’ˇ
Download the plugin at https://www.palatialxr.com/downloads
Can’t find what you’re looking for? Ask our team directly on the :discord-icon: Community Discord
</aside>
For detailed documentation, refer to the pages below: