Changes
Jump to navigation
Jump to search
Created page with "By MaKiPL ---------- This is generic MAGfiles article. Use this to reffer if file is either .nn (where nn is digit/number) or .N.dat (where n is literal) and therefore you do..."
By MaKiPL
----------
This is generic MAGfiles article. Use this to reffer if file is either .nn (where nn is digit/number) or .N.dat (where n is literal) and therefore you don't know if given file is mag_t, mag_s, mag_p or mag_r. You made need to use HEX editor.
== General info about MAG files ==
MAG files are complete sequences for magic and G.Fs. These files contain textures, geometry data, camera movement, special effects, script data and AKAO frames. Sometimes, the naming is correct, but in some files the naming is completely messed up (00,01,02... or a,b,c(...).dat. Use below samples to know which format is which file.
The engine loads files by sequences. Some magic files are just one sequence, but some (especially G.Fs) are multi sequenced files. The engine loads files by sequences. When one sequence is ending, the second one is loaded in the place of the first one (not really, the sizes are varied, and the addresses are not static). After G.F. is over, the latest sequence is still in memory. It's just overwritten when needed.
TODO
----------
This is generic MAGfiles article. Use this to reffer if file is either .nn (where nn is digit/number) or .N.dat (where n is literal) and therefore you don't know if given file is mag_t, mag_s, mag_p or mag_r. You made need to use HEX editor.
== General info about MAG files ==
MAG files are complete sequences for magic and G.Fs. These files contain textures, geometry data, camera movement, special effects, script data and AKAO frames. Sometimes, the naming is correct, but in some files the naming is completely messed up (00,01,02... or a,b,c(...).dat. Use below samples to know which format is which file.
The engine loads files by sequences. Some magic files are just one sequence, but some (especially G.Fs) are multi sequenced files. The engine loads files by sequences. When one sequence is ending, the second one is loaded in the place of the first one (not really, the sizes are varied, and the addresses are not static). After G.F. is over, the latest sequence is still in memory. It's just overwritten when needed.
TODO
