JMF (Jackhammer Map Format): Difference between revisions
Jump to navigation
Jump to search

Warning:As of the Christmas 2023 update, JMF files from the latest paid version of Jack cannot be opened in the free version of Jack. The latest free version saves files in JMF version 121, whereas the latest paid version is
Confirm:It may be possible to create a program that strips the extra v122 information to create a v121 JMF, as the only new feature of the new version is background images for the 2D viewports.
SirYodaJedi (talk | contribs) mNo edit summary |
SirYodaJedi (talk | contribs) m (→Structs) |
||
| Line 15: | Line 15: | ||
}} | }} | ||
== Structs == | == Structs == | ||
{{stub}} | |||
See the TWHL wiki page linked [[#External links|below]]. | |||
== See also == | == See also == | ||
Revision as of 12:22, 30 December 2023
This page documents information about an engine not developed by Valve. This information is documented here because it has technical and/or historical relevance to Valve's engines.
The Jackhammer Map Format (JMF) is a binary file format used by
J.A.C.K. to store map project data before being exported to MAP, like RMF. Unlike RMF, JMF supports objects being part of multiple visgroups, KVs longer than 15 characters, and Quake III patch meshes. Additionally, it can store paths in a slightly different manner, optimized for Jack's Path Tool.
Structs
See the TWHL wiki page linked below.
See also
- MAP, used by the map compilers
- RMF, used by
Hammer 3.x and openable by
J.A.C.K. - VMF, used by
Hammer 4.x and openable by
J.A.C.K. - SMF, used by
Sledge
External links
Specification: JMF on THWL wiki- JmfFormat.cs from
MESS source code - sledge-formats library