Manual / Guides for v1.6

Here is the reference manual for users of PJ64, based closely off Project64.chm included with the emulator but here we can keep working on it to make it better!

The cheat system has been supported on its own website, we aim to merge this soon

  • Requirements

    Minimum and recommended systems for running Project64.

  • Installation

    Help with installing PJ64 for the first time, adding plugins, games, through to removing PJ64 from your system or moving to another PC.

  • Using Project64

    Quick guide to basic tasks in PJ64

  • Configuration: Project64 application

    Guide to setting up and tweaking the Project64 main program, including all the Settings tabs.

  • Configuration: Jabo Direct3D8

    Guide to setting up and tweaking the Project64 video plugin.

  • Configuration: Jabo DirectInput

    Guide to setting up the Project64 input plugin.

  • Configuration: Jabo DirectSound

    Setting up the default audio plugin.

  • Reference

    in-depth information that doesn't fit anywhere else! verifying ROMs, GUI translation, how PJ uses support files, etc.

  • Troubleshooting

    Having stability or graphics, sound or speed problems? Here's how to go about solving almost any problem yourself.

  • Error Messages

    Help with common error messages, what they mean, how to make them go away!

    • "The default or selected video plugin is missing or invalid..."

    • "Error 1606. Could not access network location..." (installer)

    • "Direct3D failed to initialize your HAL device / make sure you have... (video plugin)"

    • "Access Violation" (video plugin)

    • "Bad ROM? Use GoodN64 & check for updated RDB" (application)

    • "failed to load word 0 / 2" (core)

    • "AutoDetect error" (video plugin)

    • "DirectInput: Failed to initialise Joystick" (input plugin)

    • "...dinput8.dll could not be found"

    • "Zip error: File contains no N64 image" (application)

    • "Unhandled OpCode" (core)


      1. Usually indicates a Bad ROM - read how to {ln:verify your ROMs}.
      2. If your ROMs are [!], this error may indicate incorrect ROM Settings. Check {ln:download section} for updated RDB.
      3. Cheat codes can cause core errors. Disable all cheat codes and reset the game (default shortcut: F1). Load from the native save (through the game's menus). Do not load from a state save (F7 etc.), because states store memory changes. Usually loading from the native save is OK. In some cases cheat codes can damage the native save aswell so that the game crashes; it may even be necessary to start the game again, either by using a different "slot" or by deleting the native date in your Project64 \Save subfolder. (try all other suggestions here first!).
      4. If none of the above apply, try restarting the emulator and load from the native save - through the game's menus (do not load any PJ64 state save (F7 etc.) because state saves can store memory errors). This point will test for other random memory/core errors. If you find this works, overwrite your bad state save with a new clean state save.

    • "Failed to open..." (application, when starting games)

    • "in a permanent loop that cannot be exited" (core)

    • "Executing from non mapped space" (core)

    • "File loaded does not appear to be a valid Nintendo64 ROM / Verify your ROMS with GoodN64" (app.)

    • "Failed to allocate memory" (application)

    • Q: I get repeating error msgs - how do I get out of this?

    • Q: Why is there a huge error log in my Project64 folder? What should I do?

n64 usb