project 64 issues

[Felixflywheel]

Same issues

I have the same problem with Majora's mask deleting my game! I go through the trouble of manually saving my files and making copies and putting them in diff. folders so they can be safe, and apparently, that doesn't even help! Somehow, the Emulator makes the file go back in time to a way previous save. I dunno why it does this, but it sure pisses me off! Why oh why does it do this!?

I check the date my save was modified... So pretty much, the save says "Modified at 2PM today", but it loads a game from 2-3 days ago. Why!?

I'll never know.

-Felix, an angry kid.

 

[Felixflywheel]

No offense, but this sounds more like a PEBKAC error than a problem with PJ64. Put simply: PJ64 does not store its native saves in ZIP files. If the saves you have are from PJ64 and they are in ZIP files, they are save states, and were created with PJ64's (inherently error prone) save state feature - not by saving the game as you would on the original console.

Don't even touch F5, F7, Ctrl+S, Ctrl+L, System->Save, System->Save As..., System->Restore or System->Load. Pretend you're playing on the original console and have to save using the in-game save feature. This will not produce a ZIP file containing a save state, but will create a native save. If you still do not have a native save in your save folder after doing the above, chances are there is a problem with the permissions on your save folder and PJ64 is unable to write to it.

Pfft! The reason why I even use emulators is to use save states! I like to be able to save ANYTIME, and not have to worry if meh power is gonna go out any minute because of the stupid weather. >_>;

 

[Toasty]

I have the same problem with Majora's mask deleting my game! I go through the trouble of manually saving my files and making copies and putting them in diff. folders so they can be safe, and apparently, that doesn't even help! Somehow, the Emulator makes the file go back in time to a way previous save. I dunno why it does this, but it sure pisses me off! Why oh why does it do this!?

I check the date my save was modified... So pretty much, the save says "Modified at 2PM today", but it loads a game from 2-3 days ago. Why!?

I'll never know.

-Felix, an angry kid.

What do you mean by "manually saving"? Majora's Mask saves automatically when you travel back through time. (Aside from Owl Statues, which are only temporary saves, traveling back through time is the only native way to save on MM, in fact.)

 

[X-Fi6]

Pfft! The reason why I even use emulators is to use save states! I like to be able to save ANYTIME, and not have to worry if meh power is gonna go out any minute because of the stupid weather. >_>;

Though I do agree that save states shouldn't be so buggy, you have to remember that PJ64, just like all other N64 emulators, are way too damn high-level (which is why we even use microcodes) and that being able to store enough low-level information into a save state to the point where the emulator can reproduce the state exactly is damn hard.

 

[squall_leonhart]

Savestates are a currently inmemorysnapshot.

that includes dirty memory.

 

[Ultimatium]

So, i just wanted to give an update on this. It seems like the savefile for majora's mask had become so buggy, that i had to get rid of it and start over again. I have been playing all the way up to the stone tower temple without any problems, and the savefile suddenly disappears. I have not been touching the new savefile, in fact i have not even been near the savefiles folder. It's odd, because this has happened two times, both times at the entrance to the stone tower temple. Also, another bug i have noticed, is when you take a picture of one of the pirates from the pirate's fortress with the pictobox. It sometimes causes the screen to freeze for a moment, only to give you a picture that is empty. I really like the whole concept of being able to play your favorite nintendo 64 games on your computer, but i just can't risk having my savefiles disappear like that.

 

[Ultimatium]

double post

 

[squall_leonhart]

new forum policy.

if you don't read the frickin help file included with the emulator, you immediately go on a support blacklist.

 

[squall_leonhart]

Though I do agree that save states shouldn't be so buggy, you have to remember that PJ64, just like all other N64 emulators, are way too damn high-level (which is why we even use microcodes) and that being able to store enough low-level information into a save state to the point where the emulator can reproduce the state exactly is damn hard.

mudlord says (12:24 AM):
*Please say that X-Fi6 is a brainless shit
mudlord says (12:25 AM):
*Microcodes are what the RDP uses to process dlists, DUH

 

[Ultimatium]

Well, i have already read it, but i didn't find a solution to any of the problems.

 

[Agozer]

Project64 does not delete savefiles. Make sure that your save directory isn't read-only.

Pictobox problems are most likely due to your chosen graphics plugin not emulating framebuffer effects correctly

 

[Ultimatium]

Can you give me a correct answer on which of my settings are wrong? i have all the advanced settings off+ hide anvanced setting is marked. i run @ 1680x1050 32bit 59hz full screen
tripple buffer v-sync 16X and 8X super 2x and texture filter enabled. BTW i took the chance and deleted the two junk files in the games folder, and it has not affected PJ64. The folder that my savefiles in is a folder that PJ64 has created itself and it is not read-only marked. Yet PJ64 fails to load my games now and then.

 

[Agozer]

I haven't used Rice's video plugin in years, so I really wouldn't know what settings are the right ones.

 

[Ultimatium]

As i see it i am running the native resolution on my screen, as well as the graphics maxed, i don't see anything wrong here, yet the pictobox screws up, as well as the menu in TLOZ:OOT.

 

[Agozer]

yet the pictobox screws up, as well as the menu in TLOZ:OOT.

Which is all the more indication that framebuffer effects emulation is not being done correctly. Fiddle with Rice's Framebufer emulation options and your bound to find the setting that works.

The current settings aren't wrong per se, Rice just offers multiple levels of emulation, and it just so happens that default settings are not the best.


Or use another plugin, like say, Glide64.

 

[Ultimatium]

Yes, that's what i did,

i downloaded the glide64 plugin, copied the files in the pluginfolder to the plugin folder in PJ64, now it says "could not launch because glide64.dll could not be found". It runs fine now though, except a few graphics glitches like the ones i mentioned, as well as saved games disappear as well as the glide64 plugin wont work.

 

[squall_leonhart]

READ
The
*******
Manual.

 

[Toasty]

and so i did, i downloaded the glide64 plugin, copied the files in the pluginfolder to the plugin folder in PJ64, now it says "could not launch because glide64.dll could not be found"

From Glide64's help file:

To install Glide64:

1. Open archive and copy everything from the 'Plugin' folder into the folder where all your N64 plugins are stored (this is usually the 'Plugin' folder in your emulator's folder, e.g. Project64\Plugin).
2. If you don’t have a Voodoo card, make sure you copy the glide3x.dll file from the 'Wrapper' folder into your emulator's folder.

 

[X-Fi6]

mudlord says (12:24 AM):
*Please say that X-Fi6 is a brainless shit
mudlord says (12:25 AM):
*Microcodes are what the RDP uses to process dlists, DUH

Please say X-Fi6 was misinformed instead of being an antisocial shit

Sorry I haven't read up on your profession

 

[squall_leonhart]

you've been here more than long enough to know what microcodes and ucodes are.