spyguy0045
New member
Memory card and sound issues fixed in Rush 2049.
What do you want in Project64 ?
- Thread starter zilmar
- Start date
Agozer
16-bit Corpse | Moderator
Was the original N64 able to play GB, NES, or SNES games? No. Project 64 is a Nintendo 64 emulator. The purpose of the emulator is to emulate a single console, not not every single pre-GameCube console.
Use a Gameboy, NES and SNES emulators to play Gameboy, NES, and SNES games. Or, if you really want an emulator that can emulate many consoles at once, use MESS.
Last edited:
Doomulation
?????????????????????????
More compability with drivers? Are you implying you are seeing graphics bugs in the emulation? Or do you want more graphics card compability (ie more cards should work)?
Emulation can be a memory hog; I don't think this will change.
Perhaps you should be more specific.
I don't know if this has been mentioned, because I haven't read through all the posts, but one of the things PJ64 is seriously lacking is debugging. Breakpointing, stepping through the code, registry viewer at that time, memory viewer, ram searcher (similar to GameShark Pro's code searching) would be extremely nice. Also, it would be nice if after code searching you could turn codes on straight from the results (for testing), and be able to search certain ranges, have flags to ignore values in a certain range, ignore pointers.
One thing I've noticed is that if you turn on gameshark codes that affect the assembly code (mid-game) for certain games , for example Donkey Kong 64, it doesn't take effect until the ROM is restarted by pressing F1. Does this have to do with how PJ64 handles TLB or something along those lines?
One thing I've noticed is that if you turn on gameshark codes that affect the assembly code (mid-game) for certain games , for example Donkey Kong 64, it doesn't take effect until the ROM is restarted by pressing F1. Does this have to do with how PJ64 handles TLB or something along those lines?
Last edited:
cooliscool
Nintendo Zealot
Mentioned it several times in this thread, SubDrag. 
One thing Nemu64 has that PJ doesn't.
One thing Nemu64 has that PJ doesn't.
Iconoclast
New member
Actually, there are several things that Nemu64 has that Project64 1.6 doesn't have:Mentioned it several times in this thread, SubDrag.
- NetPlay
- Debugging
- VRML Geometry Logging (in video plugin that cannot be used with Project64)
- Different core emulation method that does not involve the specification of Counter Factor settings and such.
- Probably the best goddamn audio plugin out there, a combination of the abilities of Azimer's Audio HLE, Jabo's DirectSound, and zilmar's No Sound plugin, made by LaC. The audio plugin is better than all three of these audio plugins combined. It's only flaw is its perversive sound emulation of GoldenEye 007.
cooliscool
Nintendo Zealot
I agree, LaC's audio is amazing.
Iconoclast
New member
Yeah. It sucks that you can't use it with any other emulator. You can, however, use Nemu64's graphics plugin with all other emulators (except for Project64, for some odd reason). Just copy GS_DLL.DLL from Nemu64.exe's directory to EmulatorName.exe's directory, copy LemD3D8.dll to the Plugin folder of that emulator, and there you go. A shame you can't do the same with the audio plugin. The graphics plugin, however, isn't so good...it is only good at emulating a couple games like Aidyn Chronicles and Star Wars Rogue Squadron. Had Project64 not had a core issue with loading this plugin, that game would have been playable today.
As for the input plugin, Idk who made that, Lemmy or LaC, but it's about the same level as Jabo's DirectInput...there are better, and there are worse.
But enough of my spamming. Back to PJ64 suggestions.
squall_leonhart
The Great Gunblade Wielder
i think hes referring to the broken framebuffer issues on NV40+ that causes the link display in OoT to appear as a white rectangle
squall_leonhart
The Great Gunblade Wielder
Jabo had an Opengl plugin but support has been dropped for it,... not sure why..
Iconoclast
New member
I'm estimating it's because DirectX plugins are faster than OpenGL, and while plugins like Glide64 work best using the OpenGL rendering engine, many are too ignorant to realize that plugins like Rice's Video 6.1.1 and Jabo's graphics, when using OpenGL, just don't work very well with graphics or speed.
The user is also saying, he wants to use a plugin that actually works. Obviously, this user's system specifications are so low (or at least DirectX version and/or video card), if he can't even get DirectX plugins working, OpenGL isn't even worth trying.
Doomulation
?????????????????????????
Not quite. DirectX vs OpenGL is pretty much equal in soeed. It all depends on HOW you use the API. It's just that some prefer DirectX and some OpenGL. OpenGL is also portable which DirectX isn't.
Jabo, may have for example, chosen DirectX because Jabo knows it better than OpenGL. Similarly, Hacktarux would use OpenGL since DirectX isn't available on non-Windows platforms.
There are games out there with great speed with OpenGL and there are games with DirectX. It's just a matter of preference. Well, almost always.
Jabo, may have for example, chosen DirectX because Jabo knows it better than OpenGL. Similarly, Hacktarux would use OpenGL since DirectX isn't available on non-Windows platforms.
There are games out there with great speed with OpenGL and there are games with DirectX. It's just a matter of preference. Well, almost always.
squall_leonhart
The Great Gunblade Wielder
actually low end geforce cards run faster in opengl then in Direct3D
Opengl is always faster on nvidia cards as they define almost the entire Opengl spec...
this was more likely because Jabo knows DirectX better then opengl
or possibly Opengl didn't have the features he wanted at the time?
Opengl is always faster on nvidia cards as they define almost the entire Opengl spec...
this was more likely because Jabo knows DirectX better then opengl
or possibly Opengl didn't have the features he wanted at the time?
squall_leonhart
The Great Gunblade Wielder
Opengl is usually not very well supported on such devices,.. but neither is direct 3d really...
Iconoclast
New member
Not for me. OpenGL only goes up to 70 FPS over here, while DirectX...300 at most.