Additional
Well, I've just figured out why the hell the game was reading in too much stuff (two bytes of info each time even though I asked it to read in only one byte). I quote from the MW extended scripting manual:
Reads the number of SHORTS (2 bytes) requested from the file
Duh me- the game was reading two bytes (not one) cause it's the shortest amount of info that the ReadFile function can read in...
Also seem to have noticed a backwards pattern in the way numbers are read in... if you have "1a 2b" in the hex file, it'll end up in the game as "2b 1a"... hoping this will not be a problem- the number in the binary file would have been 6699 (1a 2b) whereas the game would read it in as 11034 (2b 1a)... may just have to reverse the bytes as soon as they're read in
Reads the number of SHORTS (2 bytes) requested from the file
Duh me- the game was reading two bytes (not one) cause it's the shortest amount of info that the ReadFile function can read in...
Also seem to have noticed a backwards pattern in the way numbers are read in... if you have "1a 2b" in the hex file, it'll end up in the game as "2b 1a"... hoping this will not be a problem- the number in the binary file would have been 6699 (1a 2b) whereas the game would read it in as 11034 (2b 1a)... may just have to reverse the bytes as soon as they're read in
0 Comments:
Post a Comment
<< Home