RetroPlayer Test Builds (updated for Isengard) - lrusak - 2016-01-23
(2016-01-23, 01:10)Appletalk Wrote: (2016-01-22, 20:54)OurJermain Wrote: My tv remote is not working with the latest rp2 build. One before that was working fine.
The RPi build has actually lost CEC support entirely (not just remote input), it does not show up under peripherals as it previously did.
It worked in the previous build as expected.
Could be an issue with the transition from platform to p8-platform.
I'll update the necessary libs and kick off some new builds
RE: RetroPlayer Test Builds (updated for Isengard) - flipside101 - 2016-01-23
Latest Windows build has fixed my wireless XB360 issues however teh OE build still has the dpad problem. Whe you press up it jumps staight to right ,missing down, and like wise pressing right jumps left and move straight on to the next button.
http://www.xbmclogs.com/pky9xezwz
RE: RetroPlayer Test Builds (updated for Isengard) - charlie0440 - 2016-01-23
@garbear, im still having controller issues in the config wizard.
2 logs, both times I get to "up" press a button and it skips "down" same with right and left
Log 1 also had an issue with my right analogue stick. It accepted the first 3 entrys: up right down but won't not accept move stick left
log 1
log 2
Log 1 snippet: has no mention of D pad down or left
Code: 10:44:39 T:140372728428416 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 13 pressed
10:44:39 T:140372728428416 DEBUG: Removing "up" from button map due to conflict
10:44:39 T:140372728428416 DEBUG: Loaded button map with 19 features for controller game.controller.default
10:44:39 T:140372728428416 DEBUG: Previous line repeats 3 times.
10:44:39 T:140372728428416 DEBUG: Event handled
10:44:39 T:140372728428416 DEBUG: Loaded button map with 19 features for controller game.controller.default
10:44:39 T:140372728428416 DEBUG: Previous line repeats 3 times.
10:44:39 T:140372728428416 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 13 released
10:44:39 T:140372728428416 DEBUG: Event handled
10:44:40 T:140372474615552 INFO: AddOnLog: Joystick Support: CJoystickInterfaceLinux::Initialize: opening joystick /dev/input/js0
10:44:41 T:140372728428416 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 12 pressed
10:44:41 T:140372728428416 DEBUG: Removing "right" from button map due to conflict
10:44:41 T:140372728428416 DEBUG: Loaded button map with 19 features for controller game.controller.default
10:44:41 T:140372728428416 DEBUG: Previous line repeats 3 times.
10:44:41 T:140372728428416 DEBUG: Event handled
10:44:41 T:140372728428416 DEBUG: Loaded button map with 19 features for controller game.controller.default
10:44:41 T:140372728428416 DEBUG: Previous line repeats 3 times.
10:44:41 T:140372728428416 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 12 released
10:44:41 T:140372728428416 DEBUG: Event handled
10:44:42 T:140371837298432 DEBUG: Thread JobWorker 140371837298432 terminating (autodelete)
10:44:42 T:140371380352768 DEBUG: Thread JobWorker 140371380352768 terminating (autodelete)
10:44:42 T:140371258660608 DEBUG: Thread JobWorker 140371258660608 terminating (autodelete)
10:44:42 T:140371250267904 DEBUG: Thread JobWorker 140371250267904 terminating (autodelete)
10:44:45 T:140372474615552 INFO: AddOnLog: Joystick Support: CJoystickInterfaceLinux::Initialize: opening joystick /dev/input/js0
10:44:45 T:140372728428416 DEBUG: SECTION:UnloadDelayed(DLL: special://xbmcbin/system/ImageLib-x86_64-linux.so)
10:44:45 T:140372728428416 DEBUG: Unloading: /ImageLib-x86_64-linux.so
10:44:45 T:140372728428416 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 4 pressed
10:44:45 T:140372728428416 DEBUG: Removing "leftbumper" from button map due to conflict
Log 2 snippet shows button 11 pressed and not released until another button has been setup
Code: 10:48:39 T:140487113320320 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 11 pressed
10:48:39 T:140487113320320 DEBUG: Removing "left" from button map due to conflict
10:48:39 T:140487113320320 DEBUG: Loaded button map with 18 features for controller game.controller.default
10:48:39 T:140487113320320 DEBUG: Previous line repeats 3 times.
10:48:39 T:140487113320320 DEBUG: Event handled
10:48:39 T:140487113320320 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 13 pressed
10:48:39 T:140487113320320 DEBUG: Button mapping: rapid input dropped for profile "game.controller.default"
10:48:39 T:140487113320320 DEBUG: Event handled
10:48:39 T:140487113320320 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 13 released
10:48:39 T:140487113320320 DEBUG: Event handled
10:48:39 T:140487113320320 DEBUG: Loaded button map with 18 features for controller game.controller.default
10:48:39 T:140487113320320 DEBUG: Previous line repeats 3 times.
10:48:39 T:140487113320320 DEBUG: Button mapping: rapid input dropped for profile "game.controller.default"
10:48:39 T:140487113320320 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 11 released
10:48:39 T:140487113320320 DEBUG: Event handled
RE: RetroPlayer Test Builds (updated for Isengard) - OurJermain - 2016-01-23
This is lakka, it plays snes at full speed. Will Kodi ever do this? Or is the Kodi system dragging the cpu down too much?
I really would like to know peoples thoughts about this.
Also I am so happy the controller works and that I can play nes at full speed, so much fun. I hope save states will be implemented.
Thanks guys for the great work.
RE: RetroPlayer Test Builds (updated for Isengard) - OurJermain - 2016-01-23
I got a thought about a possible feature.
Auto connect with your trusted Bluetooth controller at the start of a game when none is connected.
It would be a big plus. @garbear
RetroPlayer Test Builds (updated for Isengard) - lrusak - 2016-01-23
(2016-01-23, 16:37)OurJermain Wrote: I got a thought about a possible feature.
Auto connect with your trusted Bluetooth controller at the start of a game when none is connected.
It would be a big plus. @garbear
The Bluetooth connection is the job of the OS not Kodi. OpenELEC will auto connect Bluetooth device if they have been paired.
RE: RetroPlayer Test Builds (updated for Isengard) - darwin - 2016-01-24
Sorry if I've missed this somewhere in the various threads in this forum, but I semi-regularly download a retroplayer build and use it on Windows 7.
The experience with a build + internet archive rom launcher is that most systems don't appear to have any emulator build for Windows (?) and those which do, the games often don't work. With a recent build, only NES games appeared to work.
At the same time, the retroplayer builds break keyboard volume control in the video player, so I inevitably have to revert.
Am I doing something wrong? Also, is there a wiki page somewhere with which cores currently build on which system (windows/linux/osx)? I have a linux Kodi in the house on similar hardware, perhaps I should be using that?
Thanks again for all your hard work on Retroplayer!
RE: RetroPlayer Test Builds (updated for Isengard) - lrusak - 2016-01-24
New OE builds
https://openelec.freestylephenoms.com/retroplayer/
You must remove a couple addons, you can do this via the kodi GUI or via SSH
Please remove game.libretro, peripheral.joystick, and peripheral.steamcontroller
Code: rm -rf /storage/.kodi/addons/game.libretro
rm -rf /storage/.kodi/addons/peripheral.joystick
rm -rf /storage/.kodi/addons/peripheral.steamcontroller
These add-ons have now been built into the system because it isn't possible to track their versions while using them as an installable add-on.
RE: RetroPlayer Test Builds (updated for Isengard) - motamas - 2016-01-24
(2016-01-24, 09:50)lrusak Wrote: New OE builds
https://openelec.freestylephenoms.com/retroplayer/
You must remove a couple addons, you can do this via the kodi GUI or via SSH
Please remove game.libretro, peripheral.joystick, and peripheral.steamcontroller
Code: rm -rf /storage/.kodi/addons/game.libretro
rm -rf /storage/.kodi/addons/peripheral.joystick
rm -rf /storage/.kodi/addons/peripheral.steamcontroller
These add-ons have now been built into the system because it isn't possible to track their versions while using them as an installable add-on.
Thanks Irusak.
Today i installed the new builds and everything i tested works fine (e.g. remote from TV and no crash by opening some menu or disable the airplay function.
RE: RetroPlayer Test Builds (updated for Isengard) - Torkalis - 2016-01-26
(2016-01-24, 09:50)lrusak Wrote: New OE builds
https://openelec.freestylephenoms.com/retroplayer/
You must remove a couple addons, you can do this via the kodi GUI or via SSH
Please remove game.libretro, peripheral.joystick, and peripheral.steamcontroller
Code: rm -rf /storage/.kodi/addons/game.libretro
rm -rf /storage/.kodi/addons/peripheral.joystick
rm -rf /storage/.kodi/addons/peripheral.steamcontroller
These add-ons have now been built into the system because it isn't possible to track their versions while using them as an installable add-on.
Hi,
thanks for builds, but i did your steps above and now i got no emulator running. When selecting an ROM file kodi asks for installinng an Emulator and i choose one of them (i.e. snes9x) and Kodi tells me: Installation failes Check the log... so i did: Even my Kodi.log didn't show even more then the simple information: Installation failed :-)
did i pass a reinstallation of the emulators? in my addon folder there is nothing like game.libretro.snes9x or similar - so is the any emulator on my harddrive?
here is the logpart since choosing the file
Code: 14:33:27 T:140016976676736 DEBUG: Loading settings for game.smc
14:33:27 T:140016976676736 DEBUG: CPlayerCoreFactory::GetPlayers(game.smc)
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: system rules
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: matches rule: system rules
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: hdhomerun/mms/udp
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: lastfm/shout
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: rtmp
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: rtsp
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: streams
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: dvd
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: dvdimage
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: sdp/asf
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: nsv
14:33:27 T:140016976676736 DEBUG: CPlayerSelectionRule::GetPlayers: considering rule: radio
14:33:27 T:140016976676736 DEBUG: CPlayerCoreFactory::GetPlayers: matched 0 rules with players
14:33:27 T:140016976676736 DEBUG: CPlayerCoreFactory::GetPlayers: adding retroplayer
14:33:27 T:140016976676736 DEBUG: CPlayerCoreFactory::GetPlayers: added 1 players
14:33:27 T:140016976676736 INFO: RetroPlayer: Opening: game.smc
14:33:27 T:140016976676736 DEBUG: RetroPlayer: ---------------------------------------
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Game tag loaded
14:33:27 T:140016976676736 DEBUG: RetroPlayer: URL:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Platform:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Title:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Game Code:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Region:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Publisher:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Format:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: Cartridge Type:
14:33:27 T:140016976676736 DEBUG: RetroPlayer: ---------------------------------------
14:33:27 T:140016976676736 DEBUG: GameManager: To open or not to open using game.libretro, that is the question
14:33:27 T:140016976676736 DEBUG: ------ Window Init (DialogContextMenu.xml) ------
14:33:27 T:140016976676736 DEBUG: LIRC: Update - NEW at 974820:1c 0 KEY_ENTER_UP devinput (KEY_ENTER_UP)
14:33:28 T:140016976676736 DEBUG: LIRC: Update - NEW at 975479:1c 0 KEY_ENTER devinput (KEY_ENTER)
14:33:28 T:140016976676736 DEBUG: OnKey: 11 (0x0b) pressed, action is Select
14:33:28 T:140016976676736 DEBUG: LIRC: Update - NEW at 975512:1c 0 KEY_ENTER_UP devinput (KEY_ENTER_UP)
14:33:28 T:140016976676736 DEBUG: ------ Window Deinit (DialogContextMenu.xml) ------
14:33:28 T:140016976676736 DEBUG: ------ Window Init (DialogContextMenu.xml) ------
14:33:29 T:140016976676736 DEBUG: LIRC: Update - NEW at 976460:1c 0 KEY_ENTER devinput (KEY_ENTER)
14:33:29 T:140016976676736 DEBUG: OnKey: 11 (0x0b) pressed, action is Select
14:33:29 T:140016976676736 DEBUG: LIRC: Update - NEW at 976496:1c 0 KEY_ENTER_UP devinput (KEY_ENTER_UP)
14:33:29 T:140016976676736 DEBUG: ------ Window Deinit (DialogContextMenu.xml) ------
14:33:29 T:140016976676736 DEBUG: RetroPlayer: Installing game client game.libretro.snes9x
14:33:29 T:140016976676736 DEBUG: RetroPlayer: Game client installation failed
14:33:29 T:140016976676736 DEBUG: ------ Window Init (DialogOK.xml) ------
14:33:30 T:140016976676736 DEBUG: LIRC: Update - NEW at 978005:1c 0 KEY_ENTER devinput (KEY_ENTER)
14:33:30 T:140016976676736 DEBUG: OnKey: 11 (0x0b) pressed, action is Select
14:33:30 T:140016976676736 DEBUG: LIRC: Update - NEW at 978007:1c 0 KEY_ENTER_UP devinput (KEY_ENTER_UP)
14:33:31 T:140016976676736 DEBUG: ------ Window Deinit (DialogOK.xml) ------
14:33:31 T:140016976676736 DEBUG: OnPlayBackStopped: play state was 1, starting 0
14:33:31 T:140016976676736 DEBUG: CAnnouncementManager - Announcement: OnStop from xbmc
14:33:31 T:140016976676736 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnStop
14:33:31 T:140016976676736 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Announce(flag=Player, sender=xbmc, message=OnStop)
14:33:31 T:140016976676736 DEBUG: RetroPlayer: Closing file
RE: RetroPlayer Test Builds (updated for Isengard) - lrusak - 2016-01-26
(2016-01-26, 15:36)Torkalis Wrote: Hi,
thanks for builds, but i did your steps above and now i got no emulator running. When selecting an ROM file kodi asks for installinng an Emulator and i choose one of them (i.e. snes9x) and Kodi tells me: Installation failes Check the log... so i did: Even my Kodi.log didn't show even more then the simple information: Installation failed :-)
did i pass a reinstallation of the emulators? in my addon folder there is nothing like game.libretro.snes9x or similar - so is the any emulator on my harddrive?
Yes I am aware of the automatic installation issue. Not sure why it is happening.
You can just install the emulator manually
System --> addons --> install from repo --> OpenELEC retroplayer repo --> game addons --> emulators.
RE: RetroPlayer Test Builds (updated for Isengard) - bibi - 2016-01-28
Hi Irusak,
i get this with the last build
Code: 37.414474] snd_hda_intel 0000:01:00.1: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[ 37.944938] NVRM: API mismatch: the client has the version 304.131, but
[ 37.944938] NVRM: this kernel module has the version 352.63. Please
[ 37.944938] NVRM: make sure that this kernel module and all NVIDIA driver
[ 37.944938] NVRM: components have the same version.
[ 37.944949] NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22
[ 70.200330] NVRM: API mismatch: the client has the version 304.131, but
[ 70.200330] NVRM: this kernel module has the version 352.63. Please
[ 70.200330] NVRM: make sure that this kernel module and all NVIDIA driver
[ 70.200330] NVRM: components have the same version.
[ 70.200343] NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22
[ 102.450579] NVRM: API mismatch: the client has the version 304.131, but
[ 102.450579] NVRM: this kernel module has the version 352.63. Please
[ 102.450579] NVRM: make sure that this kernel module and all NVIDIA driver
[ 102.450579] NVRM: components have the same version.
[ 102.450593] NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22
Bibi
Edit
A reboot and everything is back to normal, but the retroplayer openelec repository is empty
RE: RetroPlayer Test Builds (updated for Isengard) - Torkalis - 2016-01-28
(2016-01-26, 21:52)lrusak Wrote: (2016-01-26, 15:36)Torkalis Wrote: Hi,
thanks for builds, but i did your steps above and now i got no emulator running. When selecting an ROM file kodi asks for installinng an Emulator and i choose one of them (i.e. snes9x) and Kodi tells me: Installation failes Check the log... so i did: Even my Kodi.log didn't show even more then the simple information: Installation failed :-)
did i pass a reinstallation of the emulators? in my addon folder there is nothing like game.libretro.snes9x or similar - so is the any emulator on my harddrive?
Yes I am aware of the automatic installation issue. Not sure why it is happening.
You can just install the emulator manually
System --> addons --> install from repo --> OpenELEC retroplayer repo --> game addons --> emulators.
Thank you... I din't see this... shame on me
Where can i enable savegames? Or is my setup not usable for this? I tried bsnes snes9x and snes9x-next an openelec-build - none of my games were saved. The games are on a SMB share and have been added to the Game - files on Homescreen in Confluence. Should the games be stored on local harddrive?
It's a bit annoying to start every day a new speedrun
RE: RetroPlayer Test Builds (updated for Isengard) - natethomas - 2016-01-28
(2016-01-28, 19:24)Torkalis Wrote: Where can i enable savegames? Or is my setup not usable for this? I tried bsnes snes9x and snes9x-next an openelec-build - none of my games were saved. The games are on a SMB share and have been added to the Game - files on Homescreen in Confluence. Should the games be stored on local harddrive?
It's a bit annoying to start every day a new speedrun
Saves aren't implemented yet. Database stuff needed to be reworked and saves are part of that.
RE: RetroPlayer Test Builds (updated for Isengard) - KidVulcan - 2016-01-29
(2015-12-14, 05:13)garbear Wrote: the Steam Controller driver reads controller input using libusb, and injects the input into /dev/uinput/, which can then be read through the Linux Joystick API (or your input API of choice).
I could easily create a binary add-on for steam controller support. It would basically be a c++ translation of this 300 line python file. It would read from the controller using libusb and inject the input into Kodi's joystick API. All I need is a steam controller to test with.
Has there been any updates for this? The Steam Controller is fast becoming my favorite method for playing games on my PC
Thanks
|