You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within the last few days, I've begun having a problem with fceux, where as soon as I double-click on the fceux.exe to start the emulator, the fceux window opens, then it immediately closes. It didn't previously do this at all; it was working just fine, no problems at all. I don't recall having changed anything that might mess with it, and even the latest clean git build was having the same problem. Other emulators I have in the same parent directory all work fine, including jnes, which points to NES ROMs from the same directory that fceux points to. So I'm guessing it's not my ROM collection that's the problem here either. Am I missing something here that might shed light on this problem?
The text was updated successfully, but these errors were encountered:
Strange. I happened to run the Windows DISM and now fceux starts up just fine. I have no idea what might have caused the problem, but it seems to have gone away. I'll close this issue.
System info:
Alienware 17 r4
Intel Core i7 7820HK @2.9 GHz
16 GB RAM
Nvidia GeForce GTX 1070
Windows 10 1809
FCEUX versions affected:
2.2.2
2.2.3
latest git build
Within the last few days, I've begun having a problem with fceux, where as soon as I double-click on the fceux.exe to start the emulator, the fceux window opens, then it immediately closes. It didn't previously do this at all; it was working just fine, no problems at all. I don't recall having changed anything that might mess with it, and even the latest clean git build was having the same problem. Other emulators I have in the same parent directory all work fine, including jnes, which points to NES ROMs from the same directory that fceux points to. So I'm guessing it's not my ROM collection that's the problem here either. Am I missing something here that might shed light on this problem?
The text was updated successfully, but these errors were encountered: