Collision Checker
Checks model names against vanilla GTA and names Pulse Convert has already issued.
Start here
Run Collision Checker on a copy of your source files
PulseConvert → FiveM tools → Collision Checker
Open the workflow: PulseConvert → FiveM tools → Collision Checker. 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 list of model names or your resources folder. 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: Every name that would clash with another model. Look for clashes with base-game model names and names already allocated by PulseConvert before renaming.
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
Checks model names against vanilla GTA and names Pulse Convert has already issued. Keep the original file beside the result so you can compare what changed.
Before you begin
- Input: A list of model names or your resources folder.
- Sign in to PulseConvert before opening this tool.
- This workflow may use PulseConvert's server-side processing; keep source assets private.
Overview of the setup
Prepare the input
Work on a copy of your originals. Gather: A list of model names or your resources folder. Check that any source asset can legally be reused.
Run Collision Checker
Open Collision Checker in PulseConvert and supply the requested input or settings. Look for clashes with base-game model names and names already allocated by PulseConvert before renaming.
Review the result
Expected result: Every name that would clash with another model. 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
Checks model names against vanilla GTA and names Pulse Convert has already issued.
Input and preparation
Bring A list of model names or your resources folder. Keep an unchanged copy for comparison and rollback.
Result and verification
Expected output: Every name that would clash with another model. Look for clashes with base-game model names and names already allocated by PulseConvert before renaming.
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.
- Review warnings and test the output before putting it on a live FiveM server.
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.