Missing default plugin?

[Link318]

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. "

[Iconoclast]

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.

[Link318]

i'll try getting 1.6 but i have played before, then i stopped and it didnt work anymore..

[Iconoclast]

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.

[Smiff]

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.

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]

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.

[squall_leonhart]

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.

[Iconoclast]

how hard is it to copy glid3x.dll into the same folder as the emulator.

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]

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.

[Iconoclast]

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.