search

libretro / mupen64plus-libretro-nx

Improved mupen64plus libretro core reimplementation
GNU General Public License v2.0
227 stars 113 forks source link

Mario Tennis broken on Android #101

Closed drinfernoo closed 3 years ago

drinfernoo commented 4 years ago

I'm not really sure what I can give as the best details for this issu, but I'm running into lots of issues with Mario Tennis on RetroArch 1.7.8 for Android.

Neither the GLES2 or GLES3 version of this core seems to handle it properly, and I'm thinking it may be a framebuffer issue, but it doesn't matter if I have "Framebuffer Emulation" turned on or off.

I have missing textures, black textures, lag, audio glitches, cinematics missing, etc... Pretty much everything is broken. This game used to play fine in "pre-Next" versions of the Mupen64 core, but it really isn't on these :(

Any ideas?

m4xw commented 4 years ago

@drinfernoo Try a lower Max texture cache size (4000 or lower) Also it's irrelevant if the old core worked. Next is so far ahead, u can consider it using "different" plugins by now.

5schatten commented 4 years ago

Android is not really precise if it comes to the box hardware. So which TV box or whatever do you use?

drinfernoo commented 4 years ago

@5schatten My apologies, I'm on an Nvidia Shield 2017 running the latest update, 8.0 IIRC.

5schatten commented 4 years ago

Okay so a Tegra X1 SoC - then it's probably not limited to Mali GPUs

m4xw commented 4 years ago

Works fine on Switch, but we use GL (Also on lakka-switch with nvidia blobs). This seems to be limited to GLES variants.

drinfernoo commented 4 years ago

Unfortunately, neither turning off the texture cache, shader cache, or modifying the texture cache size (tried 4000 and 1500) remedied this issue :(

m4xw commented 4 years ago

Gave you a test build on discord.

mudlord commented 4 years ago

To some degree I found it broken on Win32 as well.

Missing things like heat haze, some shadows broken, etc.

Would have to debug things under gDebugger or something.

m4xw commented 4 years ago

You know if that happens upstream too?

mudlord commented 4 years ago

Thats one thing I have to test. I would use upstream more often if it didnt have a audio implementation from Satan's anus.

m4xw commented 3 years ago

I think this should be fine now. reopen if issue persists