What each format brings to the workflow
GLB is the binary container form used by glTF. It can keep a model and its resources together, which is convenient for a browser upload. But do not assume every GLB is entirely self-contained: the format can still refer to external resources, and support for material extensions differs between importers.
FBX is common in DCC-to-engine workflows and can contain more than static geometry. OBJ is useful for straightforward meshes but typically relies on an MTL and separate image files for its material setup. That makes a one-file browser import different from importing a complete folder.
| Format | 2VFX browser path | Unity package caveat |
|---|---|---|
| GLB | Supported, including configured Draco/Meshopt/KTX2 decoding paths | Original bytes are retained; install a compatible glTF importer in Unity. |
| FBX | Supported for self-contained resources | Unity can import the model; verify materials and scale. |
| OBJ | Supported geometry; separate sidecars are not resolved | Bring any missing external material resources into Unity yourself. |
Use an asymmetric test model
A plain centred cube hides orientation mistakes. For an import check, use a small arrow-shaped prop, two material regions and a visible checker pattern. Keep a copy of the same geometry in each format. This proposed fixture is a diagnostic method, not a downloadable model bundled with the site.
Compare the direction of the arrow, the checker orientation, the number of material regions and the model bounds. A mirrored model can look plausible if its silhouette is symmetric. Record which application exported the asset and any unit or axis settings you changed.
Understand preview normalization
2VFX normalizes the model in its browser preview so that small and large source models fit the working area. The source bytes and preview transform are different pieces of data. A model appearing at a convenient size does not prove that its authored unit scale was one metre.
The Unity package preserves the source model and applies the recorded preview transform in the generated hierarchy. Check the resulting dimensions against the scale of your actual game scene. If a flame is correctly attached but the prop is tiny, inspect the model transform rather than only enlarging the particle system.
Diagnose missing textures before the effect
If geometry loads but colour disappears, first inspect resource packaging. A loose OBJ texture or an FBX dependency outside the uploaded file is not fetched merely because a desktop DCC application knew its path. Re-export a self-contained asset when possible or reassign the resources in the engine.
A successful model import also does not certify skeletal animation, constraints, custom shaders or every material extension. The current 2VFX task is attaching effects to imported models; it does not claim a complete DCC scene round-trip.
A two-stage acceptance check
Run the browser and Unity checks separately. Keep the .2vfx project so the intended transform and effect attachment can be reproduced.
- In the browser: check geometry, orientation, textures, material regions and framing.
- Place the effect at a recognizable point on the model, not just its origin.
- Export the Unity .tgz and install the required model importer if using GLB.
- Run the prefab builder and inspect model scale plus the effect’s local attachment.
- Play the effect while moving the model. Keep source-format issues separate from simulation-space issues.