I've started playing paper mario on my project64 emulator and when I realized the graphic corruption with Jabos graphic plugin I started searching the internet on the subject of which plugin would work the best. It seems to me that the latest rice 6.1.1 is what most people claim works almost flawlessley. The problem I am having is that the game is running pretty choppy and slow compared to Jabo's, but all of my graphic corruption is gone. I'm not sure if i messed a setting up that is causing it to run badly or if it is just suposed to not run as good as Jabo's, I have a pretty powerful computer so i doubt its my side. Any help, or some screenshots of the optimal configuration for a high end PC using rices 6.1.1 would be greatly appreciated. I am using jabos sound and controller plugin also if that helps. Any help is much appreciated, thanks in advance! =)
Issue with Paper Mario
- Thread starter Xavandar
- Start date
- Thread Starter
- #5
Clements said:
Sorry I'm a little confused. Those are options that should be checked on in order to maybe fix the problem? I'm thinking maybe I accidently messed up a setting in the configuration that is causing the problem. I tried to reset the plugin to the default settings it came with when i originally installed it, but even when i deleted the entire thing and reinstalled and put a fresh download of the plugin in, it still had the prefrences I had in last saved in the configuration. If you have any idea of what I might have turned on, or what the default configuration is suposed to be (I tried searching with no luck) it would be awesome.
Also one more noob question, is 1964 saved games, not states, backwards compaitble with Project64's?
Rice's Video saves its settings in the registry. You need to delete this key:
HKEY_CURRENT_USER\Software\RICEVIDEO
Then enable the settings I listed, which are optimal for high-end cards. All other advanced options should not be touched (apart from texture filter options, they don't affect the game compatibility so can be changed).
You may need to rename your save from PAPER MARIO.fla to PAPER MARIO-65EEE53AED7D733C.fla or whatever 1964 calls the save.
HKEY_CURRENT_USER\Software\RICEVIDEO
Then enable the settings I listed, which are optimal for high-end cards. All other advanced options should not be touched (apart from texture filter options, they don't affect the game compatibility so can be changed).
You may need to rename your save from PAPER MARIO.fla to PAPER MARIO-65EEE53AED7D733C.fla or whatever 1964 calls the save.
Last edited:
- Thread Starter
- #7
Thanks a ton! Very fast and thourough responses that helped me signifgantly. I'm gona try these settings as soon as i get back to my home computer. I'll deffinitly be back here in the future if I have more problems. Thanks alot for all the help, hopefully it ends up working.
- Thread Starter
- #8
Well I got home and deleted the registry file and it fixed alot of the problems, but i was still getting some pretty bad lag. But...I figured out what was causing it and fixed all the problems by messing around with some settings. The lag was being caused because the Limit FPS option was enabled and I didn't see it before because Project64 hides that option unless you enable advanced options. After i fixed that i was getting flashes of the background blocking my entire screen constantly in some areas. I enabled frame update at the first CI change under current game options and it fixed it.
From what I read i don't believe there is a solution, but does anyone know of a fix for the menu graphical corrution. Thanks for all the help and hopefully if anyone else is having a similar problem this will resolve it for them also.
From what I read i don't believe there is a solution, but does anyone know of a fix for the menu graphical corrution. Thanks for all the help and hopefully if anyone else is having a similar problem this will resolve it for them also.
I've been running project 64 with rice video on this game and the performance is very good, with not much trouble - except one thing, that I'm hoping someone might know a fix for...
in areas where it is darker (like the castle in the begining when mario and peach are about to see bowser for the first time or toad town in the sewers) the characters are just black - no image it just looks like cutouts. the backgrounds are fine, just the characters (mario etc) are missing.
does anyone know of a workaround? I know that this config has not always had this issue, as I've played it oK before - but now I'm seeing it on 2 different pcs.
thanks for any guidance!
in areas where it is darker (like the castle in the begining when mario and peach are about to see bowser for the first time or toad town in the sewers) the characters are just black - no image it just looks like cutouts. the backgrounds are fine, just the characters (mario etc) are missing.
does anyone know of a workaround? I know that this config has not always had this issue, as I've played it oK before - but now I'm seeing it on 2 different pcs.
thanks for any guidance!
ok - perhaps I have not been clear -
if I use Jabo's video plugin, the area's are still dark, but you can see the character detail - but they are darker. Mario looks the same, just not as bright.
With rice (which I would like to use all the time due to performance being better) in the dark areas - the characters look all black - no detail visible at all.
I have never played it on the actual N64 so I can't say if they should appear black in any low light situation (like the pharoh's tomb at the end of chapter 2) but I think it is a plugin issue...
again thanks for the input!
if I use Jabo's video plugin, the area's are still dark, but you can see the character detail - but they are darker. Mario looks the same, just not as bright.
With rice (which I would like to use all the time due to performance being better) in the dark areas - the characters look all black - no detail visible at all.
I have never played it on the actual N64 so I can't say if they should appear black in any low light situation (like the pharoh's tomb at the end of chapter 2) but I think it is a plugin issue...
again thanks for the input!