Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Description: JMSv2 is a general encompassing term used by myself to describe versions of the .JMS related to Halo 2 .JMS importing.
- (See versions 8205-8210 for JMSv2 examples.) Examples of this format can be discovered by using the Tag Extractor's "extract import info" command
- to retrive the import files held by the default H2EK tags. Files that have been packaged do not hold these import files.
- In this document I will go over the file structure and try to be as descriptive as I can.
- At time of writing it is not known if specifc .JMS versions disable or enable specifc features, but going outside the 8197-8210 range will cause an unknown version error.
- It is not known if the file versions extend beyond this range.
- .JMS files in Halo 2 are unicode files that are laid out in a specific manner. Halo CE .JMS(8197-8204 are accepted by tool although it must undergo modifications.
- Files must be converted to unicode and have some sections written different such as the material flag section in CE. See the H2Codez manual for more details.
- JMSv2 files are much the same with them needing to be unicode but they also have a different layout compared to .JMS(CE) or .ASS.
- Every single section must be filled with data. Even if that data is 0. If you do not include say the 0 for markers you will get a "end of file" error.
- The file uses tabs for instead of space for items next to each other. Spaces in your file will give you pharsing errors.
- Let us begin with the first section
- This is pretty straight forward here.
- >>>>>>>>>>>>>>>>
- ;### VERSION ### (Header)
- 8210 (Version number. The number defined will determine how tool treats the file.)
- ; <8197-8210> (Comment defined by a ;. These are ignored by tool)
- >>>>>>>>>>>>>>>>
- The next section will now be able the object orgin or more commonoly known as frame or b_levelroot.
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- ;### NODES ### (Header)
- 1 (Gives the number of nodes laid out by the exporter that tool has to go through. Having the wrong amount can cause "end of file" errors.)
- ; <name> (The name of object origin)
- ; <parent node index> (The index of the object starting at -1. This can be followed by a node with an index of 0 for a child node. This will be seen in things like rigged models)
- ; <default rotation <i,j,k,w>> (Rotations are a quaternion with a default definition of 0.0000000000.)
- ; <default translation <x,y,z>> (Translation is the location of the object in the world with a default definition of 0.0000000000)
- ;NODE 0 (A header that describes what item is being laid out with a index. Index goes in increments of 1 per item starting from 0 though this is just a comment and is not needed.)
- b_pelvis (The name of our object origin.)
- -1 (The parent node index with -1 being null.)
- 0.4999988079 0.5000004768 0.4999994934 -0.5000011921(The rotation of our object in quaternion. The default values for this will always be "0.0000000000 0.0000000000 0.0000000000 1.0000000000")
- 1.4614276886 0.0000029225 44.0024833679 (The location of a vertice in space. The default for this will always be "0.0000000000 0.0000000000 0.0000000000")
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- This section will cover materials.
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- ;### MATERIALS ### (Header)
- 1 (Gives the number of materials laid out by the exporter.)
- ; <name> (Name of our material.)
- ; <[???] [LOD] [Permutation] [Region]>(A few options here for a person to look at. The first is a number surrounded by parentheses. It is unknown what this number is or any effects it may have. Testing on it gave no answer and currently it is considered to yield no effects. No hypothesis on the usage of this number as application appears to be completely random. One file can have a single material with this number starting at 1 while another starting a 3 with no 1 or 2 in sight. The next is a level of detail setting. It is a capital L followed by a number with the number ranging from the standard 1-6 seen in the editor. It's likely that both the so far brought up options only affect the render_model tag and since the model-render command doesn't exist then these two should be considered deprecated with no need to worry about including them in a potential exporter. The)
- ;MATERIAL 0 (A header that describes what item is being laid out with a index. Index goes in increments of 1 per item starting from 0 though this is just a comment and is not needed.)
- cov_battery_shiny (example name)
- (1) L5 base object (example unknown, example level of detail, example permutation, and example region)
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- This section will cover markers.
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- ;### MARKERS ### (Header)
- 1 (Gives the number of materials laid out by the exporter.)
- ; <name> (Name of our marker. Name must be unique otherwise it will be ignored as a duplicate marker.)
- ; <node index> (The index of the node that the marker is parented to.)
- ; <rotation <i,j,k,w>> (The rotation of our object in quaternion. The default values for this will always be "0.0000000000 0.0000000000 0.0000000000 1.0000000000")
- ; <translation <x,y,z>> (Translation is the location of the object in the world with a default definition of 0.0000000000)
- ; <radius> (The size of the marker)
- ;MARKER 0 (A header that describes what item is being laid out with a index. Index goes in increments of 1 per item starting from 0 though this is just a comment and is not needed.)
- drool2 (Example name. I am assuming that if the model-render command existed then this would act as more of a group name and would allow duplicates. Markerks on levels only seem to accept unique names.)
- 6 (Example node index.)
- -0.0256266929 -0.4670926630 -0.0289750062 -0.8833618760(Example rotation.)
- 3.5272619724 0.4587731361 -2.0605127811 (Example translation.)
- (Random fucking space for some reason. Not sure why this is here but it seems to be in every file I've seen with markers.)
- -1.0000000000 (Example Radius. This was most likely only a model-render option as this does not seem to be an option in the scenario_structure_bsp tag. More testing will be needed to see if this option does actually have an effect on markers in the sbsp tag.)
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- This section will cover instance xref paths. While it has instance in the name it appears unrelated atm. A more accurate writing of this section would be enviroment xref paths as this does not deal with instance geometry but enviroment objects which are scenery tags.
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- ;### INSTANCE XREF PATHS ### (Header)
- 1 (Gives the number of enviroment objects laid out by the exporter.)
- ; <path to .MAX file> (The path to a .MAX file. This file is used to find the location of the JMS files in data based on the path or the compiled tags. This list can then be referenced in the block below. Testing so far seems to indicate that finding the path is all the .MAX file is used for.
- ; <name>
- ;XREF 0
- C:\Program Files (x86)\Microsoft Games\Halo 2 Map Editor\data\objects\multi\object\render\object.max
- object
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
