Announcement: Cycle-accurate N64 development underway.
- Thread starter MarathonMan
- Start date
Reznor007
New member
Ville did submit the initial N64 driver, but the current version isn't remotely like the original. He hasn't messed with it in quite some time. He's been working on various exotic 3d arcade hardware as seen on his WIP page:
http://vlinde.mameworld.info/
OP
MarathonMan
Emulator Developer
- Thread Starter
- #703
Long-term goal. He's probably measuring amount of time it takes to issue DMA requests* and all kinds of fancy things. I could only guess at the number of things marshallh has done to prevent it from running at emulators. Maybe someday down the road I'll have all of those things implemented properly with correct timings so that ROM works, but not anytime soon likely.
Last edited:
ShadowFX
Guardian
Compatibility 2013.8.31 - Test 1
I went through an awful lot sports games this time around. Sports games are not my favorite games to play so it took me awhile to get them all through CEN64.
(I do running in real life though
)
Info:
- 'Running' means either it gives a black screen later on in the game, freezes or is unplayable due to too much corrupt graphics.
- 'in-game controller pak error' means I'm unable to progress any further into the game.
- 'in-game audio error' means I'm unable to progress any further into the game.
- Bolded titles are the last ones tested and might have been affected by changes.
Previous compatibility tests:
Compatibility 2013.8.25 - Test 2
I went through an awful lot sports games this time around. Sports games are not my favorite games to play so it took me awhile to get them all through CEN64.
(I do running in real life though
)Info:
- 'Running' means either it gives a black screen later on in the game, freezes or is unplayable due to too much corrupt graphics.
- 'in-game controller pak error' means I'm unable to progress any further into the game.
- 'in-game audio error' means I'm unable to progress any further into the game.
- Bolded titles are the last ones tested and might have been affected by changes.
Previous compatibility tests:
Compatibility 2013.8.25 - Test 2
Last edited:
OP
MarathonMan
Emulator Developer
- Thread Starter
- #705
I went through an awful lot sports games this time around. Sports games are not my favorite games to play so it took me awhile to get them all through CEN64.
(I do running in real life though
Info:
- 'Running' means either it gives a black screen later on in the game, freezes or is unplayable due to too much corrupt graphics.
- 'in-game controller pak error' means I'm unable to progress any further into the game.
- 'in-game audio error' means I'm unable to progress any further into the game.
- Bolded titles are the last ones tested and might have been affected by changes.
Previous compatibility tests:
Compatibility 2013.8.25 - Test 2
Keep up the great work, this is helping immensely. It's so easy to find bugs when you can pickout the games.
Found some major VR4300 FPU issues that are being fixed; Bomberman Intro now looks much better, but freezes at the same point still.
ShadowFX
Guardian
Compatibility 2013.8.31 - Test 2
With this latest batch of ROMs, I believe I went through most if not all the commercial games within the US N64 library.
Info:
- 'Running' means either it gives a black screen later on in the game, freezes or is unplayable due to too much corrupt graphics.
- 'in-game controller pak error' means I'm unable to progress any further into the game.
- 'in-game audio error' means I'm unable to progress any further into the game.
- Bolded titles are the last ones tested and might have been affected by changes.
Previous compatibility tests:
Compatibility 2013.8.31 - Test 1
With this latest batch of ROMs, I believe I went through most if not all the commercial games within the US N64 library.
Info:
- 'Running' means either it gives a black screen later on in the game, freezes or is unplayable due to too much corrupt graphics.
- 'in-game controller pak error' means I'm unable to progress any further into the game.
- 'in-game audio error' means I'm unable to progress any further into the game.
- Bolded titles are the last ones tested and might have been affected by changes.
Previous compatibility tests:
Compatibility 2013.8.31 - Test 1
Last edited:
OP
MarathonMan
Emulator Developer
- Thread Starter
- #708
Wuhuuuu
Had to do some makefile tweaks (add -lGL and -lglfw2 instead of plain -lglfw to linkers) to compile on Arch, but looking good
EDIT: That VI cutoff :/ was pretty consistent around 30 - 40ish
Thanks for mentioning your issues; realized I should have written the Makefile differently. Fixed to use pkg-config libglfw for distros that don't use -lglfw. Should fix -lGL as well, hopefully.
VI cutoff sounds about right. It's not fullspeed right now.
You should be able to dump a PAL PIFROM with your PAL console using hacktarux's method mentioned a few pages back if you're interested.
Last edited:
Nintendo Maniac
New member
It just hit me, since this is doing software rendering it should work on even the lowest of the low Intel iGPs, right?
OP
MarathonMan
Emulator Developer
- Thread Starter
- #710
Yes, since it uses MooglyGuy+MAME's RDP, it renders everything in software. The only OpenGL calls that ever gets executed copies the rendered frame into the card's texture memory and slaps it on the face of a quad. Even software renders (MESA) have been able to handle it fine in my experience albeit at a minor performance hit.
Nintendo Maniac
New member
Heck it might even work in a VM then.
EDIT: Yo dawg much?
EDIT: Yo dawg much?
Last edited:
OP
MarathonMan
Emulator Developer
- Thread Starter
- #713
I'm still tracking the one bug that's preventing a vast majority of games from rebooting. RSP tasks are essentially getting corrupted to the point where the whole thing comes crashing down, but only for some ROMs? I know the RSP DMAs are the direct cause of the corruptions, but I'm not sure why the bad DMAs are being requested other then bad display/audio lists being sent to the RSP.
F
Fanatic 64
Guest
Kinda off-topic, but I would like to mention that newer Intel IGPs (everything past the Intel HD Graphics 2000) are good enough even for HLE. The myth that Intel IGPs are bad for N64 emulation seems to stem from the fact that Jabo's plugin glitches up with them (which is currently the only plugin that does that, Rice did it but was fixed, and all other plugins work fine). But properly coded they work just as good as a 3dfx Voodoo or Nvida GTX Titan, for N64 emulation
Also, really nice to see this emulator is already running commercial games. You're doing great MarathonMan!
Nintendo Maniac
New member
Kinda off-topic, but I would like to mention that newer Intel IGPs (everything past the Intel HD Graphics 2000) are good enough even for HLE. The myth that Intel IGPs are bad for N64 emulation seems to stem from the fact that Jabo's plugin glitches up with them (which is currently the only plugin that does that, Rice did it but was fixed, and all other plugins work fine). But properly coded they work just as good as a 3dfx Voodoo or Nvida GTX Titan, for N64 emulation
I am well aware of this considering that the HD4600 is even fast enough to render games Dolphin at 720p. This is why I specifically said the "lowest of the low Intel iGPs", referring specifically to Intel iGPs that are extremely low-end.
Depending on your standards, this may include things like the Intel X3100 or may refer only to things that are older than, say, the Intel 945GA.
Last edited:
OP
MarathonMan
Emulator Developer
- Thread Starter
- #717
No, won't help in the slightest beyond what you've done now as I already have so many backlogged bugs.
It would be reassuring to know the non-NTSC PIFROM boot, but I don't see why they wouldn't.
OP
MarathonMan
Emulator Developer
- Thread Starter
- #718
Er, so, whoever said the MESS RDP isn't vectorizable is just plain wrong.
I just screwed around for a couple hours and dropped by binary size by 4K. There's an incredible amount of things that can be done.
Not only is this going to improve the instruction throughput, but also reduce the cache trashing that the RDP causes.
I just screwed around for a couple hours and dropped by binary size by 4K. There's an incredible amount of things that can be done.
Not only is this going to improve the instruction throughput, but also reduce the cache trashing that the RDP causes.
Last edited:
Nintendo Maniac
New member
To their credit, it kind of made some sense up until last year when the fastest AMD CPU you could get didn't support it. Luckily Piledriver and Vishera renders that moot.