mupen 64plus texture flickering after update (January 2017)

[Capt_MorganCreek]

@BuZz Cool, thanks!

Is there a place I can see changelogs of source-updates to emulators, so I know when to update?

[hooperre]

Just curious what resolution you're using. I found the flickering goes away at lower resolutions and am curious if you've found that to be the case as well.

[Capt_MorganCreek]

@hooperre Standard 320x240 resolution. I wouldn't like to go any lower than this, because I'm trying to set the system up as faithful as possible. And it's already pretty low :D

[hooperre]

@Capt_MorganCreek Ah. I only got it at 1280x720.

[BuZz]

@Capt_MorganCreek said in mupen 64plus texture flickering after update (January 2017):

@BuZz Cool, thanks!

Is there a place I can see changelogs of source-updates to emulators, so I know when to update?

You would need to check the github / websites of the various projects we include - eg mupen64plus is managed here - https://github.com/mupen64plus

Some code was moved around recently on that project which has broken the arm/neon build - I have submitted a patch to them - https://github.com/mupen64plus/mupen64plus-core/pull/233

There was another error in your log for the GlideN64 plugin - I will look into that too.

[BuZz]

@BuZz said in mupen 64plus texture flickering after update (January 2017):

https://github.com/mupen64plus/mupen64plus-core/pull/233

You can follow progress on this ticket - https://github.com/RetroPie/RetroPie-Setup/issues/1873

[BuZz]

Please try building from source after updating retropie-setup script

[Capt_MorganCreek]

@BuZz I'm really impressed how fast you submitted these fixes. I installed the latest version from source without a problem, so thank you!

But...

The flickering is still present and it is even more pronounced in the new version. I tested it with Super Mario 64 in Glide and Glide highres to see if there is a difference, but they behave exactly the same.

Is it possible to return to an older binary or maybe tweak some settings?

To reproduce my problem one can simply install a fresh 4.1 (2016_05_11) image, do an update from source or binary and try SM64 (european version). Overclocking seems to have no effect on this issue.

[mediamogul]

@Capt_MorganCreek said in mupen 64plus texture flickering after update (January 2017):

Is it possible to return to an older binary

If it helps pinpoint a workable binary, this texture flickering has been an issue since about one or two weeks before Christmas.

[Capt_MorganCreek]

@mediamogul The 4.1 stock binary is definitely working, but I have no idea what the version is. Playing the games with a fresh install from November 5th works without flickering.

[BuZz]

@Capt_MorganCreek If you think it's a problem with this plugin - https://github.com/gonetz/GLideN64 it might be worth asking them - I will check when I have a chance.

[mediamogul]

@BuZz

I believe it's already a known issue. Looks like it was reported early last December.

[BuZz]

@mediamogul Thanks - looks like there is a config workaround in there - I will test and set it as default.

@Capt_MorganCreek read through the thread and try the option they mention EnableCopyColorToRDRAM = 0

[Capt_MorganCreek]

@BuZz Yeah, just saw the thread. I'll probably try tomorrow and keep you updated.

[mediamogul]

@BuZz

I just tested by setting EnableCopyColorToRDRAM = 0 and the problem persists. I tried a few of the other settings mentioned in the thread as well, but for some reason they're being overwritten at launch.

[BuZz]

I have reverted the GLideN64 plugin to before this problem was introduced. When it is resolved upstream I will switch back to the latest code. You can update retropie-setup and update from source, or wait 20 mins or so until the binaries have been updated.

[Capt_MorganCreek]

Yay, now it works without flickering!

Thanks!

[Capt_MorganCreek]

@BuZz Just installed the new binary of lr-glupen and it seems to suffer from the same flickering problem, although it is much less severe than ithe was in mupen..

[BuZz]

@Capt_MorganCreek similar codebase. The Dev of that will likely fix the issue for both when has some time to look into it. It's a RPI issue.

[rsimmy]

This post is deleted!