For premium hard-surface vehicles, we compare providers by the output that matters: body fidelity, human-scale cabin packaging, separate components, PBR quality and cleanup time before automatic game export.
Current GTA Assistant integration. Strong multiview pipeline and PBR source mesh generation. Keep it only if the real output passes the vehicle packaging and quality gate.
Worth testing for vehicles because the API supports multi-image input, PBR, configurable texture resolution, target polycount and automatic real-world sizing.
Not connected in V10.6. Add only after we compare one identical Aether reference set against Tripo.
Another strong candidate for hard-surface comparison: up to five image inputs, PBR materials, configurable topology/face targets and high texture-quality tiers.
Not connected in V10.6. This becomes provider #3 if Tripo and Meshy still require too much cleanup.
They create source meshes. A drivable GTA V/FiveM vehicle still requires a real vehicle fragment setup: wheel/door bones, human seat placement, collisions, LODs, GTA vehicle shaders and metadata. That is why V10.6 adds the Vehicle Fit Rig instead of trying to fake the final result in JavaScript.