Emulator

Which CPU/GPU do you have? This feature requires D3D11 or OGL 4.3 :/

Do you get the same result on both D3D and OGL?

I have an intel i7 2.2 gz 8 core processor, and an intel 3000 graphics chip windows 7 x 64. I did get the same result on both d3d and ogl. this issue is similar to 7965, only this happens on the most recent version of dolphin.

HD3000, so second generation i7 CPU. Wikipedia tells me that at least the third generation is required for d3d11 support...

Really, because I can use 3d11, it works for all of my other games (xenoblade chronicles, etc.

I might be wrong about the graphics chip (dolphin only says HD graphics family), I dont have my laptop with me right now so I cant check.

Our "D3D11" backend mostly requires a .10 feature level GPU. bbox is one of the .11 feature level only features, just like zcomploc.

so I cant fix it because I dont have a third generation processor?

I forgot to mention it works on the stable release 4.0.2 with 3d11

You can disable the vertex loader jit as the old vertex loader has software bbox support built-in.

how do you do that?

The only way is to modify the codebase to drop to the older slower codepath.
The alternative is to upgrade to a GPU that can handle OpenGL 4.3+

Thanks for your help guys, I guess Ill just use an older version of dolphin until I can afford a new laptop. Maybe Ill try to modify the codebase later.

Issue 8276 has been merged into this issue.

Issue 8276 was mine. Are we aware of an older version of dolphin that works with this? OP said they would use an older version but didn't say which one.

Yeah, the stable version works great, but I haven't found any of the newer version that work yet.

Good to know, thanks for responding

Also, I cant seem to fix the problem with the newest version, its going to take a better programmer than me, probably a developer.

Unfortunately the latest stable version doesn't work for me either. When i try to launch it i get an error "Failed to losd d3dx11_42.dll, update your Dx11 runtime, please". I did update that but no luck. Direct3d9 and OpenGL are far too slow.

I have the same issue as Jeremy with the boat crossing the screen then it fading to white. I just purchased a controller specifically for playing this game, so I'm incredibly disappointed. Are there any updates or anything else I can try on my end?

Get a computer that can run GameCube and Wii games at playable speeds? At some point, it's just not possible for old computers to run some games.

You must have a low end GPU like me. As of now i don't have a way to play it. Stable doesn't work for be either. We either have to get a new GPU (or new computer in my case) oor wait and see if these developers can work magic.

If stable doesn't work for you, then there's nothing we can do. It uses no fancy GPU features like latest master to speed it up. Your computer is having problems with D3D11 even and that has nothing to do with Dolphin.

I just find it odd I can run every other game I've tried with no issues. Mario Kart Double Dash, Mario Kart Wii, Mario Strikers, Super Smash Bros Melee, Mario Party 4 and 5....all with the D3D11 option in Graphic Settings and I get a consistent 60fps with all of them. Paper Mario is the only one I have trouble with right now. 3D311 didn't work on Stable but it works on Development.

I apologize for my ignorance, but I don't know what most of that means. My computer is two years old, how recent a computer should be able to run this?

Jay, the GPU is your graphics card. If your computer is 2 years old I am assuming it is a laptop with a poor processor and integrated graphics and is probably only good for email, internet, and school work. My laptop is 5 years old with a decent processor and a not-so-great GPU where I can run all games but Paper Mario so far.

With some digging, I've got a Intel HD Graphics 4000.

That's better than mine technically

I suppose I'm out of luck.

I just tried something for the hell of it. I loaded Paper Mario on the Stable version using D3D9. It was painfully slow, but I did get past the part we are having trouble with and was able to save the game. I then restarted the game up with the latest dev build and I am able to play quite normally. The graphics messed up after the first battle though. A bunch of enemies try to jump on you and you escape. All I saw were black shadows, but they are supposed to look like the enemies at 2:20 in this video https://www.youtube.com/watch?v=COawRaqc4lM

I'll probably encounter more issues, but I'll play it this way until then.

You're literally playing the game without bounding box support, something it uses for a ton of special effects. Yes, newer dev builds are much faster, but when you're lacking a key feature. (which, you could enable software bounding box if you modified the code, but that would slow down the emulator for you.)

I also was able to work around it Jeremy, thanks for the suggestion! I'll continue playing this way then using the workaround when/if I hit other errors. Painfully slow was a very apt way to describe it. Thanks again.

JMC is there a list of games that use bounding box that we can look at to know which games we likely won't be able to play? I think it's probably a given i will encounter more issues with Paper Mario so i don't really want to invest the time to play it and get stuck.

I've been playing it for 20 minutes or so and anything that uses stronger animation like all the paper peeling effects of which this game has many the game just stops. Music keeps playing but the animation never takes place. It works but very slowly with stable. So basically play the majority of the game in stable. Doesn't seem like this is going to work.

Try going to a build before the hardware bounding box was implemented. That way the game will be playable, and it's probably still a lot faster than 4.0.

I tried it out on stable 3.5 and i was able to get through the boat part and i actually saw the enemies attacking me in the prologue but I'm only getting about 35 to 40 fps. I'll probably just have to call it quits on Paper Mario.

The version that broke the game was 5143, any version before 5143 works like it should (bbox working perfectly), the latest version that worked before 5143 was 5124. 5143 was when they implemented the vertexloader: rewrite JIT.

I'm going to try that version now. My biggest issue is the frame rate right now since 3.5 didn't error out

It's known that the new vertex loader JIT doesn't support software bounding box. Obviously, any version before 4.0-5143 will work for you (and will most likely also be slower).

Please only comment if you actually have new information beyond that. If you would like to discuss older versions/unsupported hardware, please use the forum.

Guitar, you are absolutely correct. I just tested out Paper Mario on 5124 and the boat scene and prologue characters I couldn't see before were no issue and I am getting a constant 53-60fps which is totally playable. Thank you for finding this, and I hope the devs can somehow implement this as an option in future builds.

Til, you mention it would likely be slower but i get closer to 60fps than i did on any other version. There's something about 5124 that's makes it faster in my case. Not sure what but it helps folks like me :)

5124 has had some slow points for me as well but generally runs well and the animations work. Thanks guys!

Issue 8322 has been merged into this issue.

I'd rather disable vertex loader JIT and get an accurate emulation of the game. Now we have the pre-bbox glitches that caused more than just graphical issues.

The accurate emulation is to use the hardware bbox code. The old code wasn't accurate at all.

The old code generated visibly correct output.

I'll be maintaining a fork with the old implementation for any users with crap hardware like mine.

Well, a fork might actually be better for me in the mean time, but I'm quite unfamiliar with how forks work so, where should I go once the fork is ready?

AHeinerm: If you're going to need some help, feel free to ask me on #dolphin-dev. I'm always looking for other ways to implement such features. I'm just against the way of the old "software" implemention. But I'm looking forwards to a technical discussion :D