Paper Mario video issues.

[soberflashlight]

1. Alot of times the screen will flicker and show the background, usually when multiple objects are moving on screen.

2. With certain bars that are supposed to fill (Bombettes Body Slam attack, phonograph in Bow's castle).

Any help at all will be appreciated. Thanks in advance.

 

[Haisook]

I used to have similar issues with Yoshi's Story, with Graphic plugin Jabo's 1.6. I changed it to 1.5.2 and the issues disappeared. After installing the last ROM update from here, it's working great with either any of the two plugins.

So if you haven't intalled the latest ROM update, get it. If you did or if you don't want to, try to choose the other Graphic plugin.

 

[Agozer]

The flickering is a known issue with Jabo's Direct3D8 plugin. You will have to use another graphics plugin, like Rice's video plugin or Glide64.

 

[Haisook]

Hey Agozer,

I've downloaded Glide64, and placed the Glide64.dll file in the Plugin folder of Project64.
When I start Project64, click Settings (to choose the new plugin), I hear the Error sound of Windows, and the program freezes. I have to shut it down with the Task Manager. When I delete the dll file, I can go into Settings with no problems.

How can I install Glide64 correctly if that case is not working?

Thanks.

 

[Agozer]

That could be Glide failing because you don't have the Glide wrapper in the emulator folder.

Anyway, make sure that you have hactarux's Glide wrapper (glide3x.dll) in the emulator folder. Hacktarux wrapper with hardware frame buffer emulation. Files and feedback - Emu X Haven

 

[Haisook]

Thanks Agozer!

I've got it to work, but it's really slow, and many games failed to be emulated.
I have tried the default settings, and modified them a bit, but it's still slow overall.

I think I'll stick to Jabo's for now.

 

[Iconoclast]

Here's a suggestion: Use Rice's Daedalus 5.2.0. If it's one game this plugin doesn't screw up so much, it's Paper Mario. If you don't know where to get the plugin, don't worry, just install 1964 and use that emulator.

Now, I don't know anything about navigation within this game, so I haven't tested very many things. Therefore, if you experience any issues with Rice's Daedalus, let me know, and I can find another plugin.

 

[soberflashlight]

I downloaded glide64 and glide3x.dll but when i open the settings menu it says it can't open glide64 because it can't find glide3x.dll. How do i resolve this?

 

[soberflashlight]

Now it let's me select "glide64 v0.7 ME SP8" but it says "your video card does not support GL_ARB_texture_mirrored_repeat extention" and "Error: uCode crc not found in INI, using currently selected uCode 21f91834" and it freezes. What am I supposed to do?

 

[Iconoclast]

Try the 1964 emulator instead.

 

[mudlord]

Hmm...GL_ARB_texture_mirrored_repeat is a extremely important OpenGL texturing feature used by the wrapper...Changing emulators will make zero difference as that error is purely related to the Glide3x wrapper and your video card. Which makes me wonder that brand and model of video card you have in the 1st place, as that error only occurs on low-spec video hardware.

 

[Thrillho]

hi, ive had similar issues as well with paper mario. (flickering/background showing up with pj64). Ive tried using rice's 6.1.1 beta 10 and the background pops up much more frequently.

i just tried 1964 with daedulus 5.2.0 and right in the intro (when mario + peach are running back and forth before bowser pops in), everything becomes choppy/flickers, characters turn black and it just slowly crashes.

Also tried the newest Glide64 wonder++ on both pj64 and 1964, i get a black screen with the actual game flickering on every few sec.

Atm im using 1964 with rice 6.1.1 beta 10, but so far, during some scenes(mario talking to bowser in the intro) the characters will turn into grey blocks.

 

[Dykstra Fedora]

I also am having problems with Paper Mario. Everything looks fine, but sometimes the error box pops up and says "While processing graphics an exception occurred, you may need to restart your emulator." I hit Enter on the box a couple times, and I can move around for another 5 seconds, and sometimes it stops.

But then I have a massive error that happens at a specific moment in the game: after you first go to Star Haven, and right after the Princess first meets the little star Twink, and the screen goes white after the shot of her on the balcony. I get a "Cache failed to translate at 400" and then if I hit enter on this I get another number, and I pressed down on Enter for about 10 minutes and it kept generating "Cache failed to translate at 3241234123" etc etc.

I searched for the error and found someone who fixed it with "Options>Rom Settings>interpreter>protect memory>8mb (don't know if this has anything to do w/ it)>advanced block linking (same)" But I can't find that setting.

 

[Dykstra Fedora]

Okay, I was using the E version. The U version gets past that scene with Twink, but I'm experiencing INSANE numbers of Access Violation notices with either version.

I played the first hour of the game with ZERO errors, so I am baffled at why there are suddenly all these problems.

 

[Agozer]

What are your computer specs? Are you using a good rom?

 

[nothing_funny]

if i'm not wrong, these issues were discussed many times :getlost: ......
go use the search engine and type this small words"paper mario"

 

[Dykstra Fedora]

I did search and found about 8 different people asking questions about these 2 problems. Mostly they got nowhere. But, I've gotten everything to work and I'll lay it out here so hopefully from now on a search will find these answers instead of all the scattered stuff.

(using Project 64 v1.6)

Basically there are two problems here:
1. the crash after Twink's debut
2. the incessant "Access Violation" messages during this part of the game.
Answers:
1. the crash only happens to me during the E version. Use the U version.
If you were using the E version you don't have to start a whole new game; use the save file from when you are given "Save and Continue" before the Twink section and it will be compatible, but the quicksaves won't work.
2. simply continue through the part, endure the frustration, and the messages stop happening right about as you leave the town for Koopa Fortress.

Sometimes when I boot the game up I get 4-5 Access Violation messages. Press on, and they'll stop happening.

As for the Original Poster's problems, I never really found them to interfere with gameplay enough to try fixing them.

I apologize if I have bothered anyone and hopefully this helps us all.