Outpost Universe Forums

Projects & Development => Outpost 2 Programming & Development => Topic started by: 0warfighter0 on January 08, 2016, 10:11:32 AM

Title: .map File format questions
Post by: 0warfighter0 on January 08, 2016, 10:11:32 AM
Hello there, I've figured out the uncompressed VOL and tileset BMP formats (thanks to all you folks' prior research) but now I'm a bit stuck on the .map format.

Does anyone have an idea how the mapdata references the tiletypes? And what is the point of the Tilegroups in the .map file, are they used? (Seems more of an editor only thing to me)

This is what I have:

Size (bytes)Description
4?
4?
4Value to calculate mapWidth (Math.Pow(2, value))
4Map height
4?
-------------------------------------------- For each tile{
4Tiledata. TerrainType seems to be 0x0000000F(Fast1, Fast2, Impassable1, etc.) No idea how it references the tilesets or types, maybe it references some sort of palette?
--------------------------------------------}
4?
4?
4?
4?
-------------------------------------------- For each tileset{
4Length of tilesetName
TilesetNameLengthTileset name
4Tileset tile count
--------------------------------------------}
?? space
10TILE SET 1a 00
?Is this maybe some sort of palette referencing the tilesets?
-------------------------------------------- For each tilegroup{
4Length of tilegroupName
TilegroupNameLengthTilegroup name
?Tilegroup data
--------------------------------------------}
Title: Re: .map File format questions
Post by: dave_erald on January 08, 2016, 12:38:07 PM
Tile groups make placing large items quicker, volcano's, cliffs, ice cliffs at the top and bottom of world maps, and there are large brush blocks for making sand, rock, volcano terrain easier and more random (albeit those stamp pads, if you want to call them that, could be much larger in my opinion)  Open the mapper and open a OP2 current map and you should see that.

I am hoping you're asking because you want to make the mapper more productive (in that case some suggestions could be made on that part)

Hooman would be able to tell you the ins and outs of the code I'm sure, and Leeor has experience with mappers as well. And most people are on the same page in believing that this mapper could use a healthy update.
Title: Re: .map File format questions
Post by: 0warfighter0 on January 08, 2016, 01:18:50 PM
Yeah, it's very buggy. I need to write a game tool for ToolDev with WPF so I thought a more user friendly editor would be handy. I'm open for suggestions.

I know that tilegroups are handy, I just wonder why they are stored in the map files themselves, it seems pretty illogical.
It would make more sense if the map files contained just the map info, tiles and keep the tilegroups in the editor only. (unless the tilegroups are referenced in the tiledata, I don't know)
Title: Re: .map File format questions
Post by: Sirbomber on January 08, 2016, 03:07:30 PM
Quote from: 0warfighter0 on January 08, 2016, 01:18:50 PM
I know that tilegroups are handy, I just wonder why they are stored in the map files themselves, it seems pretty illogical.

You're confused because OP2's devs did something dumb?  You must be new here.  :P

Anyways, this post (https://forum.outpost2.net/index.php/topic,3650.0.html) contains most of what we know about OP2's internals, including the map format.  It should help you out.
Title: Re: .map File format questions
Post by: 0warfighter0 on January 08, 2016, 05:21:00 PM
I found the other Format topics but I missed this invaluable one! Thanks for the heads up, this is just what I need.
Title: Re: .map File format questions
Post by: Hooman on January 09, 2016, 11:26:10 AM
Thank you Sirbomber. That reminds me the data in that archive should go in the SVN somewhere. There is a post on the Saved Game and Map File Format (https://forum.outpost2.net/index.php/topic,1250.msg27376.html#msg27376) which is basically a copy of the text file found in the archive.

The TileGroup data at the end of .map files is not used by the game. It's not even loaded into memory. I think I almost missed it because of that. The data was extracted for use in the map editor, where it is useful.

The map data is actually an array of bit fields. Each 32-bit tile contains an 11-bit tile index. This is indeed an index into a palette. With 11 bits, there is a max of 2048 tiles that can be referenced. Outpost 2 uses most of these with the built in maps and tile sets. Each map specifies which tiles set files to load, and how many tiles to load from each. The index from the map data is used to lookup into the palette data, which translates to a tile set index, and an index within that tileset for the graphic to display.