Maybe because. Autoconfig is not include in asset folder ?[/quote]
are there something I can do to fix it?[/quote]
It has been like that since a few releases, that’s the only reason why I use an older release on the Shield. Maybe you can try contacting the main devs about it.
Thanks
I opened a ticket on github.
like said on github , it’s not an official release , and it doesn’t have the autoconfig in the asset folder. So it’s not an libretro Retroarch issue.
Wait an official release or contact Lordashram to include them. Or put them somewhere in your devices and setup in rgui the path to autoconfig files.
yeah.
Or put them somewhere in your devices and setup in rgui the path to autoconfig files.
and where is the autoconfig file to setup it manually?
What happened to the official release in early September ?¿?
Some things came up that necessitated the delay. There will be some weekly public beta builds soon, followed by an orderly lead-up to the actual release.
Some things came up that necessitated the delay. There will be some weekly public beta builds soon, followed by an orderly lead-up to the actual release.[/quote] Sweet!! Thanks for the fast reply!
RetroArch-2014-10-07 Android: Updated: RetroArch[7270f8], Beetle GBA[e164ec4], Beetle Lynx[68a403d], Beetle NGP[4495b3f], Beetle PCE Fast[530cfd1], Beetle PCFX[da4f5ec], Beetle PSX[36c4fd8], Beetle SuperGrafx[ac51785], Beetle VB[8357a3b], Beetle WSwan[00fe24b], DeSmuME[57bbabf], FBA[21a78df], FCEUmm[1b27f5a], fMSX[70dc911], Gambatte[6f3c97d], Genplus GX[], Handy[05afd1a], Nestopia[59057ed],PCSX_rearmed[eae1ae0], PRBoom[7c5e74a], QuickNES[3e8935c], SNES9x[0724786], SNES9x-Next[c701a1e], TyQquake[c7b2795], UME2014[e648b32], VBA-M[26a030c], VBA Next[3a7dbc7], Yabause[40a7612], 2048[ecf4edc], 3DEngine[c603e65], NXEngine[bc15f7b]
Win64: Updated: RetroArch[7270f8], Common-shaders[8f3d8cb], 4do[700e5c2], Beetle bSNES[7463e68], Beetle GBA[e164ec4], Beetle Lynx[68a403d], Beetle NGP[4495b3f], Beetle PCE Fast[530cfd1], Beetle PCFX[da4f5ec], Beetle PSX[36c4fd8], Beetle SuperGrafx[ac51785], Beetle VB[8357a3b], Beetle WSwan[00fe24b], blueMSX[17a9988], bNES[86b2aaf], bSNES-Cplusplus98[ec74b12], bSNES-Mercury[5fa7c03], DeSmuME[57bbabf], DOSBox[90a24b6], FBA[21a78df], FCEUmm[1b27f5a], fMSX[70dc911], Gambatte[6f3c97d], Genplus GX[], Handy[05afd1a], Hatari[2e6c0c7], MAME/MESS/UME2014[e648b32], Meteor[3cf63d1], Mupen64plus[021ab38], Nestopia[59057ed], o2em[e0be6df], Picodrive[1988176], PRBoom[7c5e74a], Prosystem[646ac1e], QuickNES[3e8935c], ScummVM[725481f], SNES9x[0724786], SNES9x-Next[c701a1e], Stella[394ef8c], TGBDual[abe4cdf], TyQquake[c7b2795], UAE[aadeda2], VBA-M[26a030c], VBA Next[3a7dbc7], VirtualJaguar[dfab661], Yabause[40a7612], 2048[ecf4edc], 3DEngine[c603e65], Dinothawr[059cd8d], NXEngine[bc15f7b], Vecx[7d41e3a]
NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions. MAME/MESS/UME 2014 based on MAME-SVN r32429
@all, Sorry about not including the joystick autoconfigs, a little while back when things like the overlays and autoconfigs et al had got moved around I thought I had included the joystick autoconfigs but apparently I did not. I updated my apk compile script to copy the Android autoconfigs to the correct asset folder now.
Trying to get things caught up as much as I can, as my next round of eye surgery is getting close.
THX again for your hardwork,lordashram!!
But this build even worse for me 
I can manually bind my gamepad uses" custom binds" in previous build ,and it works fine for me.But this 10-07 apk whether I manually bind or not,my gamepad can’t work.
As for the auto configure,It never works on my GPD G58 Gamepad…
Does anyone else have a crashing problem with Gambatte in this build on Windows? I can’t get it to work, but AndresSM doesn’t have a problem with his own fresh build of RA and the core.
Echoing other comments, great work Lordashram, thanks for keeping the builds going!
Sadly, on my JXD7800B, the latest build doesn’t seem to improve the control problem. The JXDs controls aren’t detected and binding controls doesn’t seem to work either =( Additionally, I don’t seem to be able to turn the overlay off (i…e even though it is set to off, it still appears)
Tried launching super mario land, worked as usual here on windows.
But I can’t get my joypad to work anymore. It’s a logitech F310 and it is still recognized in input settings. Tried to make a new retroarch.cfg, rolled back to previous retroarch version, still not working! Any idea what could be going on? The pad is working OK in other emus/games.
edit: It seems I can only reconfigure every individual button in input setting… autodetect isn’t working. And I’m using multi-cfg for each core… will have to remake everything unless there is a fix.
On github : https://github.com/libretro/retroarch-joypad-autoconfig[/quote]
Thanks for that!
by the way… I am having all this problems on NVIDIA Shield too
Do you have SRAM autosave on? That option seems to be unstable at the moment.
Tried launching super mario land, worked as usual here on windows.
But I can’t get my joypad to work anymore. It’s a logitech F310 and it is still recognized in input settings. Tried to make a new retroarch.cfg, rolled back to previous retroarch version, still not working! Any idea what could be going on? The pad is working OK in other emus/games.
edit: It seems I can only reconfigure every individual button in input setting… autodetect isn’t working. And I’m using multi-cfg for each core… will have to remake everything unless there is a fix.[/quote]
IIRC that pad has dinput and xinput mode. It should all work if you change input joypad driver to “winxinput”
Do you have SRAM autosave on? That option seems to be unstable at the moment.[/quote] Yes, autosave_interval = “60”. If I take that out of my config it works! Weird that it wasn’t causing the other cores I tried to crash.
I know that, it’s always in this “xbox like” mode and it’s the gamepad I usually use. Just tried a new retroarch install folder and that’s still the same: no autoconfig of the pad. It’s recognized but you have to reconfigure every button. Before this version it was working from the first launch without issue.
[quote=“Tatsuya79”]
I know that, it’s always in this “xbox like” mode and it’s the gamepad I usually use. Just tried a new retroarch install folder and that’s still the same: no autoconfig of the pad. It’s recognized but you have to reconfigure every button. Before this version it was working from the first launch without issue.[/quote]
If you add what I said to the config it should just work. Set input joypad driver (not input driver) to winxinput, I had the same issue
input_driver = “dinput” input_joypad_driver = “winxinput”
Does the guide button work for you? if it doesn’t you’re still using dinput and button and axis order is quite different on both modes