Wed Mar 29, 2006 11:20 pm by niktaw
you're using a complete beta version of the emulator, and 99% of commercial ROMs won't work with it. here's what the creator, PSMonkey, who by the way proved a lot of people wrong when he released this emulator earlier today, has to say about it.
"Well sorry I am late but here is the much promised first release of monkey64. I was hopping for better at the last min but it still passed my expectations for a first build.
A few things to note:
* While RSP & RDP emulation is started it is far from complete. As well there are still numerous issues in the main CPU core. I plan to fix things as soon as I can get to them.
* This won't run mario64 or 99% of the n64 library. Some ROMs are starting to do things with Mortal Kombat Trilogy actually being playable (to some extent).
* I know there are odd looking color squares when running some commercial ROMs (like mortal kombat). The reason is because I have not completed texture support in RDP. I am hoping to get a revision out ASAP once this is fixed.
* The emulator is slow. Some PD ROMs do a pretty nice framerate but games like mortal kombat do about 5fps. This is due to the emulator still being on a pure interpreter core. In good time I will build a dynamic recompiler so we can get some more playable framerate.
* The app is in user mode. So it is quite possible this works on 2.0+ PSP units. I just sadly don't have the time to check.
Well that is it. Do enjoy. The zip contains a few favorite PD ROMs. Pong by Oman is a must play IMO. Also if you're all curious what mortal kombat trilogy looks like in game. Please see attached screenshot on forums.
PS. Mortal Kombat Trilogy [!] dump wont work. [b1] dump runs just fine. When you see the second screen, press start as it's just warning you that there is only 1 controller plugged in.
The screen flickering is because it's not doing double buffering on the PSP. It's just directly rendering to the display screen. I was trying to fix this at lunch but ran into problems so I gave up since I wanted to push the build out ASAP. I'll have it fixed for the v1.1 build."