3D Model Inspector
Look at a vehicle, outfit or weapon in 3D and swap its textures to preview changes.
Start here
Run 3D Model Inspector on a copy of your source files
PulseConvert → FiveM tools → 3D Model Inspector
Open the workflow: PulseConvert → FiveM tools → 3D Model Inspector. If the tool is locked, check its access notice instead of assuming it is available to your account.
Prepare the exact kind of input listed for this feature: Input: A .yft, .ydd, .ydr or .glb model. Keep an unchanged backup and ensure you have permission to reuse the assets.
Open the tool page and provide the requested source files and any displayed options. Check that the detected file types match the input requirement; do not replace unrelated files just to make an upload succeed.
Review the resulting files or job details. Expected outcome: Expected output: Mesh and texture details plus a live preview. Check mesh visibility and material slots when swapping textures; verify game-native files in game.
Compare the result with your original in a local editor. For resources that load in FiveM, start with an isolated test server; inspect the first client/server console error and test the asset in game before installing it for players.
Practical example
Look at a vehicle, outfit or weapon in 3D and swap its textures to preview changes. Keep the original file beside the result so you can compare what changed.
Before you begin
- Input: A .yft, .ydd, .ydr or .glb model.
- Access it through PulseConvert's tool directory.
- The registry labels this as a local/browser-side tool; check its page for any exceptions.
Overview of the setup
Prepare the input
Work on a copy of your originals. Gather: A .yft, .ydd, .ydr or .glb model. Check that any source asset can legally be reused.
Run 3D Model Inspector
Open 3D Model Inspector in PulseConvert and supply the requested input or settings. Check mesh visibility and material slots when swapping textures; verify game-native files in game.
Review the result
Expected result: Mesh and texture details plus a live preview. Read reported warnings, inspect the generated files and try the output in a separate test server or appropriate editor before production use.
Features explained
What each feature does and what to check before publishing or installing the result.
Purpose
Look at a vehicle, outfit or weapon in 3D and swap its textures to preview changes.
Input and preparation
Bring A .yft, .ydd, .ydr or .glb model. Keep an unchanged copy for comparison and rollback.
Result and verification
Expected output: Mesh and texture details plus a live preview. Check mesh visibility and material slots when swapping textures; verify game-native files in game.
If it still does not work
- If the tool rejects the input, compare your file extension and the files inside the archive to the input requirement above. Source files inside nested folders may need extra review.
- If the tool reports success but the result does not function, do not assume the file is compatible: inspect warnings, actual output names and their references, manifest files, and version compatibility.
- This is marked beta/untested. A downloadable file does not establish correct FiveM behavior.
Troubleshooting and safety checks
- Unsupported format or missing files? Verify the input matches the exact type described above and that the archive isn't only a screenshot/readme.
- Output exists but fails in FiveM? Check the resource folder, generated manifest, file references, first client/server console error and version compatibility.