Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RGUI Freezes in RetroPie 3 beta 3 #863

Closed
biscuits99 opened this issue Jun 12, 2015 · 16 comments
Closed

RGUI Freezes in RetroPie 3 beta 3 #863

biscuits99 opened this issue Jun 12, 2015 · 16 comments

Comments

@biscuits99
Copy link

When in-game, if you bring up RGUI using the hotkey combo of select and X, it starts, but freezes on title screen. Was fine on RetroPie 3 beta 2, seems broken in beta 3.
I am using an iBuffallo USB joypad, but seems to happen on various others.

@joolswills
Copy link
Member

please can you try building a new retroarch from source in case we built it during a problem. If it still has an issue, we may need to trace back as to when the problem started and feed it back to retroarch

@HerbFargus
Copy link
Member

I tested it, and I don't think it is freezing- it just doesn't register joypad inputs. I opened the rgui with the hotkey combination (with my joypad) and couldn't navigate with my joypad but as soon as I pressed enter on my keyboard the rgui menu was working fine.

Just for reference the RGUI welcome screen controls say:
Scroll (Up): Auto: Hat #4294905855 ? (Key:...
Scroll (Down): Auto: 1 (btn) (Key: down)
Accept/OK: Auto: 1 (btn) (Key: enter)
etc etc.

Update: Actually on further testing.... it does freeze. will recompile and see if that solves it.

@HerbFargus
Copy link
Member

From a fresh retropie 3 BETA 3 image attemping to install from source I get this error:

Could not successfully build retroarch RetroArch (/home/pi/RetroPie-Setup/tmp/build/retroarch/retroarch not found)

This is my full error log:

http://pastebin.com/5aeE4S3d

@joolswills
Copy link
Member

Compiles fine for me currently - maybe you were just unlucky and built it when some changes had been made and some fixes were needed. RetroArch is in constant development.

@HerbFargus
Copy link
Member

its possible. perhaps I'm doing it the wrong way- I've been selecting the option in the setup script of update individual emulators from binary or source. I just tried it again and it gave me the same error. Is there a different method of compiling it?

@joolswills
Copy link
Member

aha. i was cross compiling on gcc 4.8 - looks as though there is an issue due to this https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52624 - I'll put in a workaround for now, and feed it back to retroarch.

@joolswills
Copy link
Member

libretro/RetroArch#1793

@joolswills
Copy link
Member

please try now.

@HerbFargus
Copy link
Member

you're brilliant- now it compiles - but..... the rgui still freezes.

@joolswills
Copy link
Member

np I will need to git bisect it to see when the problem started etc. Will hopefully find time for this in the next day or two.

@joolswills
Copy link
Member

bisecting the menu issue now.

@joolswills
Copy link
Member

It's quite difficult to pinpoint where the problem started due to various issues appearing during recent development (there isn't a specific point where it works then it stops working, there are various commits where certain functionality breaks ending up as we are now).

While I continue looking into this to send a report upstream, I will lock retroarch to an older stable version, and rebuild the binaries.

@joolswills
Copy link
Member

I have switched retroarch to an older revision - no binaries updated yet - but if you build from source, it should now work again.

@HerbFargus
Copy link
Member

after building from source I can verify that it is now working.

@joolswills
Copy link
Member

I have reported the issue upstream here - libretro/RetroArch#1807 I will likely need to provide further information to debug this - depending if the main developer(s) have rpi hardware and can reproduce it.

@joolswills
Copy link
Member

guess we can close this now - as we have a workaround. At some point I should be able to remove it, once they solve this upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants