Mupen64plus fails to full screen with Rice Video plugin

[mdeguzis]

@beaumanvienna , I would like to try and fix maybe why the Rice Video plugin does not work. This is lower priority, but if we can get that working eventually, it would be a great asset for us, and unique to our project as it does not work in Ubuntu by default. If you disable fullscreen, it will work "windowed" but with whatever resolution. That plugin has so many nice capabilities, it would be awesome to get it working.

Core: Starting R4300 emulator: Dynamic Recompiler
Core: R4300: starting 64-bit dynamic recompiler at: 0x7fcf220a23a0
Core Error: VidExt_ResizeWindow() called in fullscreen mode.
Core Error: VidExt_ResizeWindow() called in fullscreen mode.

Upstream Bug Report filing:

https://code.google.com/p/mupen64plus/issues/detail?id=626&thanks=626&ts=1408585639

[beaumanvienna]

Roger that!

After the latest settings change for mupen64plus, it runs flawless for all my test cases. However, I do acknowledge, that we need to learn more about the particular capabilities of this rice plugin. I also support the idea of handling this with low priority.

Firstly, we could quickly check, if the rice plugin provided by Ecklemann's PPA yields better results (in combination with libmupen provided by our PPA).

Furthermore, we should add the rice plugin to our PPA. This way we ensure to be working on the latest code base. This would also tie in with our overall strategy to separate all backends for RetroRig from possibly problematic changes in upstream versions.

FYI, the second post in https://code.google.com/p/mupen64plus/issues/detail?id=626&thanks=626&ts=1408585639 is NOT from me.

[mdeguzis]

Furthermore, we should add the rice plugin to our PPA. This way we ensure to be working on the latest code base. This would also tie in with our overall strategy to separate all backends for RetroRig from possibly problematic changes in upstream versions.

It is a library (*.so), but of course you can get the source code. And yes, you guessed correctly we need to detach from possible upstream problem versions. That does mean we have to test new versions, but that is not that bad, and quite easy given your excellent build scripts, and I have no problem compiling things from source.

FYI, the second post in https://code.google.com/p/mupen64plus/issues/detail?id=626&thanks=626&ts=1408585639 is NOT from me.

I responded with a link to our Authors.md file. :) imposter! Anyway, rice has amazing accuracy with the graphics and great capabilties. I prefer Glide64 over Glide64mk2, but I do recognize the compatibility seems to be better with the latter. I just like the better looking graphics of Glide64 :)

In due time we can work plugin graphics switches into RetroRig's early, yet crude, settings menu I am making with Advanced Launcher.

[beaumanvienna]

No improvement on this issue with the latest PPA versions: http://slexy.org/view/s2S66rc3vK

[bresheske]

Tried a number of things yesterday. Still the same issues that @beaumanvienna posted here: http://slexy.org/view/s2S66rc3vK. Not sure if this is the appropriate repository.

[mdeguzis]

I'm not sure what can do about this, but let me see if I can rebuild the PPA packages from the latest GitHub source tonight. Maybe that will help. The current target was based on beaumanvienna's Github source, which is behind master.

[mdeguzis]

I should not that this repo doesn't get much attention anymore, due to RetroRig-ES being the bigger focus, and much easier to maintain and make usable. RetroRig is something that was really hacky as well. I still keep this up as long as folks want to use it. I don't have time for this particular project, but I am willing to pick it back up if I receive some help.

[bresheske]

I think this particular issue is not RetroRig specific, after reading around I believe it's affecting a large number of UIs out there wrapping Mupen64plus. For some reason this repository was something that came up in google, thought I would post.

[mdeguzis]

OH ok. Yes, some of my stuff gets posted all over the place. I honestly don't know where it comes from other than Google :)