WWF-No Mercy Save Problem

[GamerRelic]

Every time I load up No Mercy, it keeps saying failed to load mempak. But before my PC decided it wanted to not play my games , I never had this problem I know i could just use save states but , what to do about the mempak problem :confused:

[GamerRelic]

Save States dont work .... :(

[rswedlow]

Six points


Check if you are using a controller plug-in not supplied with Project64. When you go through Options/Settings... the field for input plug-in should read "Jabo's DirectInput7 1.6". If this is not the case the method for emulating memory pak is configured to be something else.
Verify file "$Project64\Save\mempak.mpk" exists. The file should be 32 KB in size. If the file doesn't exist after first point of this list check if your save directory is "$AppPath\Save" through Options/Settings... and the Directories tab.
If you can find this file right-click it, and check through "Properties". If an option for attribute "Read Only" is marked on disable it.
If you use Windows NT/XP or later, your user account might not have priviliges to access the mempak file.
Restart your machine.
Make sure no processes still run that may be accessing the memory pak file. If this file is being read by another process even after rebooting, end it.

[GamerRelic]

Six points


Check if you are using a controller plug-in not supplied with Project64. When you go through Options/Settings... the field for input plug-in should read "Jabo's DirectInput7 1.6". If this is not the case the method for emulating memory pak is configured to be something else.
Verify file "$Project64\Save\mempak.mpk" exists. The file should be 32 KB in size. If the file doesn't exist after first point of this list check if your save directory is "$AppPath\Save" through Options/Settings... and the Directories tab.
If you can find this file right-click it, and check through "Properties". If an option for attribute "Read Only" is marked on disable it.
If you use Windows NT/XP or later, your user account might not have priviliges to access the mempak file.
Restart your machine.
Make sure no processes still run that may be accessing the memory pak file. If this file is being read by another process even after rebooting, end it.


I looked in the exact place where app data needs to be and its not there :eek::eek::eek::eek:

[rswedlow]

The folder is probably named something like "Project64\Save".
Since based on installation the naming of where the emulator is installed can change, when setting up folders Project64 refers to it as a variable $AppPath.

To make sure (to see this in effect as well) go through Options/Settings..., see the "Directories" tab.
This tab is hidden from view if "Hide Advanced Settings" is enabled from the "Options" tab. Unmark this setting, save changes, and re-enter configuration.

If this tab can be seen now look in it for "N64 Auto saves". Whatever path this is set to is where MEMPAK.MPK should be.

Memory pak is written if, through Options/Configure Controller Plugin..., the drop-down box next to "Controller is plugged in" setting is set to "Memory Pak". Otherwise it's just unemulated.

[GamerRelic]

Well I fixed the problemo by creating a directory in my ROM directory thanks for making me realize the problem

[rswedlow]

Um also if you use Jabo's DirectInput7 1.6 also check the Project64 path for a folder named "Mempaks". This should automatically be created by the plug-in if set to write.