Hello. I've been digging through the internet for the Random access memory addresses or Read Only Memory Addresses for a universal camera hack for Nintendo 64 games. In case you didn't know, Super Smash Bros original for Nintendo 64 already has a said Gameshark code to allow you to zoom the camera in (I read this from another website, can't say or remember which one)
I was thinking that you could probably do this with any game, but it may take some tweaking around. I'm specifically talking about games with 3D world and models made for the Nintendo 64. (Instance, Super Smash Bros or Pokemon Stadium 1 and 2)
As of right now, there is little knowledge of Pokemon Stadium 2's Random Access Memory Addresses and Read Only Memory Addresses and their function, and not all of Pokemon Stadium 1's RAM (Random Access Memory) Addresses and ROM (Read-Only Memory) Addresses' functions on DataCrystal's list for ROMhacking.net wiki are known/revealed.
This leaves me baffled as to how the ROMhackers got all of the addresses for mostly every details about the graphics... but nothing about the camera.
I am on Windows 10 Pro 64bit, Nvidia Geforce GT 1060, Intel i7 7700K Performance, ASUStek Motherboard (Make unknown, custom built)
I use Project 64's debug function to search for the memory addresses (I used to use Cheat Engine, but as I found out, it uses my Computer's RAM or something that utilizes dynamic addresses that change with each restart, save state save and load, etc. I need something that finds the STATIC addresses for the cameras)
If someone could point me towards a smaller set of addresses that might control the camera (should be a set of 8 or less addresses.), this may actually work, as Project 64 takes forever to find a large range of addresses (and eventually throws an "Outofmemory" like error before finishing)
My theory is that the address may be located in the 0x8000000 to 0x8FFFFFF addresses, just like everything else pointed out in the romhacking datacrystal wiki for Pokemon Stadium 1, but this still leaves 268435455 addresses, and typically, a 32 GB ram of computer cannot search that much within Project 64's own debug memory interface... too much memory involved.
Perhaps someone with more knowledge of exactly how camera addresses work could point me to the correct range of addresses (No more than 50000 addresses, or, within a C350 hex address range, example, 0x80000000-0x8000C350)
To make it simpler, you only need to search when the camera changes positions (goes from one place to another, you would search for a "Changed Value") or simply seem to stand "Completely still" (You would search for an Unchanged value). By searching during these times (like I did with cheat engine), you can narrow down the results dramatically. However, if your results are limited to 50000 results, you will only recieve 50000 results, of which, have about a 50,000/4,294,967,295 chance of even finding the correct address, which means, your said address may not exist within the 50000 results!
That's why I need it narrowed down. I have 4,294,967,295 addresses, and only 50,000 of them are returned, and always the same ones. If I seach the 0x80000000 to 0x8FFFFFF address range, that still leaves me with 268,385,455 of 268,435,455 unsearched addresses.
I don't know any way to do this through project 64. And the address range in cheat engine (0x30000000 - 0x3FFFFFFF) are not the same ones as in the actual Project64 emulator (Dynamic Addresses VS. static addresses)