Greetings
Does the latest test build supports sixaxis ps3 controller input?
I am using sixaxis controller apk+my ps3 controller (android tv box) but in RGUI input all i can see is retropad /retropad analog / none.
There is no ps3 controller. Is this a known bug?
RetroArch-2014-12-17
OpenElec-x86_64: Updated: New toolchain for RetroArch, updated all cores
I rebuilt my toolchain again along with redoing my kUbuntu Linux vm, if shaders are still not working then I may have an idea as to why but I need this new build tested first. I had ran into a bunch of unforseen issues trying to get this new toolchain going with part of it being no hack job shortcuts. This was definitely a training lesson and I did learn from it and if all goes well then it should make things easier for others to be able to make a toolchain capable of building apps for OE in a more normal and standard way.
Also, at this time I did not inlcude support for pulseaudio but I plan to add hat back in later.
@BlockABoots, thanks a lot for the pic, but the real thanks goes to the devs for all their hard work/
@Android users, I haven’t forgot about you guys, hopefully I can start getting back to compiling test builds for Android soon.
shaders still cause crash back to kodi =(
EDIT: Also the Mednafen PSX core causes a crash back to kodi as well, this core was working fine in the last release. Have tried the command, ‘ldd /storage/.kodi/addons/emulator.retroarch/bin/retroarch > /storage/radeps.log’ in terminal but this now doesn’t launch RetroArch at all
For the android build there are 3 main problems/glitches
There is no input of ANY controller in RGUI. Only retropad and retrokeyboard. There is no ps3 controller too (sixaxis) =| No hotkey enabled button too
This is my retroarch file http://www.2shared.com/file/raiNqpFZ/retroarch.html . It is a little bit messed up 
In settings->input even if i disable the touchscreen overlay, it is still enabled in game
I think these 3 bugs should be taken into account in next release(s)…
Work Great! @lordashram =D
RA’s buildbot post android apk without cores now days.I had tested the newest build with your cores,same problems of keybinding…so I’m sure this is not a compile error but a RA GUI bug , So should we post this issue on RA’s github?
@Haris1977 & @newisle, these issues will definitely need to be posted on github.
@BlockABoots, what was Mednafen PSX has been reworked and renamed to Beetle PSX with Mednafen PSX being a re-port back from Mednafen so there may be a few bugs still. Try using Beetle PSX. I have a few ideas about the shader issue, so hopefully I can get those ironed out in the next build. Also, what about entering text in RGUI in places like the audio hardware device, is that working now or not?
Ah ok ill try Beetle PSX.
Yeah entering text in RGUI now works!! =D
Just a quick question, ive been getting the following warning in terminal when launching RA since the first OE release…
“sh: xdg-screensaver: not found RetroArch [WARN] :: x11_suspend_screensaver :: Could not suspend screen saver.”
What does that warning actually mean?
When I was testing the recent builds with another PC with AMD phenom X3 B75 and Radeon HD 5450, the menu was going too fast regardless if I toggle fast forward or not, and the games are not affected by this. I had to set limit fast forwarding speed to on with 1.0x which means I can’t toggle fast forward on the games. Before that, the menu was going around 888 fps, making it almost impossible to control the UI.
Also, I don’t know if the issue has been fixed on the android with I was testing the latest version and builds from few months ago. When you use retroarch and when you finished using it, you don’t have audio, which means you can’t listen to music or some apps won’t have audio. The videos on YouTube and video players won’t load at all and so e apps would crash. It still happens if you force stop Retroarch from running, and I have to hard reset the system to fix this.
That means vsync is not working with your driver (or you haven´t enabled it) I am on the latest nightly and I have never had that android issue
It was working previously with radeonpro. I had to close out radeonpro for it to work. Also, it was updated to omega driver before it happened. I will test the latest android build to see if it works.
You should remove api detection for RA with radeonpro, then it should work
To all android users who have issue with saving their gamepad binding and the overlay impossible to deactivate:
i ve found something useful to avoid binding all the gamepad each time
after having bind all the buttons in the RGUI, click on 'save new config". it will create a retroarch-date-.cfg file in the data\data\com.retroarch.com folder. copy this file to a full read and write folder of your choice like your sdcard. edit the file with any text editur, find the line input_overlay and edit it :input_overlay = “false” then at each startup, you just click on “configuration” in the rgui and select your cfg file !!
it works perfectly with the 28-11 release ! now we just have to find how to load this cfg file automatically
In the latest android version none of my gamepads ("Wired logitech Rumblepad™ 2, wireless ps3 controller) are detected in RA RGUI
Is it a matter of drivers?
I’ve been pretty busy with my personal life these last few weeks but I did manage to have time to put OpenElec on a spare 2.5: hdd and throw it in my wife’s laptop, giving me something to work with.In my spare time I am still trying to figure out how the heck I manage to originally get sharers to work but not now. If any of the devs see this maybe they might be able to help as I get the following when trying to enable a shader before RA fc’s:
RetroArch [ERROR] :: gl_cg_init :: Invalid profile type
RetroArch [WARN] :: gl_set_shader :: [GL]: Failed to set multipass shader. Falling back to stock.
RetroArch [ERROR] :: gl_cg_init :: Invalid profile type
@BlockABoots, that just means that RA is trying to temp disable the screensaver while it is running but with OE there is no screensaver to disable.
@lordashram: just to ask, did you manage to look into the NetPlay issue at all?
As I’ve been using the buildbot nightly releases and i’m still having problems for some strange reason.
If you’re getting failed to initialize NETPLAY it’s because you have UAC enabled, you might need to add an UAC exception or run as administrator. It uses sockets and for some reason it won’t work without that and there is no way around that. I guess it should give you an UAC prompt but I don’t know how to make that happen, I’ll look into it.
For now give it a shot like that, run as administrator
I have UAC completely disabled, as i find that it’s unnecessary and gets really annoying.
Running as Admin, still does nothing for me.
I don’t understand why it’s not working for me, when it used to work before. 
Well that did it for some user on the channel… I’ve personally tested win32 and win64 nightlies net play and it’s always worked for me
Can I update nightlies by overwriting old files with the ones from a new package except for configuration files or do I have to configure new build each time?