Difference between revisions of "Talk:INTER.DAT"
Jump to navigation
Jump to search
m (format mistake) |
(Additional offsets) |
||
| Line 1: | Line 1: | ||
Just for reference before I forget. Not sure enough yet for main article page. | Just for reference before I forget. Not sure enough yet for main article page. | ||
| − | *0x12 (word): y position of | + | |
| − | *0x14 (word): x position( | + | File length 0x238 568 bytes |
| + | 4 records per interception window x Record length 0x8E 142 bytes | ||
| + | |||
| + | Record structure: | ||
| + | *0x00 (word): ??damage?? total guess | ||
| + | *0x02 (word): eg '''02 00''' | ||
| + | *0x04/6/8 (words): 3-4-3 2-3-2 1-2-1 1-1-0 (hidden). Some kind of previous/next window list? Window depth/tiling? | ||
| + | *0x0a (word): eg '''08 00''' | ||
| + | *0x0c (word): eg '''04 00''' | ||
| + | *0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word). | ||
| + | *0x14 (word): x position of window (x position is accessed as a word) | ||
*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]]) | *0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]]) | ||
*0x18 (word): count down before the status message is cleared | *0x18 (word): count down before the status message is cleared | ||
*0x1A (word): firing mode | *0x1A (word): firing mode | ||
| − | *0x1E (word): requested distance to target | + | *0x1C (word): ?current distance to target? (km x8) eg '''30 02''' = 560 = 70km (stand off) |
| + | *0x1E (word): requested distance to target (km x8) | ||
| + | *0x22 (word): air speed (current? max?) eg '''18 15''' = 5,400 = Avenger | ||
*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft | *0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft | ||
*0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data | craft builtin stats]] | *0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data | craft builtin stats]] | ||
Revision as of 01:19, 17 February 2010
Just for reference before I forget. Not sure enough yet for main article page.
File length 0x238 568 bytes 4 records per interception window x Record length 0x8E 142 bytes
Record structure:
- 0x00 (word): ??damage?? total guess
- 0x02 (word): eg 02 00
- 0x04/6/8 (words): 3-4-3 2-3-2 1-2-1 1-1-0 (hidden). Some kind of previous/next window list? Window depth/tiling?
- 0x0a (word): eg 08 00
- 0x0c (word): eg 04 00
- 0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word).
- 0x14 (word): x position of window (x position is accessed as a word)
- 0x16 (word): status message (starting at offset 0x397 in ENGLISH.DAT)
- 0x18 (word): count down before the status message is cleared
- 0x1A (word): firing mode
- 0x1C (word): ?current distance to target? (km x8) eg 30 02 = 560 = 70km (stand off)
- 0x1E (word): requested distance to target (km x8)
- 0x22 (word): air speed (current? max?) eg 18 15 = 5,400 = Avenger
- 0x76 (dword): memory pointer to CRAFT.DAT entry of the attacking craft
- 0x7A (dword): memory pointer to attacking craft builtin stats
- 0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO
- 0x8A (dword): memory pointer to attacked craft builtin stats
Logging Interception status window messages to file?
Dude, if there is any way you could enable your Extender to log the status messages out to a log file that would really help me in figuring out the air combat mechanics. It's very difficult/impossible to reliably read the status messages off the screen. And there are not that many other options to be able to count when a craft hits or misses another craft. But then you are probably way ahead of me on figuring out the mechanics since you are decompiling the logic directly! :)
cheers, Spike 06:52, 5 July 2009 (EDT)