-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
RetroArch 1.7.4 closing out after playing N64 or making adjustments #7177
Comments
If you find the logs, it may tell you what is missing. |
I googled how to do that but the thing is I don't know what I am looking for, it's a sea of information. |
My apologies, I should have been clearer. The log file was generated but I don't know exactly what I am looking for in the log it generates. From what I can tell it shows all the paths, controller configurations, and more. Is there something I should be looking for or should I post the entire thing into here? |
Yes, please post the entire log here. Preferably wrapped in code tags to make it easier to read. |
Gotta remember here that I am new to this so I have no idea how to wrap anything with code tags, but the next post will be the log. |
The log after I launched RetroArch and tried to load GoldenEye 007. [INFO] RetroArch 1.7.4 (Git b1643f9) |
What does "closes out" mean? Is there a crash? Any error message? Does the program just disappear? We need a lot more information as nobody else seems to be having this problem. Maybe a video would make things clearer. |
There is a video in the "Steps to reproduce the bug" section. |
It looks like you've changed other settings besides the defaults (I can see you have auto-load state on at least). Can you please try deleting/renaming retroarch.cfg and retroarch-core-options.cfg and try it again, both without changing any settings at all, and only changing the settings that you are having issues with? There could be a specific option causing the problem that other people typically don't use. |
Excellent, that seems to have corrected the issue. I can exit the game and relaunch it without issue as well as make graphical changes and have it launch again. So in the future don't turn on auto-load state. Thank you for your time on this problem, it's greatly appreciated. |
First and foremost consider this:
Description
I was told to report this issue here via Twitter. When I launch a N64 game using the Mupen64Plus core it will run fine for one time only. If any adjustments are made to the resolution, graphical settings, etc, RetroArch will close out. If I exit the game and relaunch it, RetroArch closes. If I exit RetroArch and relaunch it and try to load any N64 game, RetroArch closes.
Expected behavior
The games to play and to be able to return to them if making any adjustments or relaunching at a later time.
Actual behavior
RetroArch goes to a black screen and closes out.
Steps to reproduce the bug
I have also made a video showing exactly what I have been doing: https://www.youtube.com/watch?v=2RU31lp4GpY
Bisect Results
This issue has been ongoing for me since version 1.7.1 but has gotten slightly better with the current 1.7.4 build. In previous builds if RetroArch crashed from doing the methods described above it would refuse to load any game from any platform or core and instantly close out.
Version/Commit
You can find this information under Information/System Information
Environment information
The text was updated successfully, but these errors were encountered: