NEW Paper Mario problem

[crispi]

I wanted to play Paper Mario on PJ64. At first it wasn't working for various reasons, so I plunged into this forum and followed their instructions step-by-step. I'm running Glide64 v0.7 w/ eVoodoo on a GeForce2, with Hybrid buffer swapping selected. The game worked... with numerous graphical artifacts, i.e. sprites dissapearing altogether in dark areas and glitchy menus, but it worked.
I played for a bit, decided to call it a night, and turned the game off.
The next morning, I ran the game, and as soon as it finished loading the ROM, it quit. Tried again. It quit again.
I reinstalled PJ64 and eVoodoo, then started the game up. Once again, it worked the first time, but after I save and quit, any further attempts to run the game simply caused PJ64 to quit.
I discovered that if I deleted the .fla save file, then it would run. OK, so I'm just going to have to use save states... nope! As soon as I started taking advantage of this, the emulator started quitting whether or not there was a save file, as soon as it finished loading the ROM.

There's no error message or anything... it's just quitting without warning.

Any thoughts?

 

[ScottJC]

I think thats an issue with the emulator not the rom its loaded, i've seen it happen to me with Star fox 64 with glide64 (and another wrapper). I Don't know if its a wrapper issue or if its a glide64 issue, however, the combination of wrapper(yes evoodoo is a wrapper) and glide64 in 1964 work much better than with project64 i've found.

Btw, this other wrapper which isn't evoodoo is included in the latest glide64 release, I reckon its much better than evoodoo is.

http://glide64.emuxhaven.net/

 

[JinXD]

I ran the game, and as soon as it finished loading the ROM, it quit. Tried again. It quit again.
I reinstalled PJ64 and eVoodoo, then started the game up. Once again, it worked the first time, but after I save and quit, any further attempts to run the game simply caused PJ64 to quit.

I've had the same problem with PJ64 and funnily enough Paper Mario! I originally used 1964 with glide64 0.7 SP7, except it crashes on menus with me (the start menu, not ingame menu) or when saving to memcard. So I switched to PJ64 which works fine apart from that odd crash that occasionally occurs!!

Does anyone know how to solve the problem with Paper Mario crashing in 1964 when either in the start menu or trying to save a game to memory card? It seems like an emulator problem rather than a plugin one.....

http://www.emutalk.net/showthread.php?t=19673&highlight=paper+mario+crash

 

[Doomulation]

Hacktarux's wrapper, which is bundled with glide64 is indeed better than evoodoo.

 

[crispi]

Hmm... the Hacktarux wrapper just seems to be a new glide3x.dll... is there anything in particular I have to do to install it?
I tried replacing eVoodoo's glide3x with that one, but it didn't change a thing.

I also tried 1964, and it worked at about the same graphical level, but at the Dry Dry Ruins I ran into the same problem that JinXD has... it crashes when I try to save to the memory card.

 

[ScottJC]

nope, just shove it in the emulator dir thats all.

As for the save issue, why not try save states?

 

[crispi]

I *could* just use save states... but even that seems to be a little glitchy. And besides, it's compounded with countless graphical glitches. Mario was invisible for the entire Dry Dry Ruins dunegon.

 

[JinXD]

I just use save states now which work fine, the point is it's still a bug with 1964.

As for the problems with gfx in Dry Dry ruins, I didn't have any. crispi are you running the latest version of glide64 (0.7 SP7) with Hacs wrapper?

 

[crispi]

I'm using the same version you described. Switching to Hac's wrapper fixed a couple minor problems, but it's still real ugly, and the sprites still dissapear. The darkness in the Forever Woods is so thick that it makes the dungeon impossible.

 

[Powerlord]

Does anyone know how to solve the problem with Paper Mario crashing in 1964 when either in the start menu or trying to save a game to memory card? It seems like an emulator problem rather than a plugin one.....

http://www.emutalk.net/showthread.php?t=19673&highlight=paper+mario+crash

My suggestion would be not to use save states... although it would be nice to know if there's a fix in the works for newer versions of 1964.

Ha, I just noticed that I'm the person who started the thread you linked to.

 

[ScottJC]

Crispi update to the latest version of Glide64, hack's wrapper was made after glide64 0.7, plus glide64 0.7 SP7 is much much newer.

Save states will work but make sure you don't quick save that way, you feck up one save state you've lost your entire game, hit the same button and give it meaningful names.

Mempaks are handled by the input plugin so try jabos direct input to see what it does.

 

[crispi]

I already am using glide64 0.7 SP7. Or at least, that's what the choice says on my plugin-choosing screen (Glide64 0.7 ME SP7, even... is that bad?). Graphical glitches persist in 1964, game-quitting glitches persist in PJ64.

 

[JinXD]

The ME is meant to be there (stands for Miracle Edition).

As for Forever Woods I had the same problem where it goes really dark or flickers. Seems to happen when you go to switch party members, go into the menu or sometimes just randomly! All I did to solve was switch from fullscreen > window > fullscreen and it's fine after that.

Save states will work but make sure you don't quick save that way, you feck up one save state you've lost your entire game, hit the same button and give it meaningful names.

Do you mean pressing CTRL + F5 instead of just F5?

 

[Powerlord]

My suggestion would be not to use save states... although it would be nice to know if there's a fix in the works for newer versions of 1964.

Ha, I just noticed that I'm the person who started the thread you linked to.

Oops, sorry, I meant to tell you not to use Save States or not to use the Save Blocks. Using one or the other should solve this... in theory at any rate.