JMF (Jackhammer Map Format): Difference between revisions
Jump to navigation
Jump to search
SirYodaJedi (talk | contribs) mNo edit summary |
SirYodaJedi (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
{{stub}} {{non-valve engine|engine}} | {{stub}} {{non-valve engine|engine}} | ||
The '''Jackhammer Map Format''' ('''JMF''') is a binary file format used by {{jack|4}} to store map project data before being exported to [[MAP]], like [[RMF]]. Unlike RMF, JMF supports objects being part of multiple visgroups, and {{quake3|2}} patch meshes. Additionally, it can store [[path entity|paths]] in a slightly different manner, optimized for Jack's [[J.A.C.K./Path Tool|Path Tool]]. | The '''Jackhammer Map Format''' ('''JMF''') is a binary file format used by {{jack|4}} to store map project data before being exported to [[MAP]], like [[RMF]]. Unlike RMF, JMF supports objects being part of multiple visgroups, and can store {{quake3|2}} patch meshes. Additionally, it can store [[path entity|paths]] in a slightly different manner, optimized for Jack's [[J.A.C.K./Path Tool|Path Tool]]. | ||
== Structs == | == Structs == | ||
Latest revision as of 09:47, 10 February 2025
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, and can store 
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