ModdingWiki - User contributions [en-gb]

Wacky Wheels High Score Files

2012-02-20T02:59:33Z

Yellowantphil: copy editing

This page describes the high score file formats in [[Wacky Wheels]].

==Single-player race==
Single-player race high scores are saved in <tt>wacky1.hi</tt> for 12 hp engines and <tt>wacky2.hi</tt> for 6 hp engines.

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>[[Wacky Wheels#File formats|wacky.dat]]</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.

Each file contains 144 of the following structures:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || unknown || A number between 1 and 6. I don’t think this number is used for anything.
|-
| [[INT16LE]] || racer || 0=Uno, 1=Sultan, 2=Morris, 3=Peggles, 4=Razer, 5=Ringo, 6=Blombo, 7=Tigi
|-
| [[INT16LE]] || score || Player’s score
|-
| [[char]][20] || date || The date, in the format <tt>01 SEP 1994</tt>, or whatever other text you want to enter. Should be null-terminated after 12 characters for the text to fit the screen.
|-
| [[char]][20] || name || The player’s name. 14 characters will fit on the screen.
|}

The structures come in groups of four, because the top four scores are displayed on each “famous drivers” screen. Every other group of four structures is unused.
* The first group of four structures give the four highest scores for the regular bronze courses, amateur class.
* The second group of four structures is unused.
* The third group is for the regular bronze courses, pro class.
* The fourth group is unused.

Next is regular bronze courses, champion class, followed by regular silver courses, amateur class, etc. After the regular gold courses, champion class, the bonus pack course high scores start.

==Duck shoot==
Duck shoot high scores are stored in <tt>wacky.dtt</tt>. If deleted, the file is created using default names and scores in <tt>ww.exe</tt>.

The file contains four of the following structures:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[char]][20] || player || Player’s name
|-
| [[INT32LE]] || score || Number of points
|}

The four names and scores are displayed just before starting a duck shoot.

==Time trial==
The fastest time trial times are saved in <tt>wacky1.tim</tt> for 12 hp engines, and <tt>wacky2.tim</tt> for 6 hp engines.

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.

Each file contains 30 of the following structures:
{|class="wikitable"
! Data type !! Name !! Description
|-
| [[char]][20] || lap_name1 || Name of the driver with the best lap time. Needs to be null-terminated.
|-
| [[char]][20] || lap_name2 || Driver with the second best lap time
|-
| [[char]][20] || lap_name3 || Driver with the third best lap time
|-
| [[char]][20] || lap_name4 || Driver with the fourth best lap time
|-
| [[UINT32LE]] || lap_time1 || Time of the first driver, in tenths of a second. Maximum is one hour (36,000 tenths of a second)
|-
| [[UINT32LE]] || lap_time2 || Time of the second driver
|-
| [[UINT32LE]] || lap_time3 || Time of the third driver
|-
| [[UINT32LE]] || lap_time4 || Time of the fourth driver
|-
| [[char]][20] || overall_name || Name of the driver with the best time for the entire race
|-
| [[UINT32LE]] || overall_time || Best overall race time, in tenths of a second. Maximum one hour.
|}

The thirty structures are in this order:
* Regular bronze courses, tracks 1–5
* Regular silver courses
* Regular gold courses
* Bonus bronze courses
* Bonus silver courses
* Bonus bronze courses

[[Category:Wacky Wheels]]
[[Category:File Formats]]

User talk:Malvineous

2012-02-02T14:06:44Z

Yellowantphil: /* Wacky Wheels */ reply

== Wolfenstein 3D -> Wolfenstein 3-D ==
I've corrected the infamous 3D tyop in the names of several Wolf3D-related pages; can you please delete the following ones?

[[:Category:Wolfenstein 3D]] -> Superseded by [[:Category:Wolfenstein 3-D]] 
[[:Image:Wolfenstein_3D.png]] -> Superseded by [[:Image:Wolfenstein_3-D.png]]

Thanks :) --De Zeurkous (zeurkous@zeurcomp.nichten.info), Thu Nov 22 08:18:42 UTC 2007

:Haha, you've certainly been busy. Don't forget that this wiki isn't meant to be an encyclopaedia of the games, its main purpose is documenting the file formats and editing tools that can be used with the games, as opposed to how the games behave without any mods, or what they might be called if you forget to change the title screen :-) -- [[User:Malvineous|Malvineous]] 11:14, 22 November 2007 (GMT)

::Nah, I haven't forgotten. As we're reinventing the wheel for a semi-virgin wiki, the naming and something static like the cheats seemed like a good place to start :) --De Zeurkous (zeurkous@nichten.info), Thu Nov 22 12:20:04 UTC 2007

== Jill of the Jungle palette ==

Hi, I'm currently working on a level viewer for [[Jill of the Jungle]] (maybe an editor later on). Some of the information I found here has been very useful, but there's one thing I'm a bit stuck on. On the [[SHA Format]] page it says:
:''Each array item contains 4 unsigned bytes, representing CGA, EGA and VGA, respectivley, and then a null value. [...] Each byte maps to the index of a colour in the palette. If there are no colours required, the tile set uses the default colours.''
However, it doesn't say anywhere where the palette can be found. Is it stored in the EXE file? I hope you can help me on this :)

Regards, [[User:Spinal|Spinal]] 13:00, 2 March 2008 (GMT)

:Unfortunately I didn't write the JotJ SHA page, and I haven't yet had the time to figure this out. For Xargon I've taken the quick and dirty route and used a screenshot from within DOSBox as the source of the palette, until I can figure out where the palette is located. If you find this out, don't forget to update the page! :-) -- [[User:Malvineous|Malvineous]] 22:02, 2 March 2008 (GMT)

::Hey Spinal, sorry, I wrote the [[SHA Format]] page, so that was probably my bad. I wasn't able to find the palette either. I assume it's in the .EXE, however I spent a fair bit of time manually mapping it using a Wombat tool (http://www.szevvy.com/node/3). I was also writing a level viewer (initally in XHTML which turned out to be too slow, so then I moved to Flash 9). I tried to email you my findings, but the email bounced. I'm not sure if they were 100% accurat, which is why I never added them to the documentation.

::Hey Malvineous, it seems the Jill - [[DMA Format]] page has been removed. Do you have a log of what happened to it? I'm sure it existed at some point.

::- [[User:dheim|Daniel]] 20:00, 5 March 2008

:::I don't ever remember seeing a DMA page - certainly there's nothing in the wiki logs about it being deleted or renamed. Maybe you started working on it but never got around to saving it? Or is it one of the Xargon pages that shares the same format as Jill? (by the way, you can type <nowiki>~~~~</nowiki> to automatically put in the signature in these messages.) -- [[User:Malvineous|Malvineous]] 11:28, 5 March 2008 (GMT)

::::Sorry, it must have been the stuff in the [[SHA Format]] page that I was thinking of. I may have added the link to the [[DMA Format]] page, and never expanded on it. - [[User:Dheim|Daniel]] 02:46, 6 March 2008 (GMT)

:::::Hi guys. Sorry for the mistake, I mixed up the authors of the SHA and level formats. I've written a level viewer in PHP the last week, by using static images instead of getting them from the actual files. This causes some problems for episode 2, which uses a different palette, but besides that it works great :) When everything is done I'll upload the maps to my server and the tile/object lists to this wiki.
:::::@Daniel: strange that it bounced, I confirmed my address so it should be working fine... You can mail it to spinal -at- zanderz -dot- net. Also, I saw on your Wombat page that you "have a vague idea of how to do" [[Hocus Pocus]]. Could you share your findings on this wiki? I'd love to make maps, or even a level viewer/editor for that game :) -- [[User:Spinal|Spinal]] 00:32, 8 March 2008 (GMT)
:Okay, with help of [[User:Dheim|Daniel]] who send me the palette I found it! I'll put my findings on [[Jill of the Jungle palette]]. -- [[User:Spinal|Spinal]] 15:36, 13 March 2008 (GMT)

== Halloween Harry/Alien Carnage ==

Hi Malvineous. Thanks for your edits on the GMF article! I notice you mentioned there exist versions of the game which don't require exploding a BNK to get at the game data. What does the directory structure look like for the version you have? I'm working on a map viewer (which will become a map editor at some point) and would like it to be able to work on whatever versions are out there. Thanks for any info. -[[User:Duckthing|Duckthing]] 04:41, 11 December 2010 (GMT)

: Hi Duckthing - no worries, Halloween Harry has long been an interest of mine, but my map editor sadly needs a lot more work before I can begin reverse engineering more file formats so I'm glad you've made a start! AFAIK technically Halloween Harry has no compression, but for whatever reason (probably listed in the Apogee FAQ) they decided to swap episodes 1 and 3, compress the BNK file and then re-release it under the name Alien Carnage. You can download all available versions (including registered versions since the game was released as freeware in 2007) from [http://www.classicdosgames.com/game/Alien_Carnage.html RGB Classic Games]. BTW not sure if you noticed but I also posted a couple of things on the GMF article's talk/discussion page. -- [[User:Malvineous|Malvineous]] 06:08, 11 December 2010 (GMT)

:: Thank you! Working with the uncompressed version will keep things less complicated. I did notice the GMF discussion you added, but haven't had a chance to really go through it yet. -- [[User:Duckthing|Duckthing]] 06:41, 11 December 2010 (GMT)

::: No worries. If you're running Linux or MacOSX you should be able to compile [[Camoto|libgamearchive]] which will let you copy files in and out of the BNK files. This is a library so it's also possible to use it in your own program for accessing and editing the map files while they're still inside the BNK, for instance. (BTW the 'minor' tickbox should only be used when the edit does not affect the information on the page - e.g. fixing a typo or a broken URL. If you are changing the actual content on a page it is never a minor edit!) -- [[User:Malvineous|Malvineous]] 07:51, 11 December 2010 (GMT)

== Dangerous Dave ==

Working on this, does anyone have any info on the formats? The EGA graphics are 84KB and external, but CGA and VGA graphics unrelated to them are in the 174KB executable, apparently uncompressed, I don't know how this is possible. I've found the levels and partially reverse engineered the format (The first 1000 bytes, a 100x10 array of tiles.) but each level is followed by ~280 bytes of variable and unknown data I assume is sprites. I have a list of internal files in the executable, looks like most of it is non-game code. Any help would be appreciated. -[[User:Levellass|Endian? What are you on about?]] 06:03, 12 December 2010 (GMT)

: Hmm, interesting. All I can suggest for the levels is - as you're probably already familiar with - changing the values in a hex editor then loading the game to see what happens. I would suspect that all the graphics would be in a similar format, so if there are any headers or structures used in the EGA graphics files perhaps they're duplicated for CGA/VGA? Also John Romero seems pretty accessible, perhaps you could ask him directly? Failing that, randomly writing data into the .exe until the images change could be used as a last resort! -- [[User:Malvineous|Malvineous]] 12:09, 12 December 2010 (GMT)

: Ha, that was easier than I expected - uncompressed VGA data is easy to find with a good hex editor ;-) [http://www.shikadi.net/pics/ddave-vga-hexdump.png This looks like it] -- [[User:Malvineous|Malvineous]] 12:17, 12 December 2010 (GMT)

: Ok that was only the menu graphics. At offset 0xC629 there's some sort of offset table which looks very similar to the contents of EGADAVE.DAV but there are extra bytes dotted all over the place - perhaps it's RLE encoded? Actually just before that there's the number 0x6CAA. If you go a bit less than 0x6CAA bytes after this you end up with another table, which to me suggests that 0x6CAA is the decompressed size of that first table. -- [[User:Malvineous|Malvineous]] 13:01, 12 December 2010 (GMT)

:If I remember it correctly, the VGA sprites and tiles are RLE compressed and it's not too hard to decompress them. The positions of the enemies in the levels on the other hand are still a mystery to me. [[User:Calvero|Calvero]] 20:43, 12 December 2010 (GMT)

: Looking at the levels, which directly follow the VGA palette, they seem to contain 256 bytes of header data, then the 100x10 tiles, then eight bytes of lead-out data. Then the next level's 256 bytes of header, 100x10 tiles, then eight bytes of lead-out. Although I say "level", the first "level" seems to contain both level 1 and 2, and this seems to be the way it works in the game - in some levels you can see through to others. I'm not sure what the 256 bytes of header data are for, but some levels have FF FF 00 00 repeated which seems to indicate two uint16 fields which are blanked out for those levels. -- [[User:Malvineous|Malvineous]] 13:15, 13 December 2010 (GMT)

::First up, levels; where does level 1 start? It's possible I'm reading the start of a level as the previous level's end, I looked for the start of tile data, which I assumed, like Keen 1, would be the level start.

::Next, palette; I'm assuming, as you said, it is located just before the level data?

::There is VGA and CGA graphics in the executable, plus headers, but the bulk of graphics for CGA and VGA I haven't been able to locate. If the data is RLE compressed I should think it would use either Keen 1-3 fullscreen or Jazz Jackrabbit tile RLE, both of which I know well. I'll look into both of these options, cheers! -[[User:Levellass|Endian? What are you on about?]] 12:03, 20 December 2010 (GMT)

:::I've found the VGA and CGA data for the menu graphics. It looks like the CGA data is stored in a series of 1-bit-per-pixel (monochrome) images. Or it could be EGA data with the planes split out (e.g. red plane for all images, then green plane for all images, etc.) I think I found three planes which means it's probably EGA, as CGA would have a max of two planes. I've also found the font graphics, this looks like 4bpp/16 colour EGA data. Haven't seen level graphics yet. I've successfully modded the levels with a hex editor (putting the jetpack everywhere) so now I've finally looked at all the levels! The creatures are definitely not stored in the 100x10 tile data. Putting random bytes in there revealed that the values are indices into the image files, because if you put the value in for fire it will animate, and the following three or so values show up as still frames from the fire animation.

:::The VGA palette starts at 0x26B0A (I updated the main DDave page with this) + 768 bytes leads straight onto the start of level 1 at 0x26E0A. So at 0x26E0A there are 256 bytes of data, then 100x10 tiles, then 24 bytes of footer data. Some of this data (perhaps footer data) might be the level start coordinates, because Dave doesn't always start the level at the same place (e.g. the warp level when you climb the tree on level 5 and jump off the edge of the screen.) -- [[User:Malvineous|Malvineous]] 12:24, 20 December 2010 (GMT)

:::I think I've found all the files so far, I've updated [[Dangerous Dave]] with the offsets of the files, including what appears to be CGA and VGA tiles. I'm not sure what sort of format they're in though, it looks like they might be compressed (and so the offsets in that list might be off by ~4, as I may have cut off the decompressed-size field.) I've also updated the map format page, I think it's pretty much fully reverse engineered now. -- [[User:Malvineous|Malvineous]] 05:13, 21 December 2010 (GMT)

== Noahs Ark 3D and IMFs ==

Been poking around Noah's Ark 3D, an adaption of the Wolfenstein game and found a few interesting things which I'm hoping to confirm.

First, the game uses MID files, not IMF files for music, second, the MIDI files have an extra word at the start of the file giving the file length. Third, the code uses the first word of the midi file as the length of data to read from the file and put into memory to play. After poking around a bit in Wolfenstein and Keen I believe this is the same with IMF files, that is, ALL IMF files are type 0 as it were and the type 1s are read just like type 0s by the games (The first word is read as the amount of IMF data to copy into memory to play, this is then read as type 0.) I'm not quite sure what this does for the two types since type 1 is would essentially be a type 0 with a header and footer that are part of the AUDIO.xxx format, much like PC\adlib sounds can have the huffman lengths at the start. Are there any games that use 'individual' type 1 IMFs (Even if included as part of a group file. All I've seen are games like cosmo, where non-AUDIO IMFs are type 0.)

Should there be a Noah's Ark 3D page and should we add the midi note to the AUDIO format page? It seems that the format can hold any type of music file the game can read, not just IMFs. -- Levellass

: Yes it is known that the type-1 header might really be part of the AUDIO.xxx format but alas there were many type-1 files floating around the place (incorrectly extracted, you could argue) before this was realised, so the format variant is here to stay. It does have some advantages though (like tagging files with the song title) but I'm not sure whether anyone has figured out definitively whether the header (and footer, in the case of the Wolf3D files) belongs to the IMF or the AUDIO file. I guess you'd have to browse the game source code and see how the game uses the data to know for sure.

: As far as the MIDI goes, I believe the AUDIO.xxx file is just a container file like any other, capable of supporting any data at all. It's up to the game to decide how to use it. If anything this makes me think it would fit better if the AUDIO.xxx article was merely documenting the structure, with links to actual audio formats like PC SFX, Adlib SFX, IMF and MIDI and notes about which games make use of which formats.

: Oh and yes, by all means create a page for the new game. -- [[User:Malvineous|Malvineous]] 08:41, 3 February 2011 (GMT)

== Sound Files category ==

I don’t know why there’s a Sound Files category and also an Audio Files category... it seems redundant. I left those categories the way they are though.

Also, the [[File format data types]] page needs some signed ints, but I didn’t know what naming convention you wanted to use. I described something as an [[INT16LE]] on [[BMC Format]]. [[User:Yellowantphil|Yellowantphil]] 20:12, 11 September 2011 (GMT)

: Not sure about the Sound vs Audio - I use the term 'audio' to mean both sound and music, but you're right, if there are separate sound and music categories we don't really need an audio one as well. Feel free to update. [[INT16LE]] is perfectly fine too! I added a note to the data types page. -- [[User:Malvineous|Malvineous]] 22:30, 11 September 2011 (GMT)

== GamePage template ==

Should the GamePage template add the page to its own category? It seems a little odd that [[Wacky Wheels]] is not in the Wacky Wheels category. [[User:Yellowantphil|Yellowantphil]] 04:51, 16 September 2011 (GMT)
: I decided against this because there is a link to the game's page in the category intro at the top of the page. It seemed unnecessary having another link in amongst all the other pages. This was also because the game page was really only meant to be a summary, there wasn't supposed to be a huge amount of detail on it, only links to other pages with the detail (which then would appear in the category list.) I would imagine that, eventually, [[Wacky Wheels]] would be tweaked to move a lot of the content onto subpages. -- [[User:Malvineous|Malvineous]] 12:58, 16 September 2011 (GMT)

== Scope of the wiki ==

I don’t know how extensive you want the information to be on ModdingWiki... I added a few lists of audio and graphics files a while ago, and there will probably be other information that I’ll find out that’s potentially helpful for level editing but not directly related to it. I can move some information to my website if it starts to become out of scope for your wiki. I also sometimes end up documenting everything imaginable... there’s some minutiae on my website and possibly on your wiki that I ought to go through and delete. [[User:Yellowantphil|Yellowantphil]] 05:28, 10 October 2011 (GMT)

:Hmm, that's a difficult one - I'm always in favour of documenting more rather than less. Generally speaking if it's related to a game and it would help either a programmer writing a utility or a someone trying to change a game manually then it should be documented. About the only thing that comes to mind that's over documenting is when some small calculation is expressed in a couple of different programming languages, but I've left that in so people can just copy it rather than trying to figure it out from the text. But the [[Wacky Wheels]] page is probably the gold standard for what all wiki pages should look like :-) Do you have anything in particular you're unsure of whether it would fit here? -- [[User:Malvineous|Malvineous]] 10:07, 10 October 2011 (GMT)

::I was mainly thinking of the list of VOC files on [[Wacky Wheels Music and Sound Effects]] and the list of <tt>*.sp</tt> files on [[Wacky Wheels Graphics Formats]]. I have an expanded list of the <tt>*.sp</tt> files on my computer but it isn’t finished yet. I guess there isn’t all that much more Wacky Wheels information to be added to this wiki though. There is still some modding information on my website that ought to be moved over here, so that would take up another page or two. I’ve been lazy about doing Wacky Wheels stuff lately, but I might find some time for it this weekend.

::By the way, I guess that guy from Cascadia Games emailed you. It’s pretty interesting that WW might become an iPhone app. He told me that he was going to be using his own game engine, which sounds a lot easier than trying to get a hold of the WW source code and porting it. —[[User:Yellowantphil|Yellowantphil]] 16:46, 15 October 2011 (GMT)

::: I was going to say the list of VOCs might be overkill, but then the list of .sp files might be useful. To be honest, it's the sort of thing that you could probably omit if you were feeling lazy, but likewise I don't mind at all if you choose to include it, so since it's already there I'm happy to keep it.

::: Yes I did get an e-mail from Cascadia, I was going to pass along your details but it sounds like you're already aware of it! Using their own engine might make it a bit smoother than the original, as the jerkiness of turning is my only criticism of the game. -- [[User:Malvineous|Malvineous]] 00:14, 16 October 2011 (GMT)

== Wacky Wheels ==

Basically all of the WW modding information from my website is here now. I moved one page when I realized it should probably be capitalized to match the rest of the pages on this site... you can delete the redirect at [[Wacky Wheels high score files]] if you want to.

Now, I need to remove most of the modding information from my website and refer people here. Then we’ll have reached the glorious future where all WW modding information is in one place. I’m going to keep those two text files of notes on my website though—the information in them is disorganized and I think not 100% accurate, but they might have some information that isn’t here yet.

By the way, how’s Camoto going? I’m planning to use it to make a new WW level, but I won’t have time for it for a few more months. —[[User:Yellowantphil|Yellowantphil]]

: Sounds good! Thanks for all the effort you've put in by moving it across. I think Wacky Wheels is now the most completely documented game on the wiki! Also can't hurt leaving your own info up - sometimes it's nice to go back to the original source if something is unclear. Camoto's going well, but unfortunately I haven't had much time to work on it over the last few weeks. You probably won't be able to make much of a level until I add in the ability to select a tile from the tileset, but that's in progress and hopefully will be ready by the time you are! Keep me posted when you do start your level(s?) -- [[User:Malvineous|Malvineous]] 12:22, 2 February 2012 (GMT)

::Well, as I was reading some of the information on my website, I noticed that it isn’t written very well. I wrote those pages back when I had very little experience programming. Anyway, I’m planning to redesign my website soon, and this will save me from having to rewrite a few of those pages.

::The tile editor in Camoto as it is now is still certainly useful—I can add new tile types to a level using a binary editor and then move them around in Camoto. I think that it shouldn’t be too hard to make a new WW level using the Gimp and Camoto plus some binary editing. I recall having some problems with the route editor for the computer players, but I didn’t look into it at the time—I’ll let you know when I’m working with Camoto again, and I’ll try to come up with some useful bug reports or fixes if I run into problems. —[[User:Yellowantphil|Yellowantphil]] 14:06, 2 February 2012 (GMT)

User talk:Malvineous

2012-02-02T03:23:58Z

Yellowantphil: /* Wacky Wheels */ new section

Wacky Wheels

2012-02-02T03:07:45Z

Yellowantphil: /* Files not in wacky.dat */ changed links after moving other page

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFFFCC;" | A table of integers that influence where objects are drawn on the screen at different viewing angles. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>slp</tt>
| style="background: #FFFFCC;" | A table of integers that influence when objects are considered to be in your field of view. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>view</tt>
| style="background: #FFFFCC;" | A table of integers that influence the apparent distance of objects and other drivers. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [[wacky.cfg]].

|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. See [[Wacky Wheels High Score Files#Duck shoot|editing duck shoot high scores]].
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for single-player races. See [[Wacky Wheels High Score Files#Single-player race|editing single-player race high scores]].

|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. See [[Wacky Wheels High Score Files#Time trial|editing time trial scores]].
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels High Score Files

2012-02-02T03:05:02Z

Yellowantphil: moved Wacky Wheels high score files to Wacky Wheels High Score Files: I guess this should be capitalized

This page describes the high score file formats in [[Wacky Wheels]].

==Single-player race==
Single-player race high scores are saved in <tt>wacky1.hi</tt> for 12 hp engines and <tt>wacky2.hi</tt> (6 hp engines).

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>[[Wacky Wheels#File formats|wacky.dat]]</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.

Each file contains 144 of the following structures:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || unknown || A number between 1 and 6. I don’t think this number is used for anything.
|-
| [[INT16LE]] || racer || 0=Uno, 1=Sultan, 2=Morris, 3=Peggles, 4=Razer, 5=Ringo, 6=Blombo, 7=Tigi
|-
| [[INT16LE]] || score || Player’s score
|-
| [[char]][20] || date || The date, in the format <tt>01 SEP 1994</tt>, or whatever other text you want to enter. Should be null-terminated after 12 characters for the text to fit the screen.
|-
| [[char]][20] || name || The player’s name. 14 characters will fit on the screen.
|}

The structures come in groups of four, because the top four scores are displayed on each “famous drivers” screen. Every other group of four structures is unused.
* The first group of four structures give the four highest scores for the regular bronze courses, amateur class.
* The second group of four structures is unused.
* The third group is for the regular bronze courses, pro class.
* The fourth group is unused.

Next is regular bronze courses, champion class, followed by regular silver courses, amateur class, etc. After the regular gold courses, champion class, the bonus pack course high scores start.

==Duck shoot==
Duck shoot high scores are stored in <tt>wacky.dtt</tt>. If deleted, the file is created using default names and scores in <tt>ww.exe</tt>.

Each file contains four of the following structures:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[char]][20] || player || Player’s name
|-
| [[INT32LE]] || score || Number of points
|}

The four names and scores are displayed just before starting a duck shoot.

==Time trial==
The fastest time trial times are saved in <tt>wacky1.tim</tt> for 12 hp engines, and <tt>wacky2.tim</tt> for 6 hp engines.

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.

Each file contains 30 of the following structures:
{|class="wikitable"
! Data type !! Name !! Description
|-
| [[char]][20] || lap_name1 || Name of the driver with the best lap time. Needs to be null-terminated.
|-
| [[char]][20] || lap_name2 || Driver with the second best lap time
|-
| [[char]][20] || lap_name3 || Driver with the third best lap time
|-
| [[char]][20] || lap_name4 || Driver with the fourth best lap time
|-
| [[UINT32LE]] || lap_time1 || Time of the first driver, in tenths of a second. Maximum is one hour (36,000 tenths of a second)
|-
| [[UINT32LE]] || lap_time2 || Time of the second driver
|-
| [[UINT32LE]] || lap_time3 || Time of the third driver
|-
| [[UINT32LE]] || lap_time4 || Time of the fourth driver
|-
| [[char]][20] || overall_name || Name of the driver with the best time for the entire race
|-
| [[UINT32LE]] || overall_time || Best overall race time, in tenths of a second. Maximum one hour.
|}

The thirty structures are in this order:
* Regular bronze courses, tracks 1–5
* Regular silver courses
* Regular gold courses
* Bonus bronze courses
* Bonus silver courses
* Bonus bronze courses

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels High Score Files

2012-02-02T02:50:52Z

Yellowantphil: finished adding information from my website

This page describes the high score file formats in [[Wacky Wheels]].

==Single-player race==
Single-player race high scores are saved in <tt>wacky1.hi</tt> for 12 hp engines and <tt>wacky2.hi</tt> (6 hp engines).

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>[[Wacky Wheels#File formats|wacky.dat]]</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.

Each file contains 144 of the following structures:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || unknown || A number between 1 and 6. I don’t think this number is used for anything.
|-
| [[INT16LE]] || racer || 0=Uno, 1=Sultan, 2=Morris, 3=Peggles, 4=Razer, 5=Ringo, 6=Blombo, 7=Tigi
|-
| [[INT16LE]] || score || Player’s score
|-
| [[char]][20] || date || The date, in the format <tt>01 SEP 1994</tt>, or whatever other text you want to enter. Should be null-terminated after 12 characters for the text to fit the screen.
|-
| [[char]][20] || name || The player’s name. 14 characters will fit on the screen.
|}

The structures come in groups of four, because the top four scores are displayed on each “famous drivers” screen. Every other group of four structures is unused.
* The first group of four structures give the four highest scores for the regular bronze courses, amateur class.
* The second group of four structures is unused.
* The third group is for the regular bronze courses, pro class.
* The fourth group is unused.

Next is regular bronze courses, champion class, followed by regular silver courses, amateur class, etc. After the regular gold courses, champion class, the bonus pack course high scores start.

==Duck shoot==
Duck shoot high scores are stored in <tt>wacky.dtt</tt>. If deleted, the file is created using default names and scores in <tt>ww.exe</tt>.

Each file contains four of the following structures:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[char]][20] || player || Player’s name
|-
| [[INT32LE]] || score || Number of points
|}

The four names and scores are displayed just before starting a duck shoot.

==Time trial==
The fastest time trial times are saved in <tt>wacky1.tim</tt> for 12 hp engines, and <tt>wacky2.tim</tt> for 6 hp engines.

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.

Each file contains 30 of the following structures:
{|class="wikitable"
! Data type !! Name !! Description
|-
| [[char]][20] || lap_name1 || Name of the driver with the best lap time. Needs to be null-terminated.
|-
| [[char]][20] || lap_name2 || Driver with the second best lap time
|-
| [[char]][20] || lap_name3 || Driver with the third best lap time
|-
| [[char]][20] || lap_name4 || Driver with the fourth best lap time
|-
| [[UINT32LE]] || lap_time1 || Time of the first driver, in tenths of a second. Maximum is one hour (36,000 tenths of a second)
|-
| [[UINT32LE]] || lap_time2 || Time of the second driver
|-
| [[UINT32LE]] || lap_time3 || Time of the third driver
|-
| [[UINT32LE]] || lap_time4 || Time of the fourth driver
|-
| [[char]][20] || overall_name || Name of the driver with the best time for the entire race
|-
| [[UINT32LE]] || overall_time || Best overall race time, in tenths of a second. Maximum one hour.
|}

The thirty structures are in this order:
* Regular bronze courses, tracks 1–5
* Regular silver courses
* Regular gold courses
* Bonus bronze courses
* Bonus silver courses
* Bonus bronze courses

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels High Score Files

2012-02-01T04:17:59Z

Yellowantphil: Created page with "This page describes the high score file formats in Wacky Wheels. ==Single-player race== Single-player race high scores are saved in <tt>wacky1.hi</tt> for 12 hp engines and ..."

Wacky Wheels

2012-02-01T03:45:55Z

Yellowantphil: /* Files not in wacky.dat */ moved information to a new page

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFFFCC;" | A table of integers that influence where objects are drawn on the screen at different viewing angles. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>slp</tt>
| style="background: #FFFFCC;" | A table of integers that influence when objects are considered to be in your field of view. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>view</tt>
| style="background: #FFFFCC;" | A table of integers that influence the apparent distance of objects and other drivers. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [[wacky.cfg]].

|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. See [[Wacky Wheels high score files#Duck shoot|editing duck shoot high scores]].
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for single-player races. See [[Wacky Wheels high score files#Single-player race|editing single-player race high scores]].

|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. See [[Wacky Wheels high score files#Time trial|editing time trial scores]].
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Configuration Format

2012-02-01T03:28:59Z

Yellowantphil: added saved game category, although this isn't only a saved game format... hmm

This page describes the <tt>wacky.cfg</tt> file format used in [[Wacky Wheels]].

Most of the information in <tt>wacky.cfg</tt> can be set using the <tt>setup.exe</tt> program that ships with Wacky Wheels. <tt>Setup.exe</tt> can also generate a new <tt>wacky.cfg</tt> file. <tt>Wacky.cfg</tt> also contains saved game information.

==Editing saved games==
Wacky Wheels can store two saved games: a single player race and a two-player race. Each saved game can be enabled or disabled—if a game is enabled, then when selecting that race type from the Wacky Wheels main menu, you are prompted to either restore the saved game or start a new game.

The command-line program wwsave can edit Wacky Wheels saved games. It can be compiled for Windows or Linux, and presumably other operating systems including Mac:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]

Saved games are stored in <tt>wacky.cfg</tt> using [[INT32LE]] integers at the following offsets. '''P1''' designates player one, and '''P2''' designates player two.

{| class="wikitable"
!| Single-player race
!| Description
!| Two-player race
|-
| <tt>866</tt> || Saved game enabled (0=disabled, 1=enabled) || <tt>8DA</tt>
|-
| <tt>876</tt> || Race type (1=amateur, 2=pro, 3=champ, 4=time trial, 5=sort of like kid mode). If you set the race type to time trial, only the first six laps are recorded, but your overall time is for all laps. If the number of laps is less than six, any laps that you didn’t race have will get a time of zero seconds. || <tt>8EA</tt>
|-
| <tt>872</tt> || Number of laps. A zero lap race ends when you cross the finish line before the first lap. If you set the number of laps to a negative number, the race ends as soon as it starts, and you get first place. || <tt>8E6</tt>
|-
| <tt>958</tt> || Horsepower (1=12HP, 2=6HP) || <tt>95A</tt>
|-
| <tt>87A</tt> || Course group (1=bronze, 2=silver, 3=gold). || <tt>8EE</tt>
|-
| <tt>95C</tt> || Course pack (0=regular races, 3=bonus pack) || <tt>95E</tt>
|-
| <tt>87E</tt> || Course number (1–5) || <tt>8F2</tt>
|-
| <tt>86A</tt> and <tt>8A2</tt> || Your character type (0=Uno, 1=Sultan, 2=Morris, 3=Peggles, 4=Razer, 5=Ringo, 6=Blombo, 7=Tigi). Both of these bytes should be the same number. || '''P1:''' <tt>8DE</tt> and <tt>916</tt> '''P2:''' <tt>8E2</tt> and <tt>91A</tt>
|-
| <tt>8A6–8BE</tt> || Opponents’ character types. Use the numbers listed above. || <tt>91E–932</tt>
|-
| <tt>882</tt> || Your points || '''P1''': <tt>8F6</tt> '''P2:''' <tt>8FA</tt>
|-
| <tt>886–89E</tt> || Opponents’ points || <tt>8FE–912</tt>
|-
| <tt>8C2</tt> || Number of hedge hogs. You can’t save hedgehogs in a two player race. ||
|-
| <tt>8C6</tt> || Item held. (0=nothing, 3=fire, 4=devil pups, 5=bomb, 6=oil, 7=upside down hog, 8=ice). If you hit an upside down hog, your steering reverses, but the screen doesn’t turn upside down like it does in shootouts. Opponents spin out when they hit one. You can’t save an item in a two player race. ||
|-
| || Two-player race type (1=race head to head, 2=race with all cars) || <tt>94E</tt>
|-
|}

The information in the above table is an expanded and corrected version of the information in the [http://www.rinkworks.com/apogee/s/6.1.2.2.shtml Apogee FAQ].

[[Category:Wacky Wheels]]
[[Category:File Formats]]
[[Category:Saved Game Files]]

Wacky Wheels Configuration Format

2012-02-01T03:18:46Z

Yellowantphil: wacky.cfg information from my site

Wacky Wheels

2012-02-01T02:39:46Z

Yellowantphil: /* Files not in wacky.dat */ moving wwsave links to new page on wacky.cfg

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFFFCC;" | A table of integers that influence where objects are drawn on the screen at different viewing angles. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>slp</tt>
| style="background: #FFFFCC;" | A table of integers that influence when objects are considered to be in your field of view. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>view</tt>
| style="background: #FFFFCC;" | A table of integers that influence the apparent distance of objects and other drivers. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [[wacky.cfg]] for how to edit saved games.

|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [[Wacky Wheels high score files#Duck shoot|Editing duck shoot high scores]]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [[Wacky Wheels high score files#Single player race|Editing single player race high scores]]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [[Wacky Wheels high score files#Time trial|Editing time trial scores]]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels

2012-02-01T02:31:47Z

Yellowantphil: /* Files not in wacky.dat */ moving the rest of the information from my website to here

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFFFCC;" | A table of integers that influence where objects are drawn on the screen at different viewing angles. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>slp</tt>
| style="background: #FFFFCC;" | A table of integers that influence when objects are considered to be in your field of view. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>view</tt>
| style="background: #FFFFCC;" | A table of integers that influence the apparent distance of objects and other drivers. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [[wacky.cfg]] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [[Wacky Wheels high score files#Duck shoot|Editing duck shoot high scores]]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [[Wacky Wheels high score files#Single player race|Editing single player race high scores]]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [[Wacky Wheels high score files#Time trial|Editing time trial scores]]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

User talk:Malvineous

2011-10-15T16:46:06Z

Yellowantphil: /* Scope of the wiki */

User talk:Malvineous

2011-10-10T05:28:33Z

Yellowantphil:

User talk:Malvineous

2011-10-10T05:22:59Z

Yellowantphil: /* Scope of the wiki */ new section

Wacky Wheels Graphics Formats

2011-09-25T08:08:12Z

Yellowantphil: formatting

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Many of the graphics in Wacky Wheels are in [[PCX Format]]. The uses of most PCX files are self-explanatory.The files <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described below. PCX graphics can be edited in many image editors, but you need to pay attention to the color palettes used. Details are in the [[#Color palettes|color palettes]] section below.

===Tile appearance and properties===
* <tt>a_f*.pcx</tt>: Tile graphics
* <tt>a_ma*.pcx</tt>: Selects tile properties for each pixel in each tile of the tile graphics files
* ''n''<tt>.gam</tt>: Chooses the primary and secondary tile graphics files and property files (among other things) for track ''n''
* ''n''<tt>.sin</tt>: Sets tile properties 0 and 1 for each tile in track ''n''

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (<tt>a_f*.pcx</tt>) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles, each 32×32 pixels. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (<tt>a_ma*.pcx</tt>) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track ''n'', any pixel in tile ''m'' that is color #0 will have property #0 specified in struct ''m'' of the file ''n''<tt>.sin</tt>; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

===Color palettes===
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique.

== Sprites ==
=== <tt>sprite.atr</tt> ===
The file <tt>sprite.atr</tt> is the index of all of the sprites that can be used as objects in the game maps. The first two bytes of this file are an [[INT16LE]] giving the number of structs that follow. Each struct is 40 bytes long and has this format:

{| style="float: left;" class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || type || Type of item pickup. See table.
|-
| [[INT16LE]] || unknown || No apparent use. Always 0x0a.
|-
| [[INT16LE]] || width1 || Sprite width in pixels
|-
| [[INT16LE]] || height1 || Sprite height in pixels
|-
| [[INT16LE]] || width2 || Always equal to <tt>width1</tt>.
|-
| [[INT16LE]] || height2 || Always equal to <tt>height2</tt>.
|-
| [[INT16LE]] || size_index || 1 if size is 28×28; 2 if size is 14×28; 3 if size is 32×24. Other values are unknown.
|-
| [[INT16LE]] || frames || Number of frames in sprite file (for animation)
|-
| [[char]][24] || filename || Name of the file containing the sprite
|}

{| style="white-space: nowrap;" class="wikitable"
! Index !! Item pickup type
|-
| 0 || None (not an item pickup)
|-
| 1 || Tires (used when you run over a stack of tires)
|-
| 2 || Four hedgehogs
|-
| 3 || Fireballs
|-
| 4 || Devil pups
|-
| 5 || Bomb
|-
| 6 || Oil slick
|-
| 7 || Upside down hog
|-
| 8 || Ice cube
|}

Setting <tt>size_index</tt> = 4 appears to work but I haven’t figured out what size it selects or how high the size index goes.

Changing <tt>width2</tt> and <tt>height2</tt> doesn’t appear to have any effect.

The file name will be no more than 12 characters long (an 8.3 character DOS file name). The remaining bytes in the string are filled with zeros.
Sprites are placed on the map using their index in the <tt>sprite.atr</tt> file. The first sprite file listed has index 0. See [[Wacky Wheels Track Format#Where objects are placed – *.spw|Where objects are placed – <tt>*.spw</tt>]].

The default <tt>sprite.atr</tt> file lists 36 files. The tables below list what sprites are in each <tt>*.sp</tt> file listed, and their index in <tt>sprite.atr</tt>. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in <tt>sprite.atr</tt>.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrel
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

=== <tt>*.sp</tt> ===
The <tt>*.sp</tt> sprite files are raw image data (8bpp, no header or image size). Each byte is a pixel, and the value of the byte gives the index to use in the [[#Color palettes|track’s palette]].

If your image editor supports reading raw image data, you can open the <tt>*.sp</tt> files by specifying the width and height, 8 bits per pixel, indexed colors, and then applying the appropriate color palette. Then rotate the image 90° clockwise and flip the image horizontally. Some <tt>*.sp</tt> files have multiple sprites of varying widths, so you’ll need to specify a file offset and length along with the width and height.

To use a sprite file as an object on the track, it needs to be listed in [[#sprite.atr|sprite.atr]].

== Horizon graphics – <tt>*.par</tt> ==
The <tt>*.par</tt> files contain the graphics to draw on the horizon (such as buildings or mountains). Like the <tt>[[#*.sp|*.sp]]</tt> files, they are raw image data, where each byte is a pixel and specifies which color palette index to use. The color palette used is the main track [[#Color palettes|color palette]]. Each <tt>*.par</tt> file is 640×40 pixels. Unlike the <tt>*.sp</tt> files, they do not require rotation or flipping when opening them as raw image data in an image editor.

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels

2011-09-25T04:05:53Z

Yellowantphil: /* Files in wacky.dat */ described and added links for a few files

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFFFCC;" | A table of integers that influence where objects are drawn on the screen at different viewing angles. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>slp</tt>
| style="background: #FFFFCC;" | A table of integers that influence when objects are considered to be in your field of view. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>view</tt>
| style="background: #FFFFCC;" | A table of integers that influence the apparent distance of objects and other drivers. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See [[Miscellaneous Wacky Wheels File Formats#Tabulated data for drawing the screen|Tabulated data for drawing the screen]].
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Miscellaneous Wacky Wheels File Formats

2011-09-25T04:05:11Z

Yellowantphil: added a few other files that influence the game perspective

This page describes a number of [[Wacky Wheels]] file formats that are difficult to categorize.

== Tabulated data for drawing the screen ==
The files in this section contain only tables of numbers used when drawing objects and tiles on the screen. Editing these files changes the viewing perspective of the game.

=== <tt>ndist</tt> ===
This file contains a table of [[INT16LE]] integers. If you convert each integer to a decimal number and write them to a file, 70 integers to a line, then each column of numbers describes a function. They resemble parabolas but I couldn’t find a good fit line. If you multiply all the numbers in the file by a constant factor, then the objects in the game are drawn in the wrong position from certain viewing angles.

=== <tt>slp</tt> ===
This file contains a table of [[INT16LE]] integers. I haven’t tried plotting them yet. If you change the values, objects won’t be drawn when viewed from certain angles. This file may tell the game when a certain object is in the player’s field of view and therefore needs to be drawn.

=== <tt>view</tt> ===
This file contains 320 [[INT16LE]] integers. The integers describe a section of a parabola. The numbers in this file influence the apparent distance of objects and other drivers.

=== <tt>trig.dat</tt> ===
This file contains only a series of (x, y) points that describe a circle of radius 65,535. Each (x, y) pair is described with two signed integers:

{|class="wikitable"
!Data type!!Description
|-
| [[INT32LE]] Xpos || X-position on the circle
|-
| [[INT32LE]] Ypos || Y-position on the circle
|}

The first 960 pairs describe the top half of the circle, and the last 960 pairs describe the bottom half.

If you multiply every number in this file by a constant factor, your vehicle’s size changes. If you multiply the values by 1.2, for example, you can drive faster and see farther away (extending to the black area beyond the edge of the map). Multiplying by a factor less than one shrinks your vehicle.

== <tt>wacky.ing</tt> ==
Most of this file looks like an unused high score file, similar in format to <tt>[[Wacky Wheels#Files not in wacky.dat|wacky*.hi]]</tt>. It consists of structs that are 46 bytes long containing some text (“<tt>KNOCK ME OFF!</tt>” and “<tt>MAR 1994”</tt>) and other data. I don’t think this data is used.

The first 66 bytes of this file are unknown data. The game won’t load unless at least the first 28 bytes are present. At least these first 28 bytes appear to be signed integers ([[INT32LE]]). The sixth and seventh integers in the file (offsets 0x14 and 0x18) are read when allocating memory. If you change either of these integers to –100, for example, the game will fail to start, and will print how many bytes of memory it allocated and state that it needed an extra –100 bytes of memory.

Most likely nothing in this file will need to be changed to edit levels.

== Devil motion – <tt>gig.mov</tt> ==
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (x, y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (x, y) position for about 0.1 seconds. Once there are no more (x, y) pairs, the devil disappears in a puff of smoke.

== Changing go kart/lawnmower speed – <tt>*.tab</tt> ==
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels Graphics Formats

2011-09-25T01:27:41Z

Yellowantphil: reorganizing a little

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Many of the graphics in Wacky Wheels are in [[PCX Format]]. The uses of most PCX files are self-explanatory.The files <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described below. PCX graphics can be edited in many image editors, but you need to pay attention to the color palettes used. Details are in the [[#Color palettes|color palettes]] section below.

===Tile appearance and properties===
* <tt>a_f*.pcx</tt>: Tile graphics
* <tt>a_ma*.pcx</tt>: Selects tile properties for each pixel in each tile of the tile graphics files
* ''n''<tt>.gam</tt>: Chooses the primary and secondary tile graphics files and property files (among other things) for track ''n''
* ''n''<tt>.sin</tt>: Sets tile properties 0 and 1 for each tile in track ''n''

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (<tt>a_f*.pcx</tt>) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles, each 32×32 pixels. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (<tt>a_ma*.pcx</tt>) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track ''n'', any pixel in tile ''m'' that is color #0 will have property #0 specified in struct ''m'' of the file ''n''<tt>.sin</tt>; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

===Color palettes===
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==
=== <tt>sprite.atr</tt> ===
The file <tt>sprite.atr</tt> is the index of all of the sprites that can be used as objects in the game maps. The first two bytes of this file are an [[INT16LE]] giving the number of structs that follow. Each struct is 40 bytes long and has this format:

{| style="float: left;" class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || type || Type of item pickup. See table.
|-
| [[INT16LE]] || unknown || No apparent use. Always 0x0a.
|-
| [[INT16LE]] || width1 || Sprite width in pixels
|-
| [[INT16LE]] || height1 || Sprite height in pixels
|-
| [[INT16LE]] || width2 || Always equal to <tt>width1</tt>.
|-
| [[INT16LE]] || height2 || Always equal to <tt>height2</tt>.
|-
| [[INT16LE]] || size_index || 1 if size is 28×28; 2 if size is 14×28; 3 if size is 32×24. Other values are unknown.
|-
| [[INT16LE]] || frames || Number of frames in sprite file (for animation)
|-
| [[char]][24] || filename || Name of the file containing the sprite
|}

{| style="white-space: nowrap;" class="wikitable"
! Index !! Item pickup type
|-
| 0 || None (not an item pickup)
|-
| 1 || Tires (used when you run over a stack of tires)
|-
| 2 || Four hedgehogs
|-
| 3 || Fireballs
|-
| 4 || Devil pups
|-
| 5 || Bomb
|-
| 6 || Oil slick
|-
| 7 || Upside down hog
|-
| 8 || Ice cube
|}

Setting <tt>size_index</tt> = 4 appears to work but I haven’t figured out what size it selects or how high the size index goes.

Changing <tt>width2</tt> and <tt>height2</tt> doesn’t appear to have any effect.

The file name will be no more than 12 characters long (an 8.3 character DOS file name). The remaining bytes in the string are filled with zeros.
Sprites are placed on the map using their index in the <tt>sprite.atr</tt> file. The first sprite file listed has index 0. See [[Wacky Wheels Track Format#Where objects are placed – *.spw|Where objects are placed – <tt>*.spw</tt>]].

The default <tt>sprite.atr</tt> file lists 36 files. The tables below list what sprites are in each <tt>*.sp</tt> file listed, and their index in <tt>sprite.atr</tt>. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in <tt>sprite.atr</tt>.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrel
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

=== <tt>*.sp</tt> ===
The <tt>*.sp</tt> sprite files are raw image data (8bpp, no header or image size). Each byte is a pixel, and the value of the byte gives the index to use in the [[#Color palettes|track’s palette]].

If your image editor supports reading raw image data, you can open the <tt>*.sp</tt> files by specifying the width and height, 8 bits per pixel, indexed colors, and then applying the appropriate color palette. Then rotate the image 90° clockwise and flip the image horizontally. Some <tt>*.sp</tt> files have multiple sprites of varying widths, so you’ll need to specify a file offset and length along with the width and height.

To use a sprite file as an object on the track, it needs to be listed in [[#sprite.atr|sprite.atr]].

== Horizon graphics – <tt>*.par</tt> ==
The <tt>*.par</tt> files contain the graphics to draw on the horizon (such as buildings or mountains). Like the <tt>[[#*.sp|*.sp]]</tt> files, they are raw image data, where each byte is a pixel and specifies which color palette index to use. The color palette used is the main track [[#Color palettes|color palette]]. Each <tt>*.par</tt> file is 640×40 pixels. Unlike the <tt>*.sp</tt> files, they do not require rotation or flipping when opening them as raw image data in an image editor.

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels

2011-09-24T22:06:08Z

Yellowantphil: /* Files in wacky.dat */ changed a link; formatting

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See <tt>[[Miscellaneous Wacky Wheels File Formats#trig.dat|trig.dat]]</tt>.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels

2011-09-24T21:57:44Z

Yellowantphil: /* Files in wacky.dat */ links to new page

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See <tt>[[Miscellaneous Wacky Wheels File Formats#trig.dat|trig.dat]]</tt>.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>. See also [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]]. See also [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]]. See also [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]]. See also [[Wacky Wheels Music and Sound Effects]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Music and Sound Effects

2011-09-24T21:57:04Z

Yellowantphil: Created page with "This page describes the files containing music and sound effects in Wacky Wheels. == Music == Wacky Wheels store all of its music in two formats: AdLib KLM Format and [[..."

This page describes the files containing music and sound effects in [[Wacky Wheels]].

== Music ==
Wacky Wheels store all of its music in two formats: AdLib [[KLM Format]] and [[MID Format|MIDI Format]]. The MIDI files are played if you select “General MIDI” as your music device in <tt>setup.exe</tt>; the KLM files are used otherwise. To hear the MIDI files being played, you need to use a MIDI synthesizer (either in software or hardware).

[[Camoto]] has partial support for KLM files. There are many editors available for MIDI files.

There was one song written for Wacky Wheels that was not used or included in the game, named ''Everything''. The MIDI version of this song is available at Phil’s [http://yellowantphil.com/wacky_wheels/music.php Wacky Wheels Music] page. That page also lists where in the game each music file is used.

== Sound effects ==
Each sound effect in Wacky Wheels is stored in either one or three file formats. All sound effects are stored in [[VOC Format]]. Most sound effects are also stored as PC speaker sound effects and as AdLib sound effects.

Each of the 36 VOC format sound effects are stored in <tt>[[DAT Format (Wacky Wheels)|wacky.dat]]</tt>. There are 26 sound effects in each of the other two formats. These files are stored in <tt>audiot.fx</tt>, which is an [[AudioT Format]] file. The header for this file is stored in <tt>audiohed.fx</tt> Both <tt>audiot.fx</tt> and <tt>audiohed.fx</tt> are stored in <tt>wacky.dat</tt>. [[User:Yellowantphil|Phil]] has a rudimentary extractor for this file if you want it.

The PC speaker sound effects are used if you select “PC Speaker” as your Sound fx device in <tt>setup.exe</tt>. When selecting SoundBlaster, Sound Source or Gravis Ultrasound, the <tt>*.voc</tt> files are used. I was unable to test the Pro AudioSpectrum option. I don’t know if the AdLib sound effects are ever used.

When replacing <tt>*.voc</tt> files, the new file needs to be no longer in file size than the old file.

The tables below briefly describe each VOC file. The index listed is the index of the corresponding PC speaker file in <tt>audiot.fx</tt>. Files are numbered 0–25. The AdLib files have the same index and are found in the second section of <tt>audiot.fx</tt>.

{| style="float: left;" class="wikitable"
! File name !! Index !! Description
|-
| backfire.voc || Unknown || Noise when you start accelerating
|-
| belch.voc || Unknown || The Dopefish’s sound
|-
| bell.voc || Unknown || Last lap warning bell
|-
| blombo.voc || Unknown || Blombo’s sound
|-
| boom.voc || Unknown || Explosion in two-player shootout
|-
| clang.voc || Unknown || Clang
|-
| drop.voc || Unknown || Sound when dropping an item
|-
| flame.voc || Unknown || Sound when firing fireballs
|-
| gig1.voc || Unknown || Giggle key #1 sound
|-
| gig2.voc || Unknown || Giggle key #2 sound
|-
| gig3.voc || Unknown || Giggle key #3 sound
|-
| gig4.voc || Unknown || Giggle key #4 sound
|-
| gig5.voc || Unknown || Giggle keys #5 and 6, last lap devil
|-
| glass.voc || Unknown || Breaking glass
|-
| hog.voc || Unknown || Sound when firing hedgehogs or ice cubes
|-
| horn.voc || Unknown || Alarm when driving underwater
|-
| horn1.voc || Unknown || Horn when honking at other drivers
|-
| morris.voc || Unknown || Morris’s sound
|}

{|class="wikitable"
! File name !! Index !! Description
|-
| motor.voc || Unknown || Engine noise. Playback speed is shifted according to driving speed.
|-
| no.voc || Unknown || Out of ammo noise
|-
| pass.voc || Unknown || Noise when drivers pass you
|-
| peggles.voc || Unknown || Peggles’ sound
|-
| plip.voc || Unknown ||
|-
| puf.voc || Unknown || Sound when a driver is hit
|-
| quack.voc || Unknown || Duck quack
|-
| razer.voc || Unknown || Razer’s sound
|-
| ringo.voc || Unknown || Ringo’s sound
|-
| skid.voc || Unknown || Tires skidding
|-
| splash.voc || Unknown || Splash
|-
| stall1.voc || Unknown || Stalled engine (from ice cube)
|-
| start.voc || Unknown || Lion’s roar
|-
| sultan.voc || Unknown || Sultan’s sound
|-
| swipe.voc || Unknown || Noise when hitting another driver
|-
| tigi.voc || Unknown || Tigi’s sound
|-
| uno.voc || Unknown || Uno’s sound
|-
| warp.voc || Unknown || Jump/turbo/Apogee splash screen
|}

[[Category:Wacky Wheels]]
[[Category:File Formats]]

DAT Format (Wacky Wheels)

2011-09-24T19:55:27Z

Yellowantphil: mentioned wacky.lid; minor formatting

The '''DAT format''' is used to store most of the data for [[Wacky Wheels]]. Unfortunately the format has no signature and a generic filename extension (.dat) so automatic detection of these files is difficult.

In [http://yellowantphil.com/wacky_wheels/downloads/1ww10.zip Wacky Wheels 1.0] (a pre-release version of Wacky Wheels), this file was named <tt>WACKY.LID</tt>.

Wacky Wheels does not check the current directory for files before falling back to the DAT file, so any changed files must be merged into the DAT file before the game will see them.

== File format ==

=== Signature ===

There is no signature for this format. One method to identify files is to read in the file entries (failing if the end of the file is reached early) and confirm that each filename only consists of ASCII characters or nulls, and each file offset plus its size is less than the total size of the DAT file. It is extremely unlikely that this method would incorrectly identify a file.

=== Header ===

The file starts with a single field indicating the number of files present.

{|class="wikitable"
!Data type!!Description
|-
|UINT16LE numFiles||File count
|}

=== File entry ===

After the two-byte header, the following structure is repeated <tt>numFiles</tt> times. As each entry includes both an offset and a size, it is possible (in theory) for two different files to share the same data, and to insert “hidden” data between files.

{|class="wikitable"
!Data type!!Description
|-
|BYTE filename[14]||Filename (8.3, 12 chars including dot, null padded to 14 chars)
|-
|UINT32LE size||File size
|-
|UINT32LE offset||File offset (see below)
|}

The file offsets don’t include the two-byte file count in the header, so an <tt>offset</tt> of 10 means the file actually starts at 12 bytes from the beginning of the DAT file.

== Tools ==

{{BeginFileFormatTools|Type=group}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| canExtract = Yes
| canDecompress = N/A
| canCreate = Yes
| canModify = Yes
| canCompress = N/A
| editHidden = No
| editMetadata = N/A
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| canExtract = Yes
| canDecompress = N/A
| canCreate = No
| canModify = Yes
| canCompress = N/A
| editHidden = No
| editMetadata = N/A
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor wextract]
| Platform = DOS
| canExtract = Yes
| canDecompress = N/A
| canCreate = No
| canModify = No
| canCompress = N/A
| editHidden = No
| editMetadata = N/A
}}
{{EndFileFormatTools}}

[[Category:File Formats]]
[[Category:Group Files]]
[[Category:Group Files supporting hidden data]]


[[Category:Wacky Wheels]]

KLM Format

2011-09-24T19:55:11Z

Yellowantphil: hyphens, dashes, minus signs, typographic quotes vs. typewriter quotes...

{{NeedMoreInfo}}

The '''KLM Format''' is used by [[Wacky Wheels]] to store Adlib music tracks. It is probably named after Mark Klem, the Wacky Wheels composer.

== File format ==

The file is structured as follows.

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] tempo || Playback speed in ticks per second
|-
| [[UINT8]] unknown || Unknown
|-
| [[UINT16LE]] offNotes || Offset of song data
|-
| [[BYTE]][] inst || Instrument data
|-
| [[BYTE]][] notes || Song data
|}

=== Instrument block ===

The instrument block contains all the instruments used in the song. Each instrument is 11 bytes long, and is stored one after the other, in the following structure.

{|class="wikitable"
! Data type !! OPL base register !! Description
|-
| [[UINT8]] iModScale || 0x40 || Modulator key scaling/output level
|-
| [[UINT8]] iCarScale || 0x43 || Carrier key scaling/output level
|-
| [[UINT8]] iModAttack || 0x60 || Modulator attack/decay level
|-
| [[UINT8]] iCarAttack || 0x63 || Carrier attack/decay level
|-
| [[UINT8]] iModSustain || 0x80 || Modulator sustain/release level
|-
| [[UINT8]] iCarSustain || 0x83 || Carrier sustain/release level
|-
| [[UINT8]] iModChar || 0x20 || Modulator characteristic (Mult, KSR, EG, VIB and AM flags)
|-
| [[UINT8]] iCarChar || 0x23 || Carrier characteristic (Mult, KSR, EG, VIB and AM flags)
|-
| [[UINT8]] iModWaveSel || 0xE0 || Modulator wave select
|-
| [[UINT8]] iCarWaveSel || 0xE3 || Carrier wave select
|-
| [[UINT8]] iFeedback || 0xC0 || Feedback/connection
|}

Song data follows the instrument data.

=== Song data ===

The song data appears to be a custom event-style structure, superficially similar to MIDI. Each ''command byte'' is followed by a variable number of ''data bytes'' whose purpose depends on the command. The lower four bits are used for the channel (so command bytes of 0x30 and 0x31 perform the same command on the first and second channels, respectively.)

{|class="wikitable"
! Command byte !! # of data bytes !! Description
|-
| 0x00 || 0 || Note off
|-
| 0x10 || 0/2 || Note on with frequency
|-
| 0x20 || 1 || Volume
|-
| 0x30 || 1 || Set instrument
|-
| 0x40 || 0 || Note on
|-
| 0xFD || 1 || Delay
|-
| 0xFE || 2 || Long delay
|-
| 0xFF || 0 || End of song
|}

==== 0x00: Note off ====

Turn the note on the current channel off (this sets the ''keyon'' bit to 0, on OPL base reg 0xB0).

==== 0x10: Note on with frequency ====

Plays a note at the given frequency.

For channels 0–5 inclusive (i.e. command bytes 0x10 to 0x15), the first data byte is written to OPL base register 0xA0, and the second data byte is written to OPL base register 0xB0. As an example, if the command byte was 0x12 (set frequency on channel 2) then the two data bytes are written to register 0xA2 and 0xB2.

For channels 6–10 inclusive, there are no data bytes. Instead, these activate the OPL rhythm-mode percussion channels without setting a frequency:

{|class="wikitable"
! Command byte !! OPL 0xBD bit !! Instrument
|-
| 0x16 || 5 || Bass drum
|-
| 0x17 || 4 || Snare drum
|-
| 0x18 || 3 || Tom tom
|-
| 0x19 || 2 || Top cymbal
|-
| 0x1A || 1 || Hi-hat
|}

==== 0x20: Volume ====

This command sets the velocity of subsequent notes on the channel. As with MIDI, the single data value ranges between 0 (silence) and 127 (full volume). Wacky Wheels uses this value to write the appropriate output level to the OPL chip, using the following formula:

:''value'' = (127 − ''databyte'') / 2

Thus a data byte of 0x58 results in the value 0x13 being written to the OPL chip. The value is written to the carrier operator on OPL base reg 0x40 (so channel 0 will actually write to reg 0x43.)

==== 0x30: Set instrument ====

This command causes the instrument settings to be copied into the corresponding OPL registers for the channel. A data byte of 0x00 selects the first instrument in the instrument block.

==== 0x40: Note on ====

Turn the note on the current channel on, at the last set frequency (this sets the ''keyon'' bit to 1, on OPL base reg 0xB0).

==== 0xFD: Delay ====

This command causes a delay. The single data byte indicates how many ticks to wait for. Combined with the ticks-per-second tempo field in the header, the actual delay time can be calculated. With a data byte of 0x10 (delay for 16 ticks) and a tempo of 0x138 (312 ticks per second) the delay should be 16 ÷ 312 = 0.0512 seconds (51.2ms).

==== 0xFE: Long delay ====

This command is the same as 0xFD except it is followed by a [[UINT16LE]] delay value rather than [[UINT8]].

==== 0xFF: End of song ====

This command has no delay bytes and signifies the end of the song data.

== Tools ==

* [[Camoto]] can just about load KLM files (some instruments are a bit off)

== Credits ==

This file format was reverse engineered by [[User:Malvineous|Malvineous]]. If you find this information helpful in a project you’re working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

[[Category:Adlib]]
[[Category:Music Files]]
[[Category:File Formats]]


[[Category:Wacky Wheels]]

BMC Format

2011-09-24T19:55:01Z

Yellowantphil: formatting

BMC format is a file format used in [[Wacky Wheels]] to control player one during demo mode. Seen while viewing ordering instructions and game instructions, or when you don’t press any keys at the main menu for a while. There are six BMC files in <tt>[[DAT Format (Wacky Wheels)|wacky.dat]]</tt>: <tt>1.bmc</tt> through <tt>5.bmc</tt> control the main player for Regular Bronze Wheels tracks 1–5, and <tt>7.bmc</tt> is for Regular Silver Wheels track 2.

Each action performed is described using a three-byte struct. The first two bytes of the file are a [[UINT16LE]] giving the number of structs in the file.

Format of the structs:
{|class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || duration || Minimum duration is 0x01. 0x100 is about 23 seconds long. Note that this is a signed value so the maximum duration is 0x7FFF, or about 49 minutes. Negative or zero duration work the same way as 0x01 duration.
|-
| [[UINT8]] || action || See table below.
|}

At some point, the demo game will start over, or skip to the next track. If your BMC file doesn’t end with an End Sequence action (0x40), the game may start playing back actions read previously from another file. I don’t know how many actions you can fit into the allotted time, or whether the time would be extended if the file hasn’t been performed completely.

=== Actions ===

Each action is a bitfield composed of one or more actions below. For example, to do a right handbrake turn, combine steer-right (0x02) and handbrake (0x20) to have an action of 0x22. Some of the combinations of actions don’t make sense or aren’t very useful (such as steering left and right at the same time.)

None of the combinations trigger a jump or turbo, and the jump and turbo [http://yellowantphil.com/wacky_wheels/startup.php start-up codes] have no effect on the computer player. However, if you set a high enough duration for one of the actions where you fire, then you’ll get an ice cube, so the [http://yellowantphil.com/wacky_wheels/morecheats.php registered version cheat] works for the computer player.

The fire, ice and hog start-up codes also work. If you use one of these codes and don’t fire off some of your ammo, you’ll bounce off of the hedgehog packs and other objects on the track. To make the player follow the same course whether or not these cheats are enabled, make sure that you have no more than 98 shots whenever you’re about to drive over an object to pick up.

{|class="wikitable"
! Binary !! Hex !! Action
|-
| 00000000 || 00 || Do nothing
|-
| 00000001 || 01 || Steer left
|-
| 00000010 || 02 || Steer right
|-
| 00000100 || 04 || Accelerate
|-
| 00001000 || 08 || Fire
|-
| 00010000 || 10 || Brake
|-
| 00100000 || 20 || Hand brake turn left
|-
| 01000000 || 40 || End sequence and go back to the start
|-
| 10000000 || 80 || Unused?
|}

== Credits ==

This format was reverse engineered by [http://yellowantphil.com/wacky_wheels/ Phil Carter] and Klas Arvidsson. If you find this information helpful in a project you’re working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

[[Category:Wacky Wheels]]
[[Category:Macro Files]]
[[Category:File Formats]]

Wacky Wheels Graphics Formats

2011-09-24T19:39:22Z

Yellowantphil: /* sprite.atr */ moved a table

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Many of the graphics in Wacky Wheels are in [[PCX Format]]. The uses of most PCX files are self-explanatory. Some files need further explanation:
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described below.

==Tile appearance and properties==
* <tt>a_f*.pcx</tt>: Tile graphics
* <tt>a_ma*.pcx</tt>: Selects tile properties for each pixel in each tile of the tile graphics files
* ''n''<tt>.gam</tt>: Chooses the primary and secondary tile graphics files and property files (among other things) for track ''n''
* ''n''<tt>.sin</tt>: Sets tile properties 0 and 1 for each tile in track ''n''

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (<tt>a_f*.pcx</tt>) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles, each 32×32 pixels. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (<tt>a_ma*.pcx</tt>) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track ''n'', any pixel in tile ''m'' that is color #0 will have property #0 specified in struct ''m'' of the file ''n''<tt>.sin</tt>; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==
=== <tt>sprite.atr</tt> ===
The file <tt>sprite.atr</tt> is the index of all of the sprites that can be used as objects in the game maps. The first two bytes of this file are an [[INT16LE]] giving the number of structs that follow. Each struct is 40 bytes long and has this format:

{| style="float: left;" class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || type || Type of item pickup. See table.
|-
| [[INT16LE]] || unknown || No apparent use. Always 0x0a.
|-
| [[INT16LE]] || width1 || Sprite width in pixels
|-
| [[INT16LE]] || height1 || Sprite height in pixels
|-
| [[INT16LE]] || width2 || Always equal to <tt>width1</tt>.
|-
| [[INT16LE]] || height2 || Always equal to <tt>height2</tt>.
|-
| [[INT16LE]] || size_index || 1 if size is 28×28; 2 if size is 14×28; 3 if size is 32×24. Other values are unknown.
|-
| [[INT16LE]] || frames || Number of frames in sprite file (for animation)
|-
| [[char]][24] || filename || Name of the file containing the sprite
|}

{| style="white-space: nowrap;" class="wikitable"
! Index !! Item pickup type
|-
| 0 || None (not an item pickup)
|-
| 1 || Tires (used when you run over a stack of tires)
|-
| 2 || Four hedgehogs
|-
| 3 || Fireballs
|-
| 4 || Devil pups
|-
| 5 || Bomb
|-
| 6 || Oil slick
|-
| 7 || Upside down hog
|-
| 8 || Ice cube
|}

Setting <tt>size_index</tt> = 4 appears to work but I haven’t figured out what size it selects or how high the size index goes.

Changing <tt>width2</tt> and <tt>height2</tt> doesn’t appear to have any effect.

The file name will be no more than 12 characters long (an 8.3 character DOS file name). The remaining bytes in the string are filled with zeros.
Sprites are placed on the map using their index in the <tt>sprite.atr</tt> file. The first sprite file listed has index 0. See [[Wacky Wheels Track Format#Where objects are placed – *.spw|Where objects are placed – <tt>*.spw</tt>]].

The default <tt>sprite.atr</tt> file lists 36 files. The tables below list what sprites are in each <tt>*.sp</tt> file listed, and their index in <tt>sprite.atr</tt>. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in <tt>sprite.atr</tt>.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrel
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

=== <tt>*.sp</tt> ===
The <tt>*.sp</tt> sprite files are raw image data (8bpp, no header or image size). Each byte is a pixel, and the value of the byte gives the index to use in the [[#Color palettes|track’s palette]].

If your image editor supports reading raw image data, you can open the <tt>*.sp</tt> files by specifying the width and height, 8 bits per pixel, indexed colors, and then applying the appropriate color palette. Then rotate the image 90° clockwise and flip the image horizontally. Some <tt>*.sp</tt> files have multiple sprites of varying widths, so you’ll need to specify a file offset and length along with the width and height.

To use a sprite file as an object on the track, it needs to be listed in [[#sprite.atr|sprite.atr]].

== Horizon graphics – <tt>*.par</tt> ==
The <tt>*.par</tt> files contain the graphics to draw on the horizon (such as buildings or mountains). Like the <tt>[[#*.sp|*.sp]]</tt> files, they are raw image data, where each byte is a pixel and specifies which color palette index to use. The color palette used is the main track [[#Color palettes|color palette]]. Each <tt>*.par</tt> file is 640×40 pixels. Unlike the <tt>*.sp</tt> files, they do not require rotation or flipping when opening them as raw image data in an image editor.

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels Graphics Formats

2011-09-24T19:26:53Z

Yellowantphil: added *.par. also minor formatting

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Many of the graphics in Wacky Wheels are in [[PCX Format]]. The uses of most PCX files are self-explanatory. Some files need further explanation:
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described below.

==Tile appearance and properties==
* <tt>a_f*.pcx</tt>: Tile graphics
* <tt>a_ma*.pcx</tt>: Selects tile properties for each pixel in each tile of the tile graphics files
* ''n''<tt>.gam</tt>: Chooses the primary and secondary tile graphics files and property files (among other things) for track ''n''
* ''n''<tt>.sin</tt>: Sets tile properties 0 and 1 for each tile in track ''n''

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (<tt>a_f*.pcx</tt>) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles, each 32×32 pixels. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (<tt>a_ma*.pcx</tt>) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track ''n'', any pixel in tile ''m'' that is color #0 will have property #0 specified in struct ''m'' of the file ''n''<tt>.sin</tt>; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==
=== <tt>sprite.atr</tt> ===
The file <tt>sprite.atr</tt> is the index of all of the sprites that can be used as objects in the game maps. The first two bytes of this file are an [[INT16LE]] giving the number of structs that follow. Each struct is 40 bytes long and has this format:

{| class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || type || Type of item pickup. See table.
|-
| [[INT16LE]] || unknown || No apparent use. Always 0x0a.
|-
| [[INT16LE]] || width1 || Sprite width in pixels
|-
| [[INT16LE]] || height1 || Sprite height in pixels
|-
| [[INT16LE]] || width2 || Always equal to <tt>width1</tt>.
|-
| [[INT16LE]] || height2 || Always equal to <tt>height2</tt>.
|-
| [[INT16LE]] || size_index || 1 if size is 28×28; 2 if size is 14×28; 3 if size is 32×24. Other values are unknown.
|-
| [[INT16LE]] || frames || Number of frames in sprite file (for animation)
|-
| [[char]][24] || filename || Name of the file containing the sprite
|}

Setting <tt>size_index</tt> = 4 appears to work but I haven’t figured out what size it selects or how high the size index goes.

Changing <tt>width2</tt> and <tt>height2</tt> doesn’t appear to have any effect.

The file name will be no more than 12 characters long (an 8.3 character DOS file name). The remaining bytes in the string are filled with zeros.

{| class="wikitable"
! Index !! Item pickup type
|-
| 0 || None (not an item pickup)
|-
| 1 || Tires (used when you run over a stack of tires)
|-
| 2 || Four hedgehogs
|-
| 3 || Fireballs
|-
| 4 || Devil pups
|-
| 5 || Bomb
|-
| 6 || Oil slick
|-
| 7 || Upside down hog
|-
| 8 || Ice cube
|}

Sprites are placed on the map using their index in the <tt>sprite.atr</tt> file. The first sprite file listed has index 0. See [[Wacky Wheels Track Format#Where objects are placed – *.spw|Where objects are placed – <tt>*.spw</tt>]].

The default <tt>sprite.atr</tt> file lists 36 files. The tables below list what sprites are in each <tt>*.sp</tt> file listed, and their index in <tt>sprite.atr</tt>. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in <tt>sprite.atr</tt>.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrel
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

=== <tt>*.sp</tt> ===
The <tt>*.sp</tt> sprite files are raw image data (8bpp, no header or image size). Each byte is a pixel, and the value of the byte gives the index to use in the [[#Color palettes|track’s palette]].

If your image editor supports reading raw image data, you can open the <tt>*.sp</tt> files by specifying the width and height, 8 bits per pixel, indexed colors, and then applying the appropriate color palette. Then rotate the image 90° clockwise and flip the image horizontally. Some <tt>*.sp</tt> files have multiple sprites of varying widths, so you’ll need to specify a file offset and length along with the width and height.

To use a sprite file as an object on the track, it needs to be listed in [[#sprite.atr|sprite.atr]].

== Horizon graphics – <tt>*.par</tt> ==
The <tt>*.par</tt> files contain the graphics to draw on the horizon (such as buildings or mountains). Like the <tt>[[#*.sp|*.sp]]</tt> files, they are raw image data, where each byte is a pixel and specifies which color palette index to use. The color palette used is the main track [[#Color palettes|color palette]]. Each <tt>*.par</tt> file is 640×40 pixels. Unlike the <tt>*.sp</tt> files, they do not require rotation or flipping when opening them as raw image data in an image editor.

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels Track Format

2011-09-24T19:26:23Z

Yellowantphil: summarized other files used that aren't really part of the track description. also some minor formatting

{{NeedMoreInfo}}
{{Map Infobox
| Type = 2D tile-based
| Layers = 1
| Tile size = 32×32
| Viewport = 320×200
| Game1 = Wacky Wheels
}}

[[Wacky Wheels]] stores its levels across multiple files, with a different aspect of the level in each file.

== Level files ==

=== Map info – *.gam ===

These are ASCII text file with CRLF line terminators (DOS format). Files contain either 25 or 28 lines. (Some of the <tt>*.gam</tt> files that ship with Wacky Wheels are one line longer than they need to be, but the last line is empty.)

The first five lines give the names of [[PCX Format|PCX]] files to use. You can add new PCX files to <tt>wacky.dat</tt> and use those instead of the defaults. See also [[Wacky Wheels Graphics Formats]].

Lines 9 and 10 give the position of the start line, but the computer players get confused if you move the start line too far. I think the finish line is located using the <tt>[[#Wrong way info – *.pos|*.pos]]</tt> files. The game might rely on the start line being in a relatively fixed position relative to the finish line.

{|class="wikitable"
! Line !! Description
|-
| 1 || File name of the primary tile graphics file, with the leading <tt>a_</tt> removed (e.g. <tt>f3.pcx</tt> designates <tt>a_f3.pcx</tt>)
|-
| 2 || File name of the secondary tile graphics file
|-
| 3 || File that selects properties for the primary tile graphics file (again with the leading <tt>a_</tt> removed)
|-
| 4 || File that selects properties for the secondary graphics file
|-
| 5 || File name of the sky PCX file to use (using the full file name)
|-
| 6 || Always 1250 in the <tt>*.gam</tt> files that ship with the game. Unknown use.
|-
| 7 || Always 1500. Unknown use.
|-
| 8 || Always 1. Unknown use.
|-
| 9 || X position of the start line. X=0 is at the left edge of the map as viewed in the course preview screen. The right edge is near X=2048.
|-
| 10 || Y position of the start line. Y=0 is at the top edge of the map. The bottom edge is near Y=2048.
|-
| 11–24 || Unknown. These might be (X, Y) pairs of coordinates, but I can’t figure out what they do.
|-
| 25 || 1 enables color cycling using the palette in <tt>beach.pcx</tt>; 0 disables it. See [[Wacky_Wheels Graphics Formats#Color palettes|Color palettes]]. If set to 0, the remaining three lines are not necessary.
|-
| 26 || Delay between changing to the next color in the color cycles associated with palette indices 148 and 161–164. In <tt>a_f3.pcx</tt>, these indices are used to show water washing up onto the shore.
|-
| 27 || Delay between the end of the color cycle and restarting it, for palette indices 148 and 161–164.
|-
| 28 || Delay between changing to the next color for palette indices 168–175. There is no delay when restarting these color cycles.
|}

=== Map surface – *.m ===

The *.m files store the road surface a 64x64 grid of tiles. These files contain a 64x64 byte array (4096 bytes exactly) with each tile representing an index into the tileset. The tilesets are 320x200 images in [[PCX Format]], split into 32x32 tiles. There are only 54 tiles per image (so in the *.m files, byte values 0–53 refer to tiles 0–53 in the first tileset, and byte values 54–106 refer to tiles 0–53 in the second tileset.)

=== Wrong way info – *.pos ===

The same as the background layer (<tt>*.m</tt>) except that instead of one byte per tile (8-bit number) there are two bytes per tile (16-bit number). So effectively every tile position has a 16-bit number starting at 1 and increasing as you get closer to the end of the track. The ‘wrong way’ message only flashes on the screen when the player moves to a tile location with a smaller number. Since the files that ship with the game are fairly coarse in this regard (only using numbers 0–30, and fairly large blocks of the map sharing the same number), there is some delay between successive ‘wrong way’ messages when driving around the track at low speed in the wrong direction.

=== Road path – *.rd ===

The ‘road’ files control the paths the computer players drive. The file begins with a [[UINT16LE]] containing the number of objects in the file, followed by that many objects. Each object is in the following structure:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[UINT16LE]] || x1 || X-coordinate of current position
|-
| [[UINT16LE]] || y1 || Y-coordinate of current position
|-
| [[UINT16LE]] || x2 || X-coordinate of next destination
|-
| [[UINT16LE]] || y2 || Y-coordinate of next destination
|-
| [[UINT16LE]] || angle || The angle given by the two (x, y) pairs above in seemingly arbitrary units. See below.
|-
| [[UINT16LE]] || compass_direction || Direction to face. Range is 0x00–0x07. 0x00 = S, 0x01 = SW, 0x02 = W, up to 0x07 = SE.
|-
| [[UINT16LE]] || distance || Distance between the current and next points
|}

The computer players drive in a straight line from (x1, y1) to (x2, y2) and then immediately appear at the (x1, y1) point of the next struct in the file. Generally, the (x2, y2) position of one struct should have the same coordinates as the (x1, y1) position in the next struct. If they aren’t, the computer players will drive in a series of line segments and teleport from the end of one line segment to the start of the next.

The <tt>angle</tt> and <tt>distance</tt> fields are apparently not used, but their values can be calculated automatically using a tool such as [[Camoto]].

==== Calculating the angle ====

For angles, north is taken to be at the top of the map. The +y direction points down, or to the south.

The <tt>angle</tt> field is in units of degrees times 16/3 and is always positive: it ranges from 0 ≤ <tt>angle</tt> < 1920 (in decimal). The angle is zero when driving in the +X direction (due east). The +Y direction (south) is 480, west is 960, north is 1440, etc.

This angle can be calculated from the X and Y positions as follows:

angle = atan2(y2−y1, x2−x1)/π*960;
if (angle < 0) angle = angle + 1920;

==== Calculating the compass direction ====

The <tt>compass_direction</tt> field can be calculated from the <tt>angle</tt>. The conversion is
compass_direction = (angle/240.0 + 6.5) % 8
where you use floating point division and then truncate the result in parentheses to an integer.

Instead of calculating <tt>compass_direction</tt>, you can set the variable any way you like, so that the computer players drive backwards, skid in the turns, spin, etc. If you hit a driver facing you, it counts as a head on collision, even if you are both traveling the same direction.

==== Calculating the distance ====

The <tt>distance</tt> field can be calculated as:

sqrt((x2 − x1)² + (y2 − y1)²)

Note that decimals are truncated, not rounded (i.e. in C, the result is simply cast to an int.)

=== Tile properties – *.sin ===

The structs in *.sin are 12 bytes long and arranged like this:

{|class="wikitable"
! Data type !! Name !! Description
|-
| [[UINT16LE]] || prop0_active || boolean telling if prop0 should be considered
|-
| [[UINT16LE]] || prop1_active || boolean telling if prop1 should be considered
|-
| [[UINT32LE]] || prop0 || properties for color 0 in f_ma#.pcx
|-
| [[UINT16LE]] || prop1 || properties for color 1 in f_ma#.pcx
|}

I think the boolean values can always be set to 1; the property won’t be used unless it’s selected in the appropriate a_ma*.pcx file. The properties select what type of ground or water that tile will be. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt gamedata.txt] for a listing that looks promising.

=== Where objects are placed – *.spw ===

Bytes 0–1 are a [[UINT16LE]] giving how many 12-byte structs follow:
{|class="wikitable"
! Data type !! Name !! Description
|-
| [[UINT16LE]] || objectid || Index of the <tt>*.sp</tt> file to read for the graphics. See [[Wacky Wheels Graphics Formats#Sprites|Sprites]] for more details.
|-
| [[UINT16LE]] || unknown1 || Unknown; always zero
|-
| [[UINT16LE]] || xcoord || 0–2048
|-
| [[UINT16LE]] || ycoord || 0–2048
|-
| [[UINT16LE]] || unknown2 || Unknown; always zero
|-
| [[INT16LE]] || unknown3 || Unknown; always zero. Setting this number to something other than zero causes the game to cycle through many graphics. Setting it to a small negative number causes it to cycle a few times and then stop on its normal graphic.
|}

== Other level-specific files ==
These files also contain data for track number ''n'':
* ''n''<tt>.par</tt>: Contains the graphics used on the horizon (buildings, etc.). See [[Wacky Wheels Graphics Formats#Horizon graphics – *.par|Horizon graphics – <tt>*.par</tt>]].
* ''n''<tt>.bmc</tt>: Controls the computer player when driving on track ''n'' during demo mode. Only used for tracks 1–5 and 7. See [[BMC Format]].
* <tt>SHRINK</tt>''n''<tt>.PCX</tt>: Track preview map. It should be possible to generate these files from ''n''<tt>.m</tt> and the tile sets specified in ''n''<tt>.gam</tt>.

The files <tt>BRONZEM.SP</tt>, <tt>SILVERM.SP</tt>, <tt>GOLDM.SP</tt> and <tt>BONUS*.SP</tt> contain the 5-track course previews. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>. It should be possible to generate these files from <tt>SHRINK*.SP</tt>.

== Tools ==
See [[Wacky Wheels#Tools|Wacky Wheels Tools]] for a listing of viewers and editors for data in this format.

== Credits ==

This format was reverse engineered by [http://yellowantphil.com/wacky_wheels/ Phil Carter] and Klas Arvidsson. If you find this information helpful in a project you’re working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

[[Category:Wacky Wheels]]

Wacky Wheels

2011-09-24T05:37:27Z

Yellowantphil: /* Files in wacky.dat */ updated some graphics descriptions and links

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains file names and properties for sprites used at objects on the track. See <tt>[[Wacky Wheels Graphics Formats#sprite.atr|sprite.atr]]</tt>.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See <tt>[[Miscellaneous Wacky Wheels File Formats#trig.dat|trig.dat]]</tt>.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats#PCX graphics|Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See <tt>[[Wacky Wheels Graphics Formats#*.sp|*.sp]]</tt>.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Graphics Formats

2011-09-24T05:36:00Z

Yellowantphil: /* PCX graphics */

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Many of the graphics in Wacky Wheels are in [[PCX Format]]. The uses of most PCX files are self-explanatory. Some files need further explanation:
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described in [[#Color palettes|Color palettes]].
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.

==Tile appearance and properties==
* '''a_f*.pcx''': Tile graphics
* '''a_ma*.pcx''': Selects tile properties for each pixel in each tile of the tile graphics files
* '''$n.gam''': Chooses the primary and secondary tile graphics files and property files (among other things) for track $n
* '''$n.sin''': Sets tile properties 0 and 1 for each tile in track $n

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (a_f*.pcx) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (a_ma*.pcx) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track $n, any pixel in tile $m that is color #0 will have property #0 specified in struct $m of the file $n.sin; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==
=== <tt>sprite.atr</tt> ===
The file <tt>sprite.atr</tt> is the index of all of the sprites that can be used as objects in the game maps. The first two bytes of this file are an [[INT16LE]] giving the number of structs that follow. Each struct is 40 bytes long and has this format:

{| class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || type || Type of item pickup. See table.
|-
| [[INT16LE]] || unknown || No apparent use. Always 0x0a.
|-
| [[INT16LE]] || width1 || Sprite width in pixels
|-
| [[INT16LE]] || height1 || Sprite height in pixels
|-
| [[INT16LE]] || width2 || Always equal to <tt>width1</tt>.
|-
| [[INT16LE]] || height2 || Always equal to <tt>height2</tt>.
|-
| [[INT16LE]] || size_index || 1 if size is 28×28; 2 if size is 14×28; 3 if size is 32×24. Other values are unknown.
|-
| [[INT16LE]] || frames || Number of frames in sprite file (for animation)
|-
| [[char]][24] || filename || Name of the file containing the sprite
|}

Setting <tt>size_index</tt> = 4 appears to work but I haven’t figured out what size it selects or how high the size index goes.

Changing <tt>width2</tt> and <tt>height2</tt> doesn’t appear to have any effect.

The file name will be no more than 12 characters long (an 8.3 character DOS file name). The remaining bytes in the string are filled with zeros.

{| class="wikitable"
! Index !! Item pickup type
|-
| 0 || None (not an item pickup)
|-
| 1 || Tires (used when you run over a stack of tires)
|-
| 2 || Four hedgehogs
|-
| 3 || Fireballs
|-
| 4 || Devil pups
|-
| 5 || Bomb
|-
| 6 || Oil slick
|-
| 7 || Upside down hog
|-
| 8 || Ice cube
|}

Sprites are placed on the map using their index in the <tt>sprite.atr</tt> file. The first sprite file listed has index 0. See [[Wacky Wheels Track Format#Where objects are placed – *.spw|Where objects are placed – *.spw]].

The default <tt>sprite.atr</tt> file lists 36 files. The tables below list what sprites are in each <tt>*.sp</tt> file listed, and their index in <tt>sprite.atr</tt>. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in <tt>sprite.atr</tt>.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrel
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

=== <tt>*.sp</tt> ===
The <tt>*.sp</tt> sprite files are raw VGA data (8bpp, no header or image size). Each byte is a pixel, and the value of the byte gives the index to use in the [[#Color palettes|track’s palette]].

If your image editor supports reading raw image data, you can open the <tt>*.sp</tt> files by specifying the width and height, 8 bits per pixel, indexed colors, and then applying the appropriate color palette. Then rotate the image 90° clockwise and mirror the image horizontally. Some <tt>*.sp</tt> files have multiple sprites of varying widths, so you’ll need to specify a file offset and length along with the width and height.

To use a sprite file as an object on the track, it needs to be listed in [[#sprite.atr|sprite.atr]].

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels Graphics Formats

2011-09-24T05:26:20Z

Yellowantphil: /* Sprites */ mostly figured out the format of sprite.atr

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Most are self-explanatory. Some files need further explanation:
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described in [[#Color palettes|Color palettes]].
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.

==Tile appearance and properties==
* '''a_f*.pcx''': Tile graphics
* '''a_ma*.pcx''': Selects tile properties for each pixel in each tile of the tile graphics files
* '''$n.gam''': Chooses the primary and secondary tile graphics files and property files (among other things) for track $n
* '''$n.sin''': Sets tile properties 0 and 1 for each tile in track $n

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (a_f*.pcx) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (a_ma*.pcx) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track $n, any pixel in tile $m that is color #0 will have property #0 specified in struct $m of the file $n.sin; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==
=== <tt>sprite.atr</tt> ===
The file <tt>sprite.atr</tt> is the index of all of the sprites that can be used as objects in the game maps. The first two bytes of this file are an [[INT16LE]] giving the number of structs that follow. Each struct is 40 bytes long and has this format:

{| class="wikitable"
! Data type !! Name !! Description
|-
| [[INT16LE]] || type || Type of item pickup. See table.
|-
| [[INT16LE]] || unknown || No apparent use. Always 0x0a.
|-
| [[INT16LE]] || width1 || Sprite width in pixels
|-
| [[INT16LE]] || height1 || Sprite height in pixels
|-
| [[INT16LE]] || width2 || Always equal to <tt>width1</tt>.
|-
| [[INT16LE]] || height2 || Always equal to <tt>height2</tt>.
|-
| [[INT16LE]] || size_index || 1 if size is 28×28; 2 if size is 14×28; 3 if size is 32×24. Other values are unknown.
|-
| [[INT16LE]] || frames || Number of frames in sprite file (for animation)
|-
| [[char]][24] || filename || Name of the file containing the sprite
|}

Setting <tt>size_index</tt> = 4 appears to work but I haven’t figured out what size it selects or how high the size index goes.

Changing <tt>width2</tt> and <tt>height2</tt> doesn’t appear to have any effect.

The file name will be no more than 12 characters long (an 8.3 character DOS file name). The remaining bytes in the string are filled with zeros.

{| class="wikitable"
! Index !! Item pickup type
|-
| 0 || None (not an item pickup)
|-
| 1 || Tires (used when you run over a stack of tires)
|-
| 2 || Four hedgehogs
|-
| 3 || Fireballs
|-
| 4 || Devil pups
|-
| 5 || Bomb
|-
| 6 || Oil slick
|-
| 7 || Upside down hog
|-
| 8 || Ice cube
|}

Sprites are placed on the map using their index in the <tt>sprite.atr</tt> file. The first sprite file listed has index 0. See [[Wacky Wheels Track Format#Where objects are placed – *.spw|Where objects are placed – *.spw]].

The default <tt>sprite.atr</tt> file lists 36 files. The tables below list what sprites are in each <tt>*.sp</tt> file listed, and their index in <tt>sprite.atr</tt>. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in <tt>sprite.atr</tt>.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrel
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

=== <tt>*.sp</tt> ===
The <tt>*.sp</tt> sprite files are raw VGA data (8bpp, no header or image size). Each byte is a pixel, and the value of the byte gives the index to use in the [[#Color palettes|track’s palette]].

If your image editor supports reading raw image data, you can open the <tt>*.sp</tt> files by specifying the width and height, 8 bits per pixel, indexed colors, and then applying the appropriate color palette. Then rotate the image 90° clockwise and mirror the image horizontally. Some <tt>*.sp</tt> files have multiple sprites of varying widths, so you’ll need to specify a file offset and length along with the width and height.

To use a sprite file as an object on the track, it needs to be listed in [[#sprite.atr|sprite.atr]].

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Miscellaneous Wacky Wheels File Formats

2011-09-18T00:33:35Z

Yellowantphil: /* trig.dat */ trig.dat is 4 byte ints

This page describes a number of [[Wacky Wheels]] file formats that are difficult to categorize.

== <tt>trig.dat</tt> ==
This file contains only a series of (x, y) points that describe a circle of radius 65,535. Each (x, y) pair is described with two signed integers:

{|class="wikitable"
!Data type!!Description
|-
| [[INT32LE]] Xpos || X-position on the circle
|-
| [[INT32LE]] Ypos || Y-position on the circle
|}

The first 960 pairs describe the top half of the circle, and the last 960 pairs describe the bottom half.

The specific uses of the data in this file are unknown. If you replace every (x, y) pair with zeros, you can’t see any objects or tiles in the track, and you can’t drive. Interesting effects may be possible by resizing or distorting the circle.

== <tt>wacky.ing</tt> ==
Most of this file looks like an unused high score file, similar in format to <tt>[[Wacky Wheels#Files not in wacky.dat|wacky*.hi]]</tt>. It consists of structs that are 46 bytes long containing some text (“<tt>KNOCK ME OFF!</tt>” and “<tt>MAR 1994”</tt>) and other data. I don’t think this data is used.

The first 66 bytes of this file are unknown data. The game won’t load unless at least the first 28 bytes are present. At least these first 28 bytes appear to be signed integers ([[INT32LE]]). The sixth and seventh integers in the file (offsets 0x14 and 0x18) are read when allocating memory. If you change either of these integers to –100, for example, the game will fail to start, and will print how many bytes of memory it allocated and state that it needed an extra –100 bytes of memory.

Most likely nothing in this file will need to be changed to edit levels.

== Devil motion – <tt>gig.mov</tt> ==
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (X, Y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (X, Y) position for about 0.1 seconds. Once there are no more (X, Y) pairs, the devil disappears in a puff of smoke.

== Changing go kart/lawnmower speed – <tt>*.tab</tt> ==
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

[[Category:Wacky Wheels]]
[[Category:File Formats]]

INT32LE

2011-09-18T00:24:58Z

Yellowantphil: redirect

#REDIRECT [[File format data types]]

Miscellaneous Wacky Wheels File Formats

2011-09-18T00:24:10Z

Yellowantphil: mindless ramblings about wacky.ing

This page describes a number of [[Wacky Wheels]] file formats that are difficult to categorize.

== <tt>trig.dat</tt> ==
This file contains only a series of (x, y) points that describe a circle of radius 65,535. Each (x, y) pair is described with two signed integers:

{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position on the circle
|-
| [[INT16LE]] Ypos || Y-position on the circle
|}

The first 960 pairs describe the top half of the circle, and the last 960 pairs describe the bottom half.

The specific uses of the data in this file are unknown. If you replace every (x, y) pair with zeros, you can’t see any objects or tiles in the track, and you can’t drive. Interesting effects may be possible by resizing or distorting the circle.

== <tt>wacky.ing</tt> ==
Most of this file looks like an unused high score file, similar in format to <tt>[[Wacky Wheels#Files not in wacky.dat|wacky*.hi]]</tt>. It consists of structs that are 46 bytes long containing some text (“<tt>KNOCK ME OFF!</tt>” and “<tt>MAR 1994”</tt>) and other data. I don’t think this data is used.

The first 66 bytes of this file are unknown data. The game won’t load unless at least the first 28 bytes are present. At least these first 28 bytes appear to be signed integers ([[INT32LE]]). The sixth and seventh integers in the file (offsets 0x14 and 0x18) are read when allocating memory. If you change either of these integers to –100, for example, the game will fail to start, and will print how many bytes of memory it allocated and state that it needed an extra –100 bytes of memory.

Most likely nothing in this file will need to be changed to edit levels.

== Devil motion – <tt>gig.mov</tt> ==
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (X, Y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (X, Y) position for about 0.1 seconds. Once there are no more (X, Y) pairs, the devil disappears in a puff of smoke.

== Changing go kart/lawnmower speed – <tt>*.tab</tt> ==
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels

2011-09-18T00:21:59Z

Yellowantphil: /* Files in wacky.dat */ wacky.ing

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See <tt>[[Miscellaneous Wacky Wheels File Formats#trig.dat|trig.dat]]</tt>.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 66 bytes have to do with memory allocation and possibly other things. See <tt>[[Miscellaneous Wacky Wheels File Formats#wacky.ing|wacky.ing]]</tt>.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Track Format

2011-09-17T22:07:24Z

Yellowantphil: /* Calculating the compass direction */ fixed compass direction formula. I thought I did this already...

{{NeedMoreInfo}}
{{Map Infobox
| Type = 2D tile-based
| Layers = 1
| Tile size = 32×32
| Viewport = 320×200
| Game1 = Wacky Wheels
}}

[[Wacky Wheels]] stores its levels across multiple files, with a different aspect of the level in each file.

== Level files ==

=== Map info – *.gam ===

These are ASCII text file with CRLF line terminators (DOS format). Files contain either 25 or 28 lines. (Some of the <tt>*.gam</tt> files that ship with Wacky Wheels are one line longer than they need to be, but the last line is empty.)

The first five lines give the names of [[PCX Format|PCX]] files to use. You can add new PCX files to <tt>wacky.dat</tt> and use those instead of the defaults.

Lines 9 and 10 give the position of the start line, but the computer players get confused if you move the start line too far. I think the finish line is located using the <tt>[[#.22Wrong_way.22_info_.E2.80.93_.2A.pos|*.pos]]</tt> files. The game might rely on the start line being in a relatively fixed position relative to the finish line.

{|class="wikitable"
!Line!!Description
|-
| 1 || File name of the primary tile graphics file, with the leading <tt>a_</tt> removed (e.g. <tt>f3.pcx</tt> designates <tt>a_f3.pcx</tt>)
|-
| 2 || File name of the secondary tile graphics file
|-
| 3 || File that selects properties for the primary tile graphics file (again with the leading <tt>a_</tt> removed)
|-
| 4 || File that selects properties for the secondary graphics file
|-
| 5 || File name of the sky PCX file to use (using the full file name)
|-
| 6 || Always 1250 in the <tt>*.gam</tt> files that ship with the game. Unknown use.
|-
| 7 || Always 1500. Unknown use.
|-
| 8 || Always 1. Unknown use.
|-
| 9 || X position of the start line. X=0 is at the left edge of the map as viewed in the course preview screen. The right edge is near X=2048.
|-
| 10 || Y position of the start line. Y=0 is at the top edge of the map. The bottom edge is near Y=2048.
|-
| 11–24 || Unknown. These might be (X, Y) pairs of coordinates, but I can’t figure out what they do.
|-
| 25 || 1 enables color cycling using the palette in <tt>beach.pcx</tt>; 0 disables it. See [[Wacky_Wheels Graphics Formats#Color palettes|Color palettes]]. If set to 0, the remaining three lines are not necessary.
|-
| 26 || Delay between changing to the next color in the color cycles associated with palette indices 148 and 161–164. In <tt>a_f3.pcx</tt>, these indices are used to show water washing up onto the shore.
|-
| 27 || Delay between the end of the color cycle and restarting it, for palette indices 148 and 161–164.
|-
| 28 || Delay between changing to the next color for palette indices 168–175. There is no delay when restarting these color cycles.
|}

=== Map surface – *.m ===

The *.m files store the road surface a 64x64 grid of tiles. These files contain a 64x64 byte array (4096 bytes exactly) with each tile representing an index into the tileset. The tilesets are 320x200 images in [[PCX Format]], split into 32x32 tiles. There are only 54 tiles per image (so in the *.m files, byte values 0-53 refer to tiles 0-53 in the first tileset, and byte values 54-106 refer to tiles 0-53 in the second tileset.)

=== Background image – *.par ===

Contains the graphics used on the horizon (buildings, etc.). Raw VGA data (8bpp, no header or image size), I think.

=== "Wrong way" info – *.pos ===

The same as the background layer (<tt>*.m</tt>) except that instead of one byte per tile (8-bit number) there are two bytes per tile (16-bit number). So effectively every tile position has a 16-bit number starting at 1 and increasing as you get closer to the end of the track. The 'wrong way' message only flashes on the screen when the player moves to a tile location with a smaller number. Since the files that ship with the game are fairly coarse in this regard (only using numbers 0-30, and fairly large blocks of the map sharing the same number), there is some delay between successive 'wrong way' messages when driving around the track at low speed in the wrong direction.

=== Road path – *.rd ===

The 'road' files control the paths the computer players drive. The file begins with a [[UINT16LE]] containing the number of objects in the file, followed by that many objects. Each object is in the following structure:

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] x1 || X-coordinate of current position
|-
| [[UINT16LE]] y1 || Y-coordinate of current position
|-
| [[UINT16LE]] x2 || X-coordinate of next destination
|-
| [[UINT16LE]] y2 || Y-coordinate of next destination
|-
| [[UINT16LE]] angle || The angle given by the two (x, y) pairs above in seemingly arbitrary units. See below.
|-
| [[UINT16LE]] compass_direction || Direction to face. Range is 0x00–0x07. 0x00 = S, 0x01 = SW, 0x02 = W, up to 0x07 = SE.
|-
| [[UINT16LE]] distance || Distance between the current and next points
|}

The computer players drive in a straight line from (x1, y1) to (x2, y2) and then immediately appear at the (x1, y1) point of the next struct in the file. Generally, the (x2, y2) position of one struct should have the same coordinates as the (x1, y1) position in the next struct. If they aren’t, the computer players will drive in a series of line segments and teleport from the end of one line segment to the start of the next.

The <tt>angle</tt> and <tt>distance</tt> fields are apparently not used, but their values can be calculated automatically using a tool such as [[Camoto]].

==== Calculating the angle ====

For angles, north is taken to be at the top of the map. The +y direction points down, or to the south.

The <tt>angle</tt> field is in units of degrees times 16/3 and is always positive: it ranges from 0 ≤ <tt>angle</tt> < 1920 (in decimal). The angle is zero when driving in the +X direction (due east). The +Y direction (south) is 480, west is 960, north is 1440, etc.

This angle can be calculated from the X and Y positions as follows:

angle = atan2(y2−y1, x2−x1)/π*960;
if (angle < 0) angle = angle + 1920;

==== Calculating the compass direction ====

The <tt>compass_direction</tt> field can be calculated from the <tt>angle</tt>. The conversion is
compass_direction = (angle/240.0 + 6.5) % 8
where you use floating point division and then truncate the result in parentheses to an integer.

Instead of calculating <tt>compass_direction</tt>, you can set the variable any way you like, so that the computer players drive backwards, skid in the turns, spin, etc. If you hit a driver facing you, it counts as a head on collision, even if you are both traveling the same direction.

==== Calculating the distance ====

The <tt>distance</tt> field can be calculated as:

sqrt((x2 − x1)² + (y2 − y1)²)

Note that decimals are truncated, not rounded (i.e. in C, the result is simply cast to an int.)

=== Tile properties – *.sin ===

The structs in *.sin are 12 bytes long and arranged like this:

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] prop0_active || boolean telling if prop0 should be considered
|-
| [[UINT16LE]] prop1_active || boolean telling if prop1 should be considered
|-
| [[UINT32LE]] prop0 || properties for color 0 in f_ma#.pcx
|-
| [[UINT16LE]] prop1 || properties for color 1 in f_ma#.pcx
|}

I think the boolean values can always be set to 1; the property won’t be used unless it’s selected in the appropriate a_ma*.pcx file. The properties select what type of ground or water that tile will be. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt gamedata.txt] for a listing that looks promising.

=== Where objects are placed – *.spw ===

Bytes 0–1 are a [[UINT16LE]] giving how many 12-byte structs follow:
{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] objectid || Index of the <tt>*.sp</tt> file to read for the graphics. See [[Wacky Wheels Graphics Formats#Sprites|Sprites]] for a list.
|-
| [[UINT16LE]] unknown || Unknown; always zero
|-
| [[UINT16LE]] xcoord || 0–2048
|-
| [[UINT16LE]] ycoord || 0–2048
|-
| [[UINT16LE]] unknown || Unknown; always zero
|-
| [[INT16LE]] unknown || Unknown; always zero. Setting this number to something other than zero causes the game to cycle through many graphics. Setting it to a small negative number causes it to cycle a few times and then stop on its normal graphic.
|}

== Tools ==
See [[Wacky Wheels#Tools|Wacky Wheels Tools]] for a listing of viewers and editors for data in this format.

== Credits ==

This format was reverse engineered by [http://yellowantphil.com/wacky_wheels/ Phil Carter] and Klas Arvidsson. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

[[Category:Wacky Wheels]]

Wacky Wheels

2011-09-17T21:20:55Z

Yellowantphil: /* Files in wacky.dat */ broke a couple links in the last edit

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See <tt>[[Miscellaneous Wacky Wheels File Formats#trig.dat|trig.dat]]</tt>.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 59 bytes appear to be something else.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Graphics Formats

2011-09-17T21:17:06Z

Yellowantphil: categories

This page describes the formats and files used to display graphics in [[Wacky Wheels]].

==PCX graphics==
Most are self-explanatory. Some files need further explanation:
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described in [[#Color palettes|Color palettes]].
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.

==Tile appearance and properties==
* '''a_f*.pcx''': Tile graphics
* '''a_ma*.pcx''': Selects tile properties for each pixel in each tile of the tile graphics files
* '''$n.gam''': Chooses the primary and secondary tile graphics files and property files (among other things) for track $n
* '''$n.sin''': Sets tile properties 0 and 1 for each tile in track $n

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (a_f*.pcx) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (a_ma*.pcx) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track $n, any pixel in tile $m that is color #0 will have property #0 specified in struct $m of the file $n.sin; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==

These tables list what sprites are in each <tt>*.sp</tt> file. The sprites are raw VGA data (8bpp, no header or image size).

The file <tt>sprite.atr</tt> contains additional data for these files, but what data is stored is still unknown.

To place an object on the track, use the index listed in one of the <tt>[[Wacky Wheels Track Format#Where objects are placed – *.spw|*.spw]]</tt> files. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in the index.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrell
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Miscellaneous Wacky Wheels File Formats

2011-09-17T21:14:17Z

Yellowantphil: new page; added some information on trig.dat

This page describes a number of [[Wacky Wheels]] file formats that are difficult to categorize.

== <tt>trig.dat</tt> ==
This file contains only a series of (x, y) points that describe a circle of radius 65,535. Each (x, y) pair is described with two signed integers:

{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position on the circle
|-
| [[INT16LE]] Ypos || Y-position on the circle
|}

The first 960 pairs describe the top half of the circle, and the last 960 pairs describe the bottom half.

The specific uses of the data in this file are unknown. If you replace every (x, y) pair with zeros, you can’t see any objects or tiles in the track, and you can’t drive. Interesting effects may be possible by resizing or distorting the circle.

== Changing go kart/lawnmower speed – <tt>*.tab</tt> ==
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

== Devil motion – <tt>gig.mov</tt> ==
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (X, Y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (X, Y) position for about 0.1 seconds. Once there are no more (X, Y) pairs, the devil disappears in a puff of smoke.

[[Category:Wacky Wheels]]
[[Category:File Formats]]

Wacky Wheels

2011-09-17T21:14:08Z

Yellowantphil: split some more information into a new page

{{NeedMoreInfo}}
{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

Note also that the file <tt>audiot.fx</tt> in <tt>wacky.dat</tt> is itself an archive file, containing 54 unnamed files. See the entry for <tt>*.fx</tt> in the table below.

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #CCFFCC;" | Series of (x, y) pairs that describe a circle. See <tt>[[Miscellaneous Wacky Wheels File Formats#trig.dat|trig.dat]]</tt>.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. <tt>audiohed.fx</tt> is the header file for <tt>audiot.fx</tt>.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. See [[Miscellaneous Wacky Wheels File Formats#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 59 bytes appear to be something else.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[Miscellaneous Wacky Wheels File Formats#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. See [[Miscellaneous Wacky Wheels File Formats#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[Miscellaneous Wacky Wheels File Formats#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]

If deleted, these files are created by copying the appropriate <tt>*.htt</tt> file from <tt>wacky.dat</tt>. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file.
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]

The file <tt>wac1.ott</tt> in <tt>wacky.dat</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>.
|}

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Track Format

2011-09-17T06:23:21Z

Yellowantphil: explained the *.rd format; updated a couple links; general formatting

{{NeedMoreInfo}}
{{Map Infobox
| Type = 2D tile-based
| Layers = 1
| Tile size = 32×32
| Viewport = 320×200
| Game1 = Wacky Wheels
}}

[[Wacky Wheels]] stores its levels across multiple files, with a different aspect of the level in each file.

== Level files ==

=== Map info – *.gam ===

These are ASCII text file with CRLF line terminators (DOS format). Files contain either 25 or 28 lines. (Some of the <tt>*.gam</tt> files that ship with Wacky Wheels are one line longer than they need to be, but the last line is empty.)

The first five lines give the names of [[PCX Format|PCX]] files to use. You can add new PCX files to <tt>wacky.dat</tt> and use those instead of the defaults.

Lines 9 and 10 give the position of the start line, but the computer players get confused if you move the start line too far. I think the finish line is located using the <tt>[[#.22Wrong_way.22_info_.E2.80.93_.2A.pos|*.pos]]</tt> files. The game might rely on the start line being in a relatively fixed position relative to the finish line.

{|class="wikitable"
!Line!!Description
|-
| 1 || File name of the primary tile graphics file, with the leading <tt>a_</tt> removed (e.g. <tt>f3.pcx</tt> designates <tt>a_f3.pcx</tt>)
|-
| 2 || File name of the secondary tile graphics file
|-
| 3 || File that selects properties for the primary tile graphics file (again with the leading <tt>a_</tt> removed)
|-
| 4 || File that selects properties for the secondary graphics file
|-
| 5 || File name of the sky PCX file to use (using the full file name)
|-
| 6 || Always 1250 in the <tt>*.gam</tt> files that ship with the game. Unknown use.
|-
| 7 || Always 1500. Unknown use.
|-
| 8 || Always 1. Unknown use.
|-
| 9 || X position of the start line. X=0 is at the left edge of the map as viewed in the course preview screen. The right edge is near X=2048.
|-
| 10 || Y position of the start line. Y=0 is at the top edge of the map. The bottom edge is near Y=2048.
|-
| 11–24 || Unknown. These might be (X, Y) pairs of coordinates, but I can’t figure out what they do.
|-
| 25 || 1 enables color cycling using the palette in <tt>beach.pcx</tt>; 0 disables it. See [[Wacky_Wheels Graphics Formats#Color palettes|Color palettes]]. If set to 0, the remaining three lines are not necessary.
|-
| 26 || Delay between changing to the next color in the color cycles associated with palette indices 148 and 161–164. In <tt>a_f3.pcx</tt>, these indices are used to show water washing up onto the shore.
|-
| 27 || Delay between the end of the color cycle and restarting it, for palette indices 148 and 161–164.
|-
| 28 || Delay between changing to the next color for palette indices 168–175. There is no delay when restarting these color cycles.
|}

=== Map surface – *.m ===

The *.m files store the road surface a 64x64 grid of tiles. These files contain a 64x64 byte array (4096 bytes exactly) with each tile representing an index into the tileset. The tilesets are 320x200 images in [[PCX Format]], split into 32x32 tiles. There are only 54 tiles per image (so in the *.m files, byte values 0-53 refer to tiles 0-53 in the first tileset, and byte values 54-106 refer to tiles 0-53 in the second tileset.)

=== Background image – *.par ===

Contains the graphics used on the horizon (buildings, etc.). Raw VGA data (8bpp, no header or image size), I think.

=== "Wrong way" info – *.pos ===

The same as the background layer (<tt>*.m</tt>) except that instead of one byte per tile (8-bit number) there are two bytes per tile (16-bit number). So effectively every tile position has a 16-bit number starting at 1 and increasing as you get closer to the end of the track. The 'wrong way' message only flashes on the screen when the player moves to a tile location with a smaller number. Since the files that ship with the game are fairly coarse in this regard (only using numbers 0-30, and fairly large blocks of the map sharing the same number), there is some delay between successive 'wrong way' messages when driving around the track at low speed in the wrong direction.

=== Road path – *.rd ===

The 'road' files control the paths the computer players drive. The file begins with a [[UINT16LE]] containing the number of objects in the file, followed by that many objects. Each object is in the following structure:

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] x1 || X-coordinate of current position
|-
| [[UINT16LE]] y1 || Y-coordinate of current position
|-
| [[UINT16LE]] x2 || X-coordinate of next destination
|-
| [[UINT16LE]] y2 || Y-coordinate of next destination
|-
| [[UINT16LE]] angle || The angle given by the two (x, y) pairs above in seemingly arbitrary units. See below.
|-
| [[UINT16LE]] compass_direction || Direction to face. Range is 0x00–0x07. 0x00 = S, 0x01 = SW, 0x02 = W, up to 0x07 = SE.
|-
| [[UINT16LE]] distance || Distance between the current and next points
|}

The computer players drive in a straight line from (x1, y1) to (x2, y2) and then immediately appear at the (x1, y1) point of the next struct in the file. Generally, the (x2, y2) position of one struct should have the same coordinates as the (x1, y1) position in the next struct. If they aren’t, the computer players will drive in a series of line segments and teleport from the end of one line segment to the start of the next.

The <tt>angle</tt> and <tt>distance</tt> fields are apparently not used, but their values can be calculated automatically using a tool such as [[Camoto]].

==== Calculating the angle ====

For angles, north is taken to be at the top of the map. The +y direction points down, or to the south.

The <tt>angle</tt> field is in units of degrees times 16/3 and is always positive: it ranges from 0 ≤ <tt>angle</tt> < 1920 (in decimal). The angle is zero when driving in the +X direction (due east). The +Y direction (south) is 480, west is 960, north is 1440, etc.

This angle can be calculated from the X and Y positions as follows:

angle = atan2(y2−y1, x2−x1)/π*960;
if (angle < 0) angle = angle + 1920;

==== Calculating the compass direction ====

The <tt>compass_direction</tt> field can be calculated from the <tt>angle</tt>. Since the <tt>angle</tt> variable divides a circle into 1920 units and <tt>compass_direction</tt> divides a circle into 8 units, the conversion is
compass_direction = (angle/240 + 6) % 8
where you use floating point division and then truncate the result in parentheses to an int. Rounding the result instead of truncating would probably also work.

Instead of calculating <tt>compass_direction</tt>, you can set the variable any way you like, so that the computer players drive backwards, skid in the turns, spin, etc. If you hit a driver facing you, it counts as a head on collision, even if you are both traveling the same direction.

==== Calculating the distance ====

The <tt>distance</tt> field can be calculated as:

sqrt((x2 − x1)² + (y2 − y1)²)

Note that decimals are truncated, not rounded (i.e. in C, the result is simply cast to an int.)

=== Tile properties – *.sin ===

The structs in *.sin are 12 bytes long and arranged like this:

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] prop0_active || boolean telling if prop0 should be considered
|-
| [[UINT16LE]] prop1_active || boolean telling if prop1 should be considered
|-
| [[UINT32LE]] prop0 || properties for color 0 in f_ma#.pcx
|-
| [[UINT16LE]] prop1 || properties for color 1 in f_ma#.pcx
|}

I think the boolean values can always be set to 1; the property won’t be used unless it’s selected in the appropriate a_ma*.pcx file. The properties select what type of ground or water that tile will be. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt gamedata.txt] for a listing that looks promising.

=== Where objects are placed – *.spw ===

Bytes 0–1 are a [[UINT16LE]] giving how many 12-byte structs follow:
{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] objectid || Index of the <tt>*.sp</tt> file to read for the graphics. See [[Wacky Wheels Graphics Formats#Sprites|Sprites]] for a list.
|-
| [[UINT16LE]] unknown || Unknown; always zero
|-
| [[UINT16LE]] xcoord || 0–2048
|-
| [[UINT16LE]] ycoord || 0–2048
|-
| [[UINT16LE]] unknown || Unknown; always zero
|-
| [[INT16LE]] unknown || Unknown; always zero. Setting this number to something other than zero causes the game to cycle through many graphics. Setting it to a small negative number causes it to cycle a few times and then stop on its normal graphic.
|}

== Tools ==
See [[Wacky Wheels#Tools|Wacky Wheels Tools]] for a listing of viewers and editors for data in this format.

== Credits ==

This format was reverse engineered by [http://yellowantphil.com/wacky_wheels/ Phil Carter] and Klas Arvidsson. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

[[Category:Wacky Wheels]]

Wacky Wheels

2011-09-17T06:10:44Z

Yellowantphil: split out some of the information to a new page

{{Stub}}

{{GamePage}}

* For information about editing Wacky Wheels tracks, see [[Wacky Wheels Track Format]].
* For information about editing the graphics in Wacky Wheels, see [[Wacky Wheels Graphics Formats]].
* For information about editing the sound effects and music in Wacky Wheels, see [[Wacky Wheels Music and Sound Effects]].
* For additional information, refer to the list of file formats below.

== File formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #FFCCCC;" | Unknown; possibly trigonometric lookup tables.
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 59 bytes appear to be something else.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. <tt>wac1.ott</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | Sprites. See [[Wacky Wheels Graphics Formats]].
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]
|}

== Miscellaneous File Formats ==
=== Changing go kart/lawnmower speed – <tt>*.tab</tt> ===
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

=== Devil motion – <tt>gig.mov</tt> ===
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (X, Y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (X, Y) position for about 0.1 seconds. Once there are no more (X, Y) pairs, the devil disappears in a puff of smoke.

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

Wacky Wheels Graphics Formats

2011-09-17T06:10:09Z

Yellowantphil: split graphics information into its own page

{{stub}}

==PCX graphics==
Most are self-explanatory. Some files need further explanation:
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described in [[#Color palettes|Color palettes]].
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.

==Tile appearance and properties==
* '''a_f*.pcx''': Tile graphics
* '''a_ma*.pcx''': Selects tile properties for each pixel in each tile of the tile graphics files
* '''$n.gam''': Chooses the primary and secondary tile graphics files and property files (among other things) for track $n
* '''$n.sin''': Sets tile properties 0 and 1 for each tile in track $n

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (a_f*.pcx) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (a_ma*.pcx) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track $n, any pixel in tile $m that is color #0 will have property #0 specified in struct $m of the file $n.sin; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== Sprites ==

These tables list what sprites are in each <tt>*.sp</tt> file. The sprites are raw VGA data (8bpp, no header or image size).

The file <tt>sprite.atr</tt> contains additional data for these files, but what data is stored is still unknown.

To place an object on the track, use the index listed in one of the <tt>[[Wacky Wheels Track Format#Where objects are placed – *.spw|*.spw]]</tt> files. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in the index.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrell
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

[[Category:Wacky Wheels]]

Inverse Frequency Sound format

2011-09-17T05:28:55Z

Yellowantphil: misplaced backslashes pain my soul

The inverse frequency sound format is the format used by Apogee/Id Software in many of their games for the PC sounds. It is named because the bulk of the data is stored as 'inverse frequency' values. (The higher the value, the lower the tone it produces.) Most commonly this is stored in a <tt>SOUNDS.xxx</tt> file, though it may be stored internally.

Later games, such as [[Wolfenstein 3D]] use a modified form of this for their (Less important) PC speaker and adlib sounds.

The file is divided into three sections, 16 bytes of header, a list of sound names and the actual sound data. The start of sound data should thus be (Numsnds + 1) * 16 bytes from the file start

==Header==

0 4 Identifier "SND" + $00; indicates the start of a sound file, whereas "SPK" + $00 indicates
the start of the older 'speaker' format, which has very few differences.
4 2 Filesize Size of file
6 2 ??? Usually $3C $00, but doesn't appear to do anything.
8 2 Sndnum Number of sounds in file. For SPK files this is blank as the number of sounds
is always 63
10 6 Spacer Padded with nulls

==Sound names==

SOUND HEADER: (1 per sound, 16 bytes each)
? 2 Location Location of sound start in file
2 1 Priority Whether or not sound will be interrupted by another sound if said sound
starts playing while the first is. Sounds can only be interrupted by sounds
that have an equal or higher value of this. 255 is max, 0 is inadvisable
3 1 Validater If a sound is a 'placeholder' to be ignored, this is 1, if it is a proper
sound it is 8
4 12 Name Sound name, padded with nulls.

==Sound data==

Sound data is divided into words, with the word value being inversely proportional to the sound frequency. Each word is around 1/64th of a second of tone and most files contain a few seconds of sound. The value $FFFF signals the end of a sound and most values are between the range $0100-$5000. $0000 is silence.

Later games use a similar format for PC and Adlib sounds, the sound data is in bytes with values of 0-255, the loss of fine-tuning being attributable to the lesser role of PC sounds and the Adlib format. The [[AudioT Format]] also has a totally different way of reading the sounds, and contains music.

==Notes==

This format has been reverse engineered many times, most often in the [[Commander Keen 1-3]] fan community. Probably first by [http://web.archive.org/web/20000815235203/http://www.dd.chalmers.se/~f98anga/projects/keen/ Anders Gavare].

Games that use this format are [[Catacomb]] 1 and 2, [[Commander Keen 1-3]], [[Cosmo's Cosmic Adventures]], [[Dangerous Dave]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Duke Nukem]], [[Duke Nukem II]], [[Hovertank 3D]], [[Math Rescue]], [[Major Stryker]], [[Monster Bash]], [[Paragon]] (aka Street Ball), [[Pickle Wars]], [[Realms of Chaos]] (beta version only), [[Rescue Rover]], [[Shadow Knights]], [[Slordax]], [[Word Rescue]] and [[Xenopods]].

[[Category:File Formats]]
[[Category:Audio Files]]

AudioT Format

2011-09-17T05:05:37Z

Yellowantphil: added Wacky Wheels; minor corrections

The AudioT format is a [[:Category:Group Files|group file]] used by many id/Apogee games to store Adlib music, Adlib sound effects and PC Speaker sound effects in a single file. The basic structure of this format is very similar to the [[EGAGraph_Format]] and the [[GameMaps Format]]. The main audio file can be compressed (<tt>AUDIO.xxx</tt>) or uncompressed (<tt>AUDIOT.xxx</tt>). It requires an associated <tt>AUDIOHED.xxx</tt> which stores the offsets of each file, and an <tt>AUDIODCT.xxx</tt> if the file is compressed.

== File formats ==

=== Audio Head (AUDIOHED.xxx) ===

This header file stores the offsets (relative to the start of the <tt>AUDIO/AUDIOT</tt> file) for each sub file. The format is trivial, in that the header file is simply an array of <tt>UINT32LE</tt> offsets.

The last offset in the file will be an offset to the end of the main <tt>AUDIO/AUDIOT</tt> file. This was probably done so that the size of each chunk could be calculated with the formula below. Thus, the number of offsets (size of the <tt>AUDIOHED</tt> in dwords) minus one will give the number of chunks (slots) included in the main file. This number varies, but is usually about 200. (Games refer to the chunks by index, not by name).

The size of a chunk can be calculated like this:

size[i] = offset[i+1] - offset[i]

Empty chunks (size[i] = 0) should be skipped when extracting chunks.

In most (not all) games, the <tt>AUDIOHED</tt> is included in the executable file. See [[Extracting data files from executables]] for information on how to locate and extract them.

=== Dictionary (AUDIODCT.xxx) ===

If the main audio file is named <tt>AUDIO.xxx</tt>, then the file is compressed. The same [[Huffman Compression]] scheme used elsewhere in the [[Commander Keen]] series is used. When reading compressed files out of the <tt>AUDIO</tt> file, the first four bytes located at the <tt>AUDIOHED</tt> offset are a UINT32LE specifying the file's decompressed size (which is required for the decompression algorithm.) The compressed data then follows.

Note that the <tt>AUDIODCT</tt> file is not often obvious, usually being embedded in the main exe file. Executables usually contain two or more dictionaries, but the <tt>AUDIODCT</tt> is usually the first one. (A simple check of whether it decompresses the data sensibly works.)

=== Main file (AUDIOT.xxx, AUDIO.xxx) ===

This file is simply an array of data files. Each file starts at the offset specified in the <tt>AUDIOHED</tt> file, and as there are no filenames each file is referred to by its index/slot number. Slots containing dummy values in the header are treated as if they don't exist in the <tt>AUDIO/AUDIOT</tt> file.

If compression is in use then the <tt>AUDIO</tt> file itself isn't compressed, rather each file within the <tt>AUDIO</tt> file is individually compressed. A file can be read by opening the <tt>AUDIOT</tt> file, seeking to the offset specified in the <tt>AUDIOHED</tt> file, reading a UINT32LE for the decompressed file size, and then decompressing the data from that point onwards using standard Huffman decompression techniques.

If compression is not in use (<tt>AUDIOT</tt> files) then a file can be read by simply seeking to the offset specified in the AUDIOHED file and reading until the offset of the following file is reached. Since the last offset in the <tt>AUDIOHED</tt> file is the size of the <tt>AUDIOT</tt> file itself, no extra handling should be necessary to correctly read all of the last file.

== Chunks ==

The AUDIOT format is a container format, meaning that any files the game can handle can be stored in it. Traditionally there have been three types of 'sub files' or chunks: Adlib music files (which are [[IMF Format]]), Adlib sound effects and PC Speaker sound effects. By default most games store PC effects first, followed by their Adlib equivalents, with the IMF music filling the last entries.

At least one case is known where the music is in MIDI format ([[Noah's Ark 3D]]) and it is possible that soundblaster 'digital' sound effects have been stored like this as well at some point. There has often been confusion about what part of a file are data and which are the AUDIOT file, for example the IMF file format was widely believed to exist in two types until it was discovered that 'type 1' IMFs were simply 'type 0' that had been incorrectly extracted from the AUDIOT file with their chunk length and tags.

It is notable that a sound file will contain exactly as many PC sounds as adlib sounds (and an arbitrary number of IMF files.) This is because most games have a PC/Adlib option and thus must match every PC sound with an adlib equivalent. The number of sounds appears to be hard-coded, though all games (except for [[Commander Keen Dreams]]) seem to add the string "!ID!" after the last sound of each 'section'. The "!ID!" tags themselves don't seem to be part of any chunk and are probably put in for debugging purposes.

Sound chunks are always in the same order, PC, then adlib then IMF. A simple method to classify the sound chunks is to check the <tt>AUDIOHED</tt> for chunks of size 0. These are 'empty' sounds and seperate sound chunks from music chunks . Every nonzero length chunk after this is an IMF chunk. (IMFs are always the last chunks in the <tt>AUDIOHED</tt> and contain no zero length chunks) For the PC/adlib chunks, the number of chunks before the first zero length chunk can be divided into two, the first half being PC, the second half being adlib.

If the file is uncompressed then the adlib and IMF chunks will be tagged (huffman compression, being a space saving exercise doesn't comoress tags.) PC chunks are never tagged. It appears that the compiler used added a footer to each chunk as they were compiled. For sounds these are null terminated strings of 12 characters or less, including terminator. For IMF files these are 88 byte strings detailed on the [[IMF Format]] page. These names are not read by games (with the possible exception of the aforementioned '!ID!' tags.)

TODO: Need to also document both sound effect formats so the sounds can be edited and not just imported/exported.

=== IMF Music ===

[[IMF Format]] files are packed at the end of the audio file. Occasionally 'empty' music files are found (e.g [[Wolfenstein 3-D]]) that contain no actual data, just footer information placed there by a compiler. They can be extracted as they are and played with various utilities such as Adplug.

=== PC Sounds ===

0 4 Length of sound data (Usually chunk length - 7)
4 2 Priority of sound, only 1 PC sound may play at a time; any sound
will interrupt a sound of equal or lower priority.
6 ? Sound data
? 1 Terminating null

PC sounds use a modified form of the [[Inverse Frequency Sound format]] used in earlier ID games. Briefly, the sound data is stored as bytes, each specifying the inverse of a frequency. (Higher value, lower frequency.) This format is properly detailed elsewhere.

While most PC chunks have no sound name and thus can be identified solely by their first four bytes and their length, it appears they can in fact be named and some games occasionally do name them.

These files can be converted into Wave files easily enough, but currently the only program known to do so is Keenwave: http://levellord.toxicsheep.com/KWbeta.zip

TODO: Document this too (Code exists to do this)

=== Adlib Sounds ===

Adlib sounds are slightly more complex. Their header contains additional information to the PC sounds, used to set up the Adlib chip when playing the sound. Games always reset the chip when playing a new sound and so each sound is given 17 bytes of Adlib data. This information is what, in effect, makes the Adlib sounds sound different from the PC ones. by changing these values, various properties of the sound can be altered. Specifically these refer to the values for each of two operators for a single Adlib channel. (Adlib sounds use two sound waves, a carrier and a modulator, C1 and C2, the modulator moves through the carrier, modifying it as it does so.) Adlib sound effects can be converted into IMF format as IMFs are essentially sequences of Adlib sounds on several instead of just one Adlib channel.

An Adlib sound entry is contained in this structure:

{|class="wikitable"
!Data type!!Name!!Description
|-
| [[UINT32LE]] || length || Length of sound data
|-
| [[UINT16LE]] || priority || Sound priority
|-
| [[BYTE]][] || data || Actual sound data
|-
| [[UINT8]] || terminator || ?
|-
| [[ASCIIZ]][] || name || NULL-terminated sound effect name (optional)
|}

The format of the <tt>data</tt> field is described on the [[Adlib sound effect]] page.

== Utilities ==

[http://www.winamp.com/player Download Winamp] a program capable of playing IMF files with the right library.

KeenWave: This program can extract, and to a limited extent, edit the AUDIOT files into various formats, including wave files. It is currently at the beta stage. http://levellord.toxicsheep.com/KWbeta.zip It also contains:

KeenISF: This program plays the Adlib sounds, if they are extracted as raw data.

[[Category:Adlib]]
[[Category:Audio Files]]
[[Category:File Formats]]
[[Category:Music Files]]
[[Category:Sound Files]]
[[Category:Compressed Files]]
[[Category:Huffman Compression]]


[[Category:Bio Menace]]
[[Category:Catacomb 3D]]
[[Category:Commander Keen 4-6]]
[[Category:Noah's Ark 3D]]
[[Category:Wolfenstein 3-D]]
[[Category:Wacky Wheels]]

Wacky Wheels

2011-09-17T04:52:59Z

Yellowantphil: /* Files in wacky.dat */ AudioT format

{{Stub}}

{{GamePage}}
== File formats ==

This section lists the major file formats used in the game.

* [[DAT Format (Wacky Wheels)|DAT Format]] - compressed group file storing most of the game data
* [[MID Format]] - game music in MIDI format
* [[KLM Format]] - game music in Adlib format
* [[VOC Format]] - sound effects
* [[B800 Text]] - exit screens
* [[PCX Format]] - various game graphics
* <tt>[[#Sprites|*.sp]]</tt> sprites are raw VGA data (8bpp, no header or image size)
** <tt>sprite.atr</tt> contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>
* [[Wacky Wheels Track Format]] - <tt>*.gam</tt>, <tt>*.m</tt>, <tt>*.par</tt>, <tt>*.pos</tt>, <tt>*.rd</tt>, <tt>*.sin</tt> and <tt>*.spw</tt> are all used to construct each level

==Tile appearance and properties==
* '''a_f*.pcx''': Tile graphics
* '''a_ma*.pcx''': Selects tile properties for each pixel in each tile of the tile graphics files
* '''$n.gam''': Chooses the primary and secondary tile graphics files and property files (among other things) for track $n
* '''$n.sin''': Sets tile properties 0 and 1 for each tile in track $n

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (a_f*.pcx) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (a_ma*.pcx) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track $n, any pixel in tile $m that is color #0 will have property #0 specified in struct $m of the file $n.sin; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== List of file formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>. Specific contents are unknown.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.fx</tt>
| style="background: #CCFFCC;" | Uncompressed [[AudioT Format]] sound effects for PC speaker and AdLib. The archive file <tt>audiot.fx</tt> contains 26 files of each format. Ask [[User:yellowantphil|Phil]] if you want an extraction program.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 59 bytes appear to be something else.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. <tt>wac1.ott</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. Most are self-explanatory. Some files need further explanation:
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described in [[#Color palettes|Color palettes]].
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | [[#Sprites|Sprites]]. See also <tt>sprite.atr</tt> in this table.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]
|}

== Miscellaneous File Formats ==
=== Changing go kart/lawnmower speed – <tt>*.tab</tt> ===
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

=== Devil motion – <tt>gig.mov</tt> ===
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (X, Y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (X, Y) position for about 0.1 seconds. Once there are no more (X, Y) pairs, the devil disappears in a puff of smoke.

== Sprites ==

These tables list what sprites are in each <tt>*.sp</tt> file. The sprites are raw VGA data (8bpp, no header or image size).

The file <tt>sprite.atr</tt> contains additional data for these files, but what data is stored is still unknown.

To place an object on the track, use the index listed in one of the <tt>[[Wacky Wheels Track Format#Where objects are placed – *.spw|*.spw]]</tt> files. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in the index.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrell
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

User talk:Malvineous

2011-09-16T04:51:14Z

Yellowantphil: /* GamePage template */ new section

Wacky Wheels Track Format

2011-09-16T04:48:09Z

Yellowantphil: /* Road path – *.rd */ changing the calculation for the compass direction

{{NeedMoreInfo}}
{{Map Infobox
| Type = 2D tile-based
| Layers = 1
| Tile size = 32×32
| Viewport = 320×200
| Game1 = Wacky Wheels
}}

[[Wacky Wheels]] stores its levels across multiple files, with a different aspect of the level in each file.

== Level files ==

=== Map info – *.gam ===

These are ASCII text file with CRLF line terminators (DOS format). Files contain either 25 or 28 lines. (Some of the <tt>*.gam</tt> files that ship with Wacky Wheels are one line longer than they need to be, but the last line is empty.)

The first five lines give the names of [[PCX Format|PCX]] files to use. You can add new PCX files to <tt>wacky.dat</tt> and use those instead of the defaults.

Lines 9 and 10 give the position of the start line, but the computer players get confused if you move the start line too far. I think the finish line is located using the <tt>[[#.22Wrong_way.22_info_.E2.80.93_.2A.pos|*.pos]]</tt> files. The game might rely on the start line being in a relatively fixed position relative to the finish line.

{|class="wikitable"
!Line!!Description
|-
| 1 || File name of the primary tile graphics file, with the leading <tt>a_</tt> removed (e.g. <tt>f3.pcx</tt> designates <tt>a_f3.pcx</tt>)
|-
| 2 || File name of the secondary tile graphics file
|-
| 3 || File that selects properties for the primary tile graphics file (again with the leading <tt>a_</tt> removed)
|-
| 4 || File that selects properties for the secondary graphics file
|-
| 5 || File name of the sky PCX file to use (using the full file name)
|-
| 6 || Always 1250 in the <tt>*.gam</tt> files that ship with the game. Unknown use.
|-
| 7 || Always 1500. Unknown use.
|-
| 8 || Always 1. Unknown use.
|-
| 9 || X position of the start line. X=0 is at the left edge of the map as viewed in the course preview screen. The right edge is near X=2048.
|-
| 10 || Y position of the start line. Y=0 is at the top edge of the map. The bottom edge is near Y=2048.
|-
| 11–24 || Unknown. These might be (X, Y) pairs of coordinates, but I can’t figure out what they do.
|-
| 25 || 1 enables color cycling using the palette in <tt>beach.pcx</tt>; 0 disables it. See [[Wacky_Wheels#Color palettes|Color palettes]]. If set to 0, the remaining three lines are not necessary.
|-
| 26 || Delay between changing to the next color in the color cycles associated with palette indices 148 and 161–164. In <tt>a_f3.pcx</tt>, these indices are used to show water washing up onto the shore.
|-
| 27 || Delay between the end of the color cycle and restarting it, for palette indices 148 and 161–164.
|-
| 28 || Delay between changing to the next color for palette indices 168–175. There is no delay when restarting these color cycles.
|}

=== Map surface – *.m ===

The *.m files store the road surface a 64x64 grid of tiles. These files contain a 64x64 byte array (4096 bytes exactly) with each tile representing an index into the tileset. The tilesets are 320x200 images in [[PCX Format]], split into 32x32 tiles. There are only 54 tiles per image (so in the *.m files, byte values 0-53 refer to tiles 0-53 in the first tileset, and byte values 54-106 refer to tiles 0-53 in the second tileset.)

=== Background image – *.par ===

Contains the graphics used on the horizon (buildings, etc.). Raw VGA data (8bpp, no header or image size), I think.

=== "Wrong way" info – *.pos ===

The same as the background layer (<tt>*.m</tt>) except that instead of one byte per tile (8-bit number) there are two bytes per tile (16-bit number). So effectively every tile position has a 16-bit number starting at 1 and increasing as you get closer to the end of the track. The 'wrong way' message only flashes on the screen when the player moves to a tile location with a smaller number. Since the files that ship with the game are fairly coarse in this regard (only using numbers 0-30, and fairly large blocks of the map sharing the same number), there is some delay between successive 'wrong way' messages when driving around the track at low speed in the wrong direction.

=== Road path – *.rd ===

The 'road' files control the paths the computer players drive. The file begins with a [[UINT16LE]] containing the number of objects in the file, followed by that many objects. Each object is in the following structure:

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] hereX || X-coordinate of current position
|-
| [[UINT16LE]] hereY || Y-coordinate of current position
|-
| [[UINT16LE]] targetX || X-coordinate of next destination
|-
| [[UINT16LE]] targetY || Y-coordinate of next destination
|-
| [[UINT16LE]] angle || The angle given by the two (X, Y) pairs above in seemingly arbitrary units. See below.
|-
| [[UINT16LE]] compass_direction || Direction to face. Range is 0x00–0x07. 0x00 = S, 0x01 = SW, 0x02 = W, up to 0x07 = SE.
|-
| [[UINT16LE]] distance || Distance between 'here' point and 'target' point
|}

It appears that the computer players do not deviate from the paths set in the <tt>*.rd</tt> files.

==== Calculating the angle ====

For angles, north is taken to be at the top of the map. The +Y direction points down, or to the south.

The <tt>angle</tt> field is in units of degrees times 16/3 and is always positive: it ranges from 0 ≤ <tt>angle</tt> < 1920 (in decimal). The angle is zero when driving in the +X direction (due east). The +Y direction (south) is 480, west is 960, north is 1440, etc.

This angle can be calculated from the X and Y positions as follows:

angle = atan2(targetY-hereY, targetX-hereX)/π*960;
if (angle < 0) angle = angle + 1920;

==== Calculating the compass direction ====

The <tt>compass_direction</tt> field can be calculated from the <tt>angle</tt>. Since the <tt>angle</tt> variable divides a circle into 1920 units and <tt>compass_direction</tt> divides a circle into 8 units, the conversion is
compass_direction = (angle/240 + 6) % 8
where you use floating point division and then truncate the result in parentheses to an int. Rounding the result instead of truncating would probably also work.

Instead of calculating <tt>compass_direction</tt>, you can set the variable any way you like, so that the computer players drive backwards, skid in the turns, spin, etc. If you hit a driver facing you, it counts as a head on collision, even if you are both traveling the same direction.

==== Calculating the distance ====

The <tt>distance</tt> field can be calculated as:

sqrt((targetX - hereX)^2 + (targetY - hereY)^2)

Note that decimals are truncated, not rounded (i.e. in C, the result is simply cast to an int.)

=== Tile properties – *.sin ===

The structs in *.sin are 12 bytes long and arranged like this:

{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] prop0_active || boolean telling if prop0 should be considered
|-
| [[UINT16LE]] prop1_active || boolean telling if prop1 should be considered
|-
| [[UINT32LE]] prop0 || properties for color 0 in f_ma#.pcx
|-
| [[UINT16LE]] prop1 || properties for color 1 in f_ma#.pcx
|}

I think the boolean values can always be set to 1; the property won’t be used unless it’s selected in the appropriate a_ma*.pcx file. The properties select what type of ground or water that tile will be. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt gamedata.txt] for a listing that looks promising.

=== Where objects are placed – *.spw ===

Bytes 0–1 are a [[UINT16LE]] giving how many 12-byte structs follow:
{|class="wikitable"
! Data type !! Description
|-
| [[UINT16LE]] objectid || Index of the <tt>*.sp</tt> file to read for the graphics. See [[Wacky Wheels#Sprites|Sprites]] for a list.
|-
| [[UINT16LE]] unknown || Unknown; always zero
|-
| [[UINT16LE]] xcoord || 0–2048
|-
| [[UINT16LE]] ycoord || 0–2048
|-
| [[UINT16LE]] unknown || Unknown; always zero
|-
| [[INT16LE]] unknown || Unknown; always zero. Setting this number to something other than zero causes the game to cycle through many graphics. Setting it to a small negative number causes it to cycle a few times and then stop on its normal graphic.
|}

== Tools ==
See [[Wacky Wheels#Tools|Wacky Wheels Tools]] for a listing of viewers and editors for data in this format.

== Credits ==

This format was reverse engineered by [http://yellowantphil.com/wacky_wheels/ Phil Carter] and Klas Arvidsson. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

[[Category:Wacky Wheels]]

Wacky Wheels

2011-09-15T05:02:09Z

Yellowantphil: /* Tools */ wombat can edit wacky.dat

{{Stub}}

{{GamePage}}
== File formats ==

This section lists the major file formats used in the game.

* [[DAT Format (Wacky Wheels)|DAT Format]] - compressed group file storing most of the game data
* [[MID Format]] - game music in MIDI format
* [[KLM Format]] - game music in Adlib format
* [[VOC Format]] - sound effects
* [[B800 Text]] - exit screens
* [[PCX Format]] - various game graphics
* <tt>[[#Sprites|*.sp]]</tt> sprites are raw VGA data (8bpp, no header or image size)
** <tt>sprite.atr</tt> contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>
* [[Wacky Wheels Track Format]] - <tt>*.gam</tt>, <tt>*.m</tt>, <tt>*.par</tt>, <tt>*.pos</tt>, <tt>*.rd</tt>, <tt>*.sin</tt> and <tt>*.spw</tt> are all used to construct each level

==Tile appearance and properties==
* '''a_f*.pcx''': Tile graphics
* '''a_ma*.pcx''': Selects tile properties for each pixel in each tile of the tile graphics files
* '''$n.gam''': Chooses the primary and secondary tile graphics files and property files (among other things) for track $n
* '''$n.sin''': Sets tile properties 0 and 1 for each tile in track $n

For each track, there are 108 possible tiles to use. The graphics for these tiles are contained in the tile graphics files (a_f*.pcx) (see also [[#Color palettes|Color palettes]]). Each tile graphics file contains 54 tiles. The primary graphics file contains tiles 0–53 and the secondary graphics file contains 54–107. The first tile is in the top left, and they are in order left to right and top to bottom. Tile #1 is the one used outside the track.

The tile properties files (a_ma*.pcx) are laid out in the same way as the graphics files. The colors in any tile must be in the first two positions of the color palette. (The colors assigned to the color palette are not used—only the indices.) In track $n, any pixel in tile $m that is color #0 will have property #0 specified in struct $m of the file $n.sin; similarly for color #1.

See [[Wacky Wheels Track Format]] for the format of the <tt>*.gam</tt> and <tt>*.sin</tt> files.

==Color palettes==
The color palette used in each race is mostly the one set in the primary tile graphics file <tt>a_f*.pcx</tt>. This palette is also used when showing the preview map before the race. The palettes set in the other PCX files are not used. However, if color cycling is enabled in <tt>*.gam</tt>, some color indices are assigned to color cycles. An example is the shoreline in regular bronze wheels track 2. Along the shore, the colors cycle between various shades of blue and sometimes brown. These color cycles are selected with their corresponding color index. For <tt>a_f3.pcx</tt>, these indices are 148, 161–164 and 168–175. The colors set in the palette for these indices are used when displaying the preview map, or when color cycles are disabled in the <tt>[[Wacky Wheels Track Format#Map info – *.gam|*.gam]]</tt> file.

The color palette used in the color cycles is colors 0–76 in the palette of <tt>beach.pcx</tt>. The progression of color indices assigned to each color cycle of <tt>a_f*.pcx</tt> may be hard-coded into the program. The image in <tt>beach.pcx</tt> doesn’t seem to be used. There are two 32x32 squares in the image that contain a pattern of color indices from 166–175, although if you blank the entire image, the color cycles work the same as ever. (Change the colors assigned to indices 166–175 to see the pattern.)

Looking at the existing <tt>a_f*.pcx</tt> files, colors 0, 3–4, 10–111, 127–128 and 255 are always the same or nearly the same. You can safely edit any other colors in the palette without affecting the display of the sprites or screen overlays. You can probably find some other colors that are unused, or change the palette colors used in the sprites if you need more colors than that.

Note that the [http://www.gimp.org/ Gimp] doesn’t like having the same color assigned to multiple indices in the palette. For example, if you open <tt>a_f3.pcx</tt> in the Gimp, and copy and paste the deep water tile (tile #27) to tile #0 (grass), the Gimp will copy the colors over and select the first index in the palette that matches each color. This is definitely not what you want, since some indices are animated. To work around this, I slightly changed the values of some of the colors, so that the Gimp would see them as being unique. There must be a better way to do this, but I don’t know what it is.

== List of file formats ==
Most of the data files for Wacky Wheels are stored in <tt>wacky.dat</tt>, which is an archive file containing a number of other files. For the file format of <tt>wacky.dat</tt> itself, see [[DAT Format (Wacky Wheels)|DAT Format]].

=== Files in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
|<tt>ndist</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>slp</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>view</tt>
| style="background: #FFCCCC;" | Unknown
|-
|<tt>sprite.atr</tt>
| style="background: #FFFFCC;" | Contains some details for <tt>h*.sp</tt> and <tt>ob*.sp</tt>. Specific contents are unknown.
|-
| <tt>*.bin</tt>
| style="background: #CCFFCC;" | [[B800 Text]]. Registered version (<tt>wwreg.bin</tt>) and shareware (<tt>wwsw.bin</tt>) exit screens.
|-
| <tt>*.bmc</tt>
| style="background: #CCFFCC;" | Controls the computer player during demo mode. See [[BMC Format]].
|-
| <tt>trig.dat</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.fx</tt>
| style="background: #FFCCCC;" | Unknown. File names are <tt>audiohed.fx</tt> and <tt>audiot.fx</tt>; they presumably have to do with the [[VOC Format|VOC]] sound effects.
|-
| <tt>*.gam</tt>
| style="background: #FFFFCC;" | Track data. See [[Wacky Wheels Track Format]].
|-
| <tt>*.htt</tt>
| style="background: #CCFFCC;" | Default high score files for single player races. <tt>wac1.htt</tt> is the default <tt>wacky1.hi</tt> file, and <tt>wac2.htt</tt> is the default <tt>wacky2.hi</tt> file. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.inf</tt>
| style="background: #FFCCCC;" | Unknown; perhaps hotspot coordinates for sprites as seems to contain signed 32-bit integers. See [http://yellowantphil.com/wacky_wheels/downloads/gamedata.txt Klas Arvidsson’s notes].
|-
| <tt>wacky.ing</tt>
| style="background: #FFCCCC;" | Unknown. Looks like an unused default high score file, but the first 59 bytes appear to be something else.
|-
| <tt>*.klm</tt>
| style="background: #CCFFCC;" | Game music in AdLib [[KLM Format]].
|-
| <tt>*.m</tt>
| style="background: #CCFFCC;" | Track maps. See [[Wacky Wheels Track Format]].
|-
| <tt>*.mid</tt>
| style="background: #CCFFCC;" | Game music in [[MID Format|MIDI Format]].
|-
| <tt>gig.mov</tt>
| style="background: #CCFFCC;" | Controls the motion of the “giggle key” devils remain in two-player races. Also controls the devil that says “last lap.” See [[#Devil motion – gig.mov|Devil motion]].
|-
| <tt>*.ott</tt>
| style="background: #CCFFCC;" | Default time trial high score files. <tt>wac1.ott</tt> is the default <tt>wacky1.tim</tt> and <tt>wac2.ott</tt> is the default <tt>wacky2.tim</tt>. See [[#Files not in wacky.dat|Files not in <tt>wacky.dat</tt>]] for the file format.
|-
| <tt>*.par</tt>
| style="background: #CCFFCC;" | Background images for the races (buildings, etc. on the horizon). See [[Wacky Wheels Track Format]].
|-
| <tt>*.pcx</tt>
| style="background: #CCFFCC;" | Game graphics in [[PCX Format]]. Most are self-explanatory. Some files need further explanation:
* <tt>a_f*.pcx</tt>, <tt>ma_f*.pcx</tt> and <tt>beach.pcx</tt> are described in [[#Color palettes|Color palettes]].
* <tt>blank.pcx</tt> is used to draw the blue bars in a two-player race that show each racer’s name and number of hedgehogs. The file also contains graphics for each player’s number of lives, but lives aren’t used for two-player races. This area of the image is replaced with a blue bar in the game.
|-
| <tt>*.pos</tt>
| style="background: #CCFFCC;" | Determines which direction is the wrong way in a race. See [[Wacky Wheels Track Format]].
|-
| <tt>*.rd</tt>
| style="background: #CCFFCC;" | The course followed by the computer players in each race. See [[Wacky Wheels Track Format]].
|-
| <tt>wacky.sdx</tt>
| style="background: #FFCCCC;" | Unknown
|-
| <tt>*.sin</tt>
| style="background: #CCFFCC;" | Sets the properties of each type of tile. See [[Wacky Wheels Track Format]].
|-
| <tt>*.sp</tt>
| style="background: #CCFFCC;" | [[#Sprites|Sprites]]. See also <tt>sprite.atr</tt> in this table.
|-
| <tt>*.spw</tt>
| style="background: #FFFFCC;" | Where objects are placed on the map. See [[Wacky Wheels Track Format]].
|-
| <tt>*.tab</tt>
| style="background: #CCFFCC;" | Sets the top speed and acceleration curve for the human players. See [[#Changing go kart/lawnmower speed – *.tab|Changing go kart/lawnmower speed]].
|-
| <tt>*.voc</tt>
| style="background: #CCFFCC;" | Sound effects in [[VOC Format]].
|-
| <tt>map.xy</tt>
| style="background: #FFCCCC;" | Unknown
|}

=== Files not in <tt>wacky.dat</tt> ===

{|class="wikitable"
!File name!!Description
|-
| <tt>wacky.cfg</tt>
| style="background: #CCFFCC;" | Generated by <tt>setup.exe</tt>. Contains settings selected in <tt>setup.exe</tt>. Also contains saved games for one- and two-player races. See [http://yellowantphil.com/wacky_wheels/savedgames.php this page] for how to edit saved games.

The program wwsave can also edit saved games:
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp C99/C++ source code]
* [http://yellowantphil.com/wacky_wheels/downloads/wwsave.exe Windows command line program]
|-
| <tt>wacky.dtt</tt>
| style="background: #CCFFCC;" | High scores for the Wacky Duck Shoot. [http://yellowantphil.com/wacky_wheels/duckshoot.php Editing duck shoot high scores]
|-
| <tt>wacky*.hi</tt>
| style="background: #CCFFCC;" | High scores for one-player races. <tt>wacky1.hi</tt> contains high scores for 12 hp engines, and <tt>wacky2.hi</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/1player.php Editing single player race scores]
|-
| <tt>wacky*.tim</tt>
| style="background: #CCFFCC;" | High scores for time trials. <tt>wacky1.tim</tt> is for 12 hp engines, and <tt>wacky2.tim</tt> is for 6 hp engines. [http://yellowantphil.com/wacky_wheels/timetrial.php Editing time trial scores]
|}

== Miscellaneous File Formats ==
=== Changing go kart/lawnmower speed – <tt>*.tab</tt> ===
The files <tt>*.tab</tt> set the player speeds for 12 hp and 6 hp engines: <tt>vel.tab</tt> is for 12 hp engines and <tt>vel2.tab</tt> is for 6 hp engines. Each file contains 200 [[INT16LE]] integers that designate the human player’s go kart/lawnmower speed as it accelerates. The first number is presumably zero, and the last number is the top speed (80 mph by default for 12 hp engines). The computer players will automatically adjust their speed to be competitive with you.

You drive backwards if you set the speeds to be negative. So far, I have only set speeds in a linear progression, but other curves should be possible. The in-game speedometer can only read to 99 mph, but you can try to drive as fast as 32,767 mph if you want to. (Good luck.)

=== Devil motion – <tt>gig.mov</tt> ===
The devil that appears at the end of the last lap, and the devils that pop up in two–player races when you hit the “giggle keys,” all move according to the data in <tt>gig.mov</tt>. The first two bytes in the file are a [[UINT16LE]] integer giving the number of structs that follow minus one (i.e., there is one more struct in the file than you would think). The default length integer is 0x50, designating 0x51 or 81 structs. You can set the length lower (down to zero), but if you set it longer, the game might crash or act erratically.

Each struct is 4 bytes long and contains a signed (X, Y) pair of coordinates:
{|class="wikitable"
!Data type!!Description
|-
| [[INT16LE]] Xpos || X-position of the devil relative to its default position (off to the right for the last lap devil, and in the middle of the screen for the other devils). The positive direction is to the right.
|-
| [[INT16LE]] Ypos || Y-position of the devil relative to its default position. The positive direction is down.
|}

The game shows the devil at each (X, Y) position for about 0.1 seconds. Once there are no more (X, Y) pairs, the devil disappears in a puff of smoke.

== Sprites ==

These tables list what sprites are in each <tt>*.sp</tt> file. The sprites are raw VGA data (8bpp, no header or image size).

The file <tt>sprite.atr</tt> contains additional data for these files, but what data is stored is still unknown.

To place an object on the track, use the index listed in one of the <tt>[[Wacky Wheels Track Format#Where objects are placed – *.spw|*.spw]]</tt> files. The files <tt>h3.sp</tt> and <tt>h13.sp</tt> do not exist, so are skipped in the index.

{| style="float: left;" class="wikitable"
! Index !! File name !! Description
|-
| 0 || <tt>h1.sp</tt> || Matchbox
|-
| 1 || <tt>h2.sp</tt> || Newspaper hedgehog
|-
| 2 || <tt>h4.sp</tt> || Sweeping hedgehog
|-
| 3 || <tt>h5.sp</tt> || Demolition hedgehog
|-
| 4 || <tt>h6.sp</tt> || Toilet hedgehog
|-
| 5 || <tt>h7.sp</tt> || Jackhammer hedgehog
|-
| 6 || <tt>h8.sp</tt> || Dancing hedgehog
|-
| 7 || <tt>h9.sp</tt> || Yo yo hedgehog
|-
| 8 || <tt>h10.sp</tt> || Machine gun hedgehog
|-
| 9 || <tt>h11.sp</tt> || Jumping jacks hedgehog
|-
| 10 || <tt>h12.sp</tt> || Bomb
|-
| 11 || <tt>h14.sp</tt> || Rock pick hedgehog
|-
| 12 || <tt>h15.sp</tt> || Devil pups
|-
| 13 || <tt>h16.sp</tt> || Oil can
|-
| 14 || <tt>h17.sp</tt> || Guard hedgehog
|-
| 15 || <tt>h18.sp</tt> || Bouncing ball hedgehog
|-
| 16 || <tt>h19.sp</tt> || Golfing hedgehog
|-
| 17 || <tt>h20.sp</tt> || Upside down hog (item pickup)
|-
| 18 || <tt>h21.sp</tt> || Dice hedgehog
|-
| 19 || <tt>h22.sp</tt> || Weightlifting hedgehog
|-
| 20 || <tt>h23.sp</tt> || Backflip hedgehog
|-
| 21 || <tt>h24.sp</tt> || Trench coat hedgehog
|-
| 22 || <tt>h25.sp</tt> || Pool hedgehog
|}

{|class="wikitable"
! Index !! File name !! Description
|-
| 23 || <tt>ob1.sp</tt> || Stack of tires
|-
| 24 || <tt>ob2.sp</tt> || One cattail plant
|-
| 25 || <tt>ob3.sp</tt> || Wooden pole with white and red stripes
|-
| 26 || <tt>ob4.sp</tt> || Cactus
|-
| 27 || <tt>ob5.sp</tt> || Red barrel
|-
| 28 || <tt>ob6.sp</tt> || Yellow barrel
|-
| 29 || <tt>ob7.sp</tt> || Green barrell
|-
| 30 || <tt>ob8.sp</tt> || Tires stacked over wooden pole
|-
| 31 || <tt>ob9.sp</tt> || Three cattail plants
|-
| 32 || <tt>ob10.sp</tt> || Yellow and gray striped pole
|-
| 33 || <tt>ob11.sp</tt> || Yellow and red striped pole
|-
| 34 || <tt>ob12.sp</tt> || Bush
|-
| 35 || <tt>ob13.sp</tt> || Wooden pole
|}
 

== Notes ==

* Wacky Wheels does not read files from the current directory first, before falling back to <tt>WACKY.DAT</tt>. This means any modified files must be packaged up into the DAT file before they can be tested.

== Tools ==

{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| grp = Edit
| map = Edit
| gfx = Edit
| mus = Edit
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| grp = Edit
| map = Read
| gfx = Read
| mus = Read
| sfx = Read
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [http://yellowantphil.com/wacky_wheels/downloads/wwsave.cpp wwsave]
| Platform = Win/Linux/Mac console
| grp = No
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = Edit
| exe = No
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor Wextract]
| Platform = DOS
| grp = Read
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

== See also ==
* [http://yellowantphil.com/wacky_wheels/wackydat.php Phil’s Wacky Wheels site] (some modding info)

[[Category:Apogee]]
[[Category:3D]]
[[Category:Driving]]

DAT Format (Wacky Wheels)

2011-09-15T04:53:11Z

Yellowantphil: /* Tools */ Wombat can replace files in wacky.dat

The '''DAT format''' is used to store most of the data for [[Wacky Wheels]]. Unfortunately the format has no signature and a generic filename extension (.dat) so automatic detection of these files is difficult.

Wacky Wheels does not check the current directory for files before falling back to the DAT file, so any changed files must be merged into the DAT file before the game will see them.

== File format ==

=== Signature ===

There is no signature for this format. One method to identify files is to read in the file entries (failing if the end of the file is reached early) and confirm that each filename only consists of ASCII characters or nulls, and each file offset plus its size is less than the total size of the DAT file. It is extremely unlikely that this method would incorrectly identify a file.

=== Header ===

The file starts with a single field indicating the number of files present.

{|class="wikitable"
!Data type!!Description
|-
|UINT16LE numFiles||File count
|}

=== File entry ===

After the two-byte header, the following structure is repeated <tt>numFiles</tt> times. As each entry includes both an offset and a size, it is possible (in theory) for two different files to share the same data, and to insert "hidden" data between files.

{|class="wikitable"
!Data type!!Description
|-
|BYTE filename[14]||Filename (8.3, 12 chars including dot, null padded to 14 chars)
|-
|UINT32LE size||File size
|-
|UINT32LE offset||File offset (see below)
|}

The file offsets don't include the two-byte file count in the header, so an <tt>offset</tt> of 10 means the file actually starts at 12 bytes from the beginning of the DAT file.

== Tools ==

{{BeginFileFormatTools|Type=group}}
{{FileFormatTool
| Name = [[Camoto]]
| Platform = Linux console/GUI
| canExtract = Yes
| canDecompress = N/A
| canCreate = Yes
| canModify = Yes
| canCompress = N/A
| editHidden = No
| editMetadata = N/A
}}
{{FileFormatTool
| Name = [[Wombat]]
| Platform = Windows GUI
| canExtract = Yes
| canDecompress = N/A
| canCreate = No
| canModify = Yes
| canCompress = N/A
| editHidden = No
| editMetadata = N/A
}}
{{FileFormatTool
| Name = [http://sfprod.shikadi.net/old/games/wackywheels.htm#extractor wextract]
| Platform = DOS
| canExtract = Yes
| canDecompress = N/A
| canCreate = No
| canModify = No
| canCompress = N/A
| editHidden = No
| editMetadata = N/A
}}
{{EndFileFormatTools}}

[[Category:File Formats]]
[[Category:Group Files]]
[[Category:Group Files supporting hidden data]]


[[Category:Wacky Wheels]]