While purists held that a proper first-person shooter couldn't exist without a mouse and keyboard, the N64's analog stick was just begging to test this theory. For several years the genre continued to be refined on the PC, but due to the physical and technical limitations of home gaming systems of the era, it was not able to make the leap to consoles. Wolfenstein is credited with not only inventing the genre, but defining how it was designed, packaged and played on the PC. Although the genre can trace its roots all the way back to 1973 with a largely unknown game, Maze War, it was not popularized until 1992 when a little shareware title called Wolfenstein 3D was released. In addition to its accomplishment of being a film-to-game adaptation that didn't suck, GoldenEye is largely responsible for bringing the then almost exclusively computer-based FPS genre to consoles, and thus, a much broader audience. and ridiculously lenient auto-aim tend to overshadow how revolutionary it was for its time and the huge impact it had on the development of other shooters.
While its fun factor has not diminished one tiny bit, its blocky graphics, questionable A.I. damn^^ĮDIT2: well, this function is also used for reading, as its meant to be a call, "writing" the arguments makes sense:Ĭode: Select all static UInt64 Hash(byte data)įor (int i = data.True, when compared to modern first-person shooters, GoldenEye does prove to be more than a little dated. with these two "magic" numbers I found a single hit in goldeneye's rom, at 0x80015F4C !ĮDIT1: lol, just noticed, im stupid, the cpu has an PROGRAM_COUNTER member, it told me it was at 0x70015f4c, well ignoring the upper part, I could have just seen the XXX15F4C and replace the XXX with 800. To do this, I got the source of project64, compiled it, ran it in interpreter mode, set a breakpoint on the eeprom command for writing to it, then looked up the actual opcode (AD 49 00 10), stepped the cpu and noted the very next opcode (8F AB 00 18). eeproms are accessed linewise, that means 8 bytes at a time and this function is called 64 times = 512 byte Learning new stuff all the time! I think I found the spot where the actual write of eeprom (if no save exists yet) is done.
0 kommentar(er)
