Lol. There's something leaking out of your X button.Workaround for vertical shumps lmao
Lol. There's something leaking out of your X button.Workaround for vertical shumps lmao
Light reflection xDLol. There's something leaking out of your X button.
There were two more pull requests merged today, just 4 hours ago, made by aliaspider:Anyone else having the emulator crash after loading a second ROM? Wii U pro works like a charm, automatically maps the buttons (except I can't use the home button to open the menu for some reason). Snes9x mainline was the only core I tested, granted, after loading a second game, it locked up with a DSI exception. And yes, I did delete all config files, so it's not that.
Keeps crashing for me no matter what, its so unstable, I get DSI exceptions all the time trying different stuff...1.4.0 is more stable. The older ones used to crash too often when I was messing through the menus and such.
There were two more pull requests merged today, just 4 hours ago, made by aliaspider:
https://github.com/libretro/RetroArch/commits/master
cores_names_size was used in a conditional branch without beingI'd recommend checking the new build up.
aliaspider committed 4 hours ago
(WiiU) simplify input code, add button labels for autoconfigs
aliaspider committed 4 hours ago
Keeps crashing for me no matter what, its so unstable, I get DSI exceptions all the time trying different stuff...
Load up any game, then open up RetroArch's menu and go to Controller inside the Quick Menu.My Wii U Pro connects fine (I can even switch pages in the HBL after with L and R !) but I can't seem to map it to anything. How did you guys do it ?
Test the newest nightly, it should have fixed the DSI problems, also remember to clean the CFG files from inside /retroarch/ to avoid consequent DSI exceptions.Keeps crashing for me no matter what, its so unstable, I get DSI exceptions all the time trying different stuff...
Ah I see it's just that I can get it to work only for Player 2. Any way to map it to player 1 currently ?My Wii U Pro connects fine (I can even switch pages in the HBL after with L and R !) but I can't seem to map it to anything. How did you guys do it ?
Load up any game, then open up RetroArch's menu and go to Controller inside the Quick Menu.
There, you can switch the controller input where it says something like RetroPad #1 or something similar.
Search around inside the Settings too, I can't recall exactly where the option is but it has to be there, remember that the controller must be on and synced with the console already so that RetroArch can detect it.
Test the newest nightly, it should have fixed the DSI problems, also remember to clean the CFG files from inside /retroarch/ to avoid consequent DSI exceptions.
I am almost sure it is a problem with the Hotkey not binding to the Pro controller.Is there a reason why I can't map the open/close menu to use the Home button so I don't have to use the game pad to open and close it? I tried to use the Wii U pro pad to do just that and it didn't work for some odd reason.
Rest of the buttons worked fine, but Home didn't. Have you had a chance to test it yet?
Ah I see it's just that I can get it to work only for Player 2. Any way to map it to player 1 currently ?
Edit : oh you got me before ShadowOne, I'll retry that thx
Edit2 : nope, I can only switch between Retropad and Retropad w/analog (FCEUmm) but none is the Wii U Pro.
It has to be either in the Quick menu or inside the Settings.It's under another option, I forgot where, I did it with Snes9x last night.
Stella build with the DSI error fix, you can load multiple ROMs in a row now without a crash. Enjoy!
Thanks to @aliaspider for finding the problem.
BTW, it takes a while to open each folder of ROMs if you have a lot of them, so try to split them into folders with less of them in each folder.
Since this does not have a DSI error now, I will make sure the appstore gets updated to this build.
It has to be either in the Quick menu or inside the Settings.
I can't for the likes of me remember exactly where, and I was having this issue with my Android box because the option is just outside of the initial range of vision and I cannot scroll, nor with a mouse nor with the Box's Remote. xD
But yeah it is inside Settings -> Input I believe.
Nightly build from today 15.20 ish can load more than one game now. Nice one.
One question, do the cores autoload automatically on boot with the latest nightly?I think the only way around the long loading time to read folders is to use Mocha or some kind of CFW that uses the libfat fix; otherwise we need to suffer from not using a CFW. Thanks for confirming that
the builds have been fixed. Gonna spam-load Snes9x ROM loading to test it out.
Will check it out today as well.
Edit: Does everyone else get that weird little context menu when loading a ROM, that it asks what core to choose before loading it up instead of loading it automatically?
I only see 1-17-17 08:22 builds though.
One question, do the cores autoload automatically on boot with the latest nightly?
I remember some previous nightlies didn't autoload the core automatically, even if you were using the individual cores, so I was just wondering.