Dolphin, the GameCube and Wii emulator - Forums

(05-18-2016, 01:31 AM)brujo5 Wrote: [ -> ]I got these answers in the dolphin bug tracker https://bugs.dolphin-emu.org/issues/9460

It works fine on the X1. But you mali driver just does not support it.

How do I get Super Paper Mario to run past the first Bowser scene?
The issue is not only the bounding box,but also a memory related issue as some have stated in old issues. Edit: Found the related issue.

Memory stride is too small. https://bugs.dolphin-emu.org/issues/9075

What is the exact line to force Bounding Box to be enabled in newer versions,would someone please tell me?

(05-18-2016, 03:30 AM)retroben Wrote: [ -> ]How do I get Super Paper Mario to run past the first Bowser scene?
The issue is not only the bounding box,but also a memory related issue as some have stated in old issues. Edit: Found the related issue.

Memory stride is too small. https://bugs.dolphin-emu.org/issues/9075

What is the exact line to force Bounding Box to be enabled in newer versions,would someone please tell me?

i think

[Video_Hacks]
UseBBox = True

Thanks,I can't even test it yet because of a terrible design flaw. (Wii input mapping gets deleted when disabling wiimotes)
Do you happen to know what the last build is that has input mapping,because that stupid issue F***ING deletes my inputs whenever I disable the wiimotes and I have to remap them AGAIN. (I use Gamecube input for Brawl and it messes with it)

(05-18-2016, 03:57 AM)retroben Wrote: [ -> ]Thanks,I can't even test it yet because of a terrible design flaw. (Wii input mapping gets deleted when disabling wiimotes)
Do you happen to know what the last build is that has input mapping,because that stupid issue F***ING deletes my inputs whenever I disable the wiimotes and I have to remap them AGAIN. (I use Gamecube input for Brawl and it messes with it)

dolphin-master-4.0-8766

(05-18-2016, 03:30 AM)retroben Wrote: [ -> ]How do I get Super Paper Mario to run past the first Bowser scene?
The issue is not only the bounding box,but also a memory related issue as some have stated in old issues. Edit: Found the related issue.

Memory stride is too small. https://bugs.dolphin-emu.org/issues/9075

What is the exact line to force Bounding Box to be enabled in newer versions,would someone please tell me?

If your hardware or drivers does not support bounding box, it will not use it. And I believe the software fallback was removed.

I am on a Shield TV where it supposedly isn't the case.

Dammit! It crashes when attempting to enter the settings because infuriating BS from OS 3.1 Marshmallow!
Now it is actually impossible to map input in a reasonable way,makes you so mad,it makes your blood boil.

Edit: I really think there should be just an app to configure input mapping with great ease so nobody has to rely on certain versions of the emulator itself.
I use a keyboard because I can't use the controller for restricted personal reasons and it sucks that I can't.

Oh. If you're on a STV it should be on because I think Dolphin uses Desktop OGL there? If it's not, yeah. UseBBox = True

The UX/UI for Dolphin Mobile is pretty bad. Somebody would have to implement a lot of the missing things for it to be less dumb. Fortunately that's all Java so it's a lot lower barrier of entry for somebody to jump in and do that. Assuming you can deal with Android's dev environment.

You folks may be interested in the latest merge to master

If your drivers implement and expose es 3.2 this should give you a nice perf boost.

Using an Exynos s7 the latest build seems more stable than previous ones

Jitarm64 still crashes almost instantly, but able to boot using cached interpreter, save, then reload using Jitarm64 on some games, which is more than I had managed before

Right now this is is useful for current gen nexus owners as an IRC tester says the 5x has drivers that correctly expose and implement ES 3.2