Define the task
Tell us what you need to simulate, the target application and the references you have.
Clarity before complexity.
The right asset is the one that works in your application. We begin with the requirements and keep them visible through delivery.
Agree the specification
Set the geometry, materials, moving parts, formats and acceptance criteria before production.
Review in context
Evaluate a representative asset or scene against the intended use. Resolve the details that matter.
Prepare the handover
Review the delivery package, dependencies and integration notes against the agreed specification.
Which file formats can I request?
Start with the format and version your application accepts. Common requirements include FBX, OBJ, glTF and USD for visual assets, or URDF and SDF for robotics workflows. Availability is confirmed for each asset or custom scope.
What should be included in the brief?
Describe the object or scene, intended use, target application and available references. Add dimensions, polygon and texture budgets, moving parts, required formats and timing where known.
Can an existing model be adapted?
Use the request link on the model page to describe the changes. Format conversion, material changes and additional detail should be reviewed against the source asset before a delivery scope is agreed.
Are physics and sensor outputs included?
Only when they are part of the agreed scope. Visual geometry alone does not define physical behavior or a sensor response. Specify collision, mass, joints or annotation needs explicitly.
How are price and delivery time determined?
The asset complexity, reference quality, target formats and review requirements determine the scope. A project request begins that discussion; it is not a checkout or a payment.
Built around your requirementsWhat do you need
What do you need
to simulate?
An individual asset, a complete scene or a starting point for something more specific.
Discuss a project