Free mapping source examples
Original, editable exercises for learning YMAP placement and MLO handoffs. These are source projects, not tested native YMAP downloads or finished FiveM interiors.
Three props: a minimal YMAP exercise
Three traffic-cone placements make it easy to count objects, compare coordinates and detect a duplicate or missing export. The project uses a local origin of zero and illustrative asset bounds: choose a clear test location and recalculate extents against your installed game assets before native export.
Download the editable Map Studio JSON · Inspect CodeWalker YMAP XML · Vanilla-prop manifest · Instructions and provenance
Open the JSON in Map Studio, then follow Create your first YMAP. The example contains placement data only: no copied GTA mesh, texture or collision assets.
Two-room MLO source handoff
The existing community-workshop source package exercises two rooms, a shared doorway and an exterior doorway. Use it with the Blender companion. Its package README identifies the source files and the unfinished native-resource folder.
Use the MLO guide to inspect the source stage, and the release checklist before any deployment. Source generation, native compilation and gameplay acceptance are separate results.
Dependencies and test status
| Example | Dependencies | Evidence boundary |
|---|---|---|
| Three props | Map Studio; matching Legacy assets; CodeWalker for native output | Deterministic source serialization and browser import; native compilation and FiveM gameplay unverified |
| Two-room source package | Blender 4.2.23 LTS, Sollumz 2.9.0, szio 1.3.0.dev9, CW Studio 0.1.0 | Existing companion source acceptance record; no new native or in-game certification from this page |
Reuse and attribution
The newly authored three-prop placement source, manifest and measurement worksheet are provided under the MIT license. That permission applies only to these authored example files, not to referenced GTA assets, external tools, or the separately GPL-licensed Blender companion. No third-party mod is mirrored here.
Record your own result
Download the empty performance-run worksheet. Record the target edition, build, hardware, resolution, route, run type and observed frame times. It contains no sample FPS claims. Follow the optimization guide for controlled comparisons.