when i wanna play pj64 ( 1.5 ) it says " Direct3D failed to initialize your HAL device, make sure you have a properly configured 3D graphics card compatible with Direct3D 6.0" then when i hit ok it then says " The default or selected video plugin is missing or invalid. check that you have at least one compatible plugin in the folder. "
Missing default plugin?
- Thread starter Link318
- Start date
Iconoclast
New member
Try installing Project64 1.6. If it gives you the error message again, wait for a plugin change dialoge to come up. Set your graphics plugin to Jabo's Direct3D 8, click OK, and now try playing the game.
If that doesn't work, then the cause is your graphics card/drivers, if you even have one.
If that doesn't work, then the cause is your graphics card/drivers, if you even have one.
Iconoclast
New member
An issue like that is not a fault of the version of Project64 you use.
To be honest, though, I like Mupen64's core better. Try installing that if Direct3D won't start up on your system.
To be honest, though, I like Mupen64's core better. Try installing that if Direct3D won't start up on your system.
Smiff
Emutalk Member
doesn't make any sense - this is a plugin problem, not core.
there are various suggestions about this in the support section on pj64.net
Iconoclast
New member
It IS a plugin problem, but I was just saying, not only has Mupen64's core fixed core game issues that no other emulator has, but it comes with an OpenGL plugin that may initialize properly but it's also relatively difficult to install to the other emulators, thanks to Glide3x.dll, meaning, he may not understand the instructions for installing the plugin.
I'm not saying, use Mupen64 because it's better; I'm saying, use Mupen64 because it comes with a plugin that, for your system, may work better, and while I'm at it, I kind of seen better overall results from its core. If Glide64 didn't come with Mupen64, I would've attempted to tell him how to install it to Project64 instead, but my opinion was off-topic.
I'm not saying, use Mupen64 because it's better; I'm saying, use Mupen64 because it comes with a plugin that, for your system, may work better, and while I'm at it, I kind of seen better overall results from its core. If Glide64 didn't come with Mupen64, I would've attempted to tell him how to install it to Project64 instead, but my opinion was off-topic.
squall_leonhart
The Great Gunblade Wielder
how hard is it to copy glid3x.dll into the same folder as the emulator.
he doesn't need to put it into system32 as apps scan the local folder for the needed dll's before searching system32.
he doesn't need to put it into system32 as apps scan the local folder for the needed dll's before searching system32.
Iconoclast
New member
I've seen some seriously newbish people, and I take no assumptions on a thread-starter's knowledge of how to use a computer. I say, install Mupen64, because it's easer than copying two DLL files when you can install a whole seperate emulator. Besides, Mupen64 is the emulator that handles the Glide64 graphics plugin the best in the case of some games where there is a difference on the emulator it's used with. To always use it on Project64 makes no sense. Mupen64's got a faster core, anyway.
squall_leonhart
The Great Gunblade Wielder
yes, thats because its a less stable, and less supportitive core.
sacrificing stability and support, for speed is never good.....
considering i've had buggy builds of 1964 crash my machine.... i'd rather use the emulator that is still worked on, and that i know has a wide support group.
sacrificing stability and support, for speed is never good.....
considering i've had buggy builds of 1964 crash my machine.... i'd rather use the emulator that is still worked on, and that i know has a wide support group.
Iconoclast
New member
Mupen64 is more stable than Project64. It fixes the RSP glitches in TWINE 007 and, where Project64, 1964 and Nemu64 fail, Interpreter games like Top Gear Overdrive. I think the description you're giving me is more suitable for 1964, not Mupen64.
Glide64 works pretty well on PJ64, however, PJ64 does not support the framebuffer 'hooks' like Mupen64 does, so certain framebuffer effects do not work. A notable example is the blur effect surrounding the Perfect Menu in Perfect Dark. You just have to bare that in mind with some games that make use of the extended zilmar spec framebuffer 'hooks'.
Iconoclast
New member
Right. Couldn't have explained the frame buffer emulation department as well as Clements, but as I've said at the bottom of the previous page, that and more making Mupen64's core a stronger core than Project64's.
The only exception to that is Donkey Kong 64, which only Project64 emulates at the correct sync. For some reason, Mupen64 has just as much sync issue as 1964, and it seems to be missing a special tweak that Project64 carefully had implemented in it that fixed this issue. Even so, Mupen64 doesn't give you the remaining object clipping issues (caused by gfx plugin or core or combo of both?) or the Signal Processor memory crashes that Project64 does (untested, but all games that have given me SP_DMA crashes on Project64 have never on Mupen64).
Other than that, the only reason why everyone thinks Project64 is better than Mupen64 is because of GS cheats and those cases where Jabo's D3D succeeds Glide64.
But, man, I am sorry to trash this thread with this off-topic stuff. I just have nowhere else to put it. I've nothing against anyone deleting it once squall's read or whatever.
The only exception to that is Donkey Kong 64, which only Project64 emulates at the correct sync. For some reason, Mupen64 has just as much sync issue as 1964, and it seems to be missing a special tweak that Project64 carefully had implemented in it that fixed this issue. Even so, Mupen64 doesn't give you the remaining object clipping issues (caused by gfx plugin or core or combo of both?) or the Signal Processor memory crashes that Project64 does (untested, but all games that have given me SP_DMA crashes on Project64 have never on Mupen64).
Other than that, the only reason why everyone thinks Project64 is better than Mupen64 is because of GS cheats and those cases where Jabo's D3D succeeds Glide64.
But, man, I am sorry to trash this thread with this off-topic stuff. I just have nowhere else to put it. I've nothing against anyone deleting it once squall's read or whatever.
Last edited:
squall_leonhart
The Great Gunblade Wielder
why delete? this is a testement of knowledge for the world? how can people learn if we keep deleteing the written texts? we are all learning and while we are learning we should help others to learn as well.
granted... the first emulator i used was Nemu :| man i didn't try emulation for 4 years after that :|
i've rarely come across a SP DMA crash, and when i have, i've found a way around it
granted... the first emulator i used was Nemu :| man i didn't try emulation for 4 years after that :|
i've rarely come across a SP DMA crash, and when i have, i've found a way around it
Iconoclast
New member
Nemu64 is the slowest core emulator. Not only does it take up more CPU than any other emulator (and yet, it also records Nemu64 videos of your gameplay, along with some serious ass debugging and a few tricks that no other N64 emulator can do), but regardless of your graphics plugin (its default doesn't emulate a single game's graphics perfectly except for Virtual Chess 64 AND it adds to the slowness of the emulation), it will always be slower than the rest.
Nevertheless, if you have a fast system, the emulator ain't obsolete. For several reasons.
squall_leonhart
The Great Gunblade Wielder
lol 
theres never going to be one emulator that can do it all.
oh noes! my musics stopped!
theres never going to be one emulator that can do it all.oh noes! my musics stopped!