Kodi Community Forum
RetroPlayer Test Builds (updated for Nexus) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Game support (https://forum.kodi.tv/forumdisplay.php?fid=292)
+--- Thread: RetroPlayer Test Builds (updated for Nexus) (/showthread.php?tid=173361)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167

RE: RetroPlayer Test Builds (updated for Nexus) - garbear - 2023-10-17

(2023-10-17, 10:26)sunlollyking Wrote: I was watching a video recently on these shaders which look fantastic https://www.youtube.com/watch?v=yNmJ0n-QMCY

However it got me thinking - Does Kodi support HDR output for Games currently as it's a pre-req for this to work. I know it'll switch over to HDR for a video source that supports it but i'm guessing there's no native HDR support in many of these emulators so wondering what the scope of work could look like to get us into a place to support these types of shaders.

I mean, technically Kodi games work with HDR since https://github.com/xbmc/xbmc/pull/23467 .

However, recognize that a retro game is usually 5-bit color to fit in a 16-bit word, so scaling to 10-bit color doesn't change anything visually if it's done right (which now it is). You might get the expected deeper blacks and brighter highlights that come with HDR but that's from rendering in HDR, not any retro game fidelity.

(2023-10-17, 10:26)sunlollyking Wrote: Garbear did you get a chance to look into Rumble for controllers at all ? It works in menu but not in game for my 8bitdo pro 2.

No, since the Kademlia success near the beginning of September I haven't had much time for Kodi.

RE: RetroPlayer Test Builds (updated for Nexus) - garbear - 2023-10-25

Kodi v21 Beta 1 is now released! I rebased the retroplayer branch on beta 1 and added a build for the Raspberry Pi 5.

Get the goodies at: https://github.com/garbear/xbmc/releases

RE: RetroPlayer Test Builds (updated for Nexus) - Deranged - 2023-10-26

Big thanks to your contribution for the Kodi gaming part. I've been switching between LibreELEC and RetroPie in the past but now I've been shifting towards LibreELEC full time as gaming part of Kodi has improved a lot.

However when I tried your newest build just moments ago I ran into couple of issues. I cannot seem to be able to launch any C64 or Atari ST games as I get always get notification dialog saying "This game can only be played directly from a hard drive or partition. Compressed files must be extracted". My games are stored in my ubuntu NAS and shared via NFS. C64 games are either T64 or D64 files and Atari ST games are ST, STX or IPF files. Should I be able to start games from network share at all? 

Also at least o2em core (Magnacox/Videopac) seems to be broken as seen is attached debug log (lines 2445 onward): https://paste.kodi.tv/sufonojohi

I use Raspberry PI4 and using your LibreELEC retroplayer build taken from here: https://github.com/garbear/xbmc/releases/tag/retroplayer-21beta1-20231024
Every rom I have are stored in my home made ubuntu NAS shared via NFS protocol as I said above. I use 2 different controllers, 8bitdo SN30 pro (connected via 8bitdo bluetooth dongle) and an old C64 joystick attached to RPI via Jakadapter which seem to work just fine. Although sometimes after my 8bitdo controller is turned off I cannot seem to make Kodi see the controller after I turn it back on. I have to reattach the 8bitdo dongle for Kodi to see my controller.

I use Arctic Horizon 2 skin is that makes any difference, it works okayish even though not every gaming related view is (or will ever be) implemented

Let me know if I can provide any more information regarding mentioned issues.

RE: RetroPlayer Test Builds (updated for Nexus) - KOPRajs - 2023-11-01

(2023-10-26, 20:24)Deranged Wrote: My games are stored in my ubuntu NAS and shared via NFS. C64 games are either T64 or D64 files and Atari ST games are ST, STX or IPF files. Should I be able to start games from network share at all?

There is a feature called VFS (Virtual File System) support that the libretro core needs to support in order to be able to load games from a network drive or directly from a zip file.
Here is a list of libretro add-ons which shows the VFS support:
https://kodi.wiki/view/Game_add-ons#Libretro_cores

In your case there might be a workaround. Try to mount the remote filesystem to a local folder and then point the Kodi to that local folder. This way the network stuff will be handled transparently by the underlying OS and Kodi/Retroplayer will see it like a local folder.

Mounting the remote filesystem might be a little tricky, if you are not familiar with Linux, but there is a bunch of guides all over the Internet.

Basic guide:
1. Enable SSH service in the LibreELEC add-on.
2. Login to your LibreELEC box via SSH (see PuTTY).
3. Create the local directory (mkdir /storage/nas).
4. Mount the remote file system (mount -t nfs 1.1.1.1:/remote_folder /storage/nas).
5. Add the local folder as a new source in Kodi -> Games.

This is not meant to be a step-by-step guide, you will need to search a bit.
If you want to have the NFS share mounted automatically after reboot, use this guide:
https://wiki.libreelec.tv/how-to/mount_network_share

RE: RetroPlayer Test Builds (updated for Nexus) - Deranged - 2023-11-01

Thanks for the pointers, mounting nfs share is easy-peasy.

I should have known that this was the issue as in RetroPie I previously mounted via fstab my rom specific nfs shares but somehow I did not even considered this with LibreELEC.

RE: RetroPlayer Test Builds (updated for Nexus) - Deranged - 2023-11-19

Okay, mounting nsf share removed the issue of "This game can only be played directly from a hard drive or partition. Compressed files must be extracted".

However none of my games won't start as I get the error dialog saying "Add-on couldn't be loaded. An unknown error has occurred."

Checking debug log shows following error messages:

Code:
2023-11-19 18:43:08.699 T:1075 error <general>: AddOnLog: game.libretro.hatari: Unable to load: /storage/.kodi/addons/game.libretro.hatari/game.libretro.hatari.so: wrong ELF class: ELFCLASS32
2023-11-19 18:43:08.700 T:1075 error <general>: AddOnLog: game.libretro.hatari: Failed to load /storage/.kodi/addons/game.libretro.hatari/game.libretro.hatari.so
2023-11-19 18:43:08.700 T:1075 error <general>: ADDON: Dll Atari - ST/STE/TT/Falcon (Hatari) - Client returned bad status (5) from Create and is not usable

2023-11-19 18:43:16.467 T:1075 error <general>: AddOnLog: game.libretro.vice_x64: Unable to load: /storage/.kodi/addons/game.libretro.vice_x64/game.libretro.vice_x64.so: wrong ELF class: ELFCLASS32
2023-11-19 18:43:16.467 T:1075 error <general>: AddOnLog: game.libretro.vice_x64: Failed to load /storage/.kodi/addons/game.libretro.vice_x64/game.libretro.vice_x64.so
2023-11-19 18:43:16.467 T:1075 error <general>: ADDON: Dll Commodore - C64 (VICE x64, fast) - Client returned bad status (5) from Create and is not usable

2023-11-19 18:43:26.484 T:1075 error <general>: AddOnLog: game.libretro.o2em: Unable to load: /storage/.kodi/addons/game.libretro.o2em/game.libretro.o2em.so: wrong ELF class: ELFCLASS32
2023-11-19 18:43:26.484 T:1075 error <general>: AddOnLog: game.libretro.o2em: Failed to load /storage/.kodi/addons/game.libretro.o2em/game.libretro.o2em.so
2023-11-19 18:43:26.484 T:1075 error <general>: ADDON: Dll Magnavox - Odyssey2 / Philips Videopac+ (O2EM) - Client returned bad status (5) from Create and is not usable

I only have Atari ST, C64 and Videopac games and none of those work.

Log file: https://paste.kodi.tv/yireyeqoka

If anyone has any ideas how to remedy this I would appreciate it a lot.

RE: RetroPlayer Test Builds (updated for Nexus) - Deranged - 2023-12-07

I updated to newest build https://github.com/garbear/xbmc/releases/tag/retroplayer-20.2-20231205 but still RPI4 builds seem to be using the wrong binary class or something (not really sure what the error message refers).

I'm referring the my previous message's debug log and the error message remains unchanged.

Wonder how we get correct ELF instead of wrong one Wink

RE: RetroPlayer Test Builds (updated for Nexus) - Deranged - 2023-12-07

...as I'm not able to edit my messages I'll add that I also lost my Movie and TV Show databases and all the settings other than path of my sources was reset after updating to the newest build. Might be intentional or might not.

RE: RetroPlayer Test Builds (updated for Nexus) - sunlollyking - 2023-12-08

Garbear i'm not sure if you've had a chance to retest RetroAchievements. It looks like the public api is now back up and online - I'm able to log in using an external RA app. However i still see the same behaviour as before "User Not Verified" error when i try to authenticate with Kodi. I'm not sure if you or anyone else has managed to get this working now its back online?

Thanks as always

RE: RetroPlayer Test Builds (updated for Nexus) - sunlollyking - 2023-12-09

Managed to get a log trace - i haven't seen whether it's the same as the issues before when the API was down but, my password is correct and the account is verified. I've tried with multiple accounts too

2023-12-09 09:14:11.997 T:858     debug <general>: CurlFile::Open - <http://retroachievements.org/dorequest.php?r=login&u=itsmechrissyd&p=******>
2023-12-09 09:14:11.997 T:858     debug <general>: easy_acquire - Created session to http://retroachievements.org
2023-12-09 09:14:12.103 T:919     debug <general>: PushCecKeypress - received key  b duration 111
2023-12-09 09:14:12.192 T:858     debug <general>: CurlFile::Open - <http://retroachievements.org/dorequest.php?r=patch&u=itsmechrissyd&t=FuaW3g1qSVAwY31v&g=0>
2023-12-09 09:14:12.192 T:858     debug <general>: easy_acquire - Created session to http://retroachievements.org
2023-12-09 09:14:12.350 T:858     error <general>: CCurlFile::Open - <http://retroachievements.org/dorequest.php?r=patch&u=itsmechrissyd&t=FuaW3g1qSVAwY31v&g=0> Failed with code 404:

Not in the logs but making the request myself i see
{"Success":false,"Error":"Unknown game","Status":404,"Code":"not_found"}

RE: RetroPlayer Test Builds (updated for Nexus) - KOPRajs - 2023-12-09

In case nobody noticed it, there is now a way to run limited Nintendo 64 emulation in Retroplayer on LibreELEC Generic (x86_64).
The libretro add-on (game.libretro.mupen64plus-nx.zip) can be found here: https://github.com/jefflessard/game.retroarch/releases

After installation from the zip, you need to go to the add-on settings first and change the renderer from GlideN64 to Angrylion.

The support is limited, it requires an x86 with decent performance and don't expect any upscaling etc., but it is playable. You will also need the updated button map from the below PR (replace the buttonmap.xml in the installed add-on with the new one from the PR).

@garbear Regarding the OpenGL support discussed in the PR (https://github.com/kodi-game/game.libretro.mupen64plus-nx/pull/17):
Any good news about the GL support? Hopefully, after the 21 is released there will be a good chance for Lukas to finish the VAO support and then the GL support in libretro cores?

Also, I've checked the RetroArch recently and I've found out that the libretro development is now heavily focused on Vulkan support. Unfortunately, it means that even if we get the GL support (which would still be great!) there are now more and more new features that are Vulkan exclusive, not to mention that the Vulkan renderers get a massive performance boost compared to the GL ones. The ultimate goal for the RetroPlayer should be to get Kodi ported to Vulkan and get the Vulkan hardware rendering in RetroPlayer and the slang shaders support.

RE: RetroPlayer Test Builds (updated for Nexus) - garbear - 2024-01-01

New round of test builds! This time I've fixed controllers on Android for good: https://github.com/xbmc/xbmc/pull/24382

Complete changelog:
 
Builds can be found at https://github.com/garbear/xbmc/releases

RE: RetroPlayer Test Builds (updated for Nexus) - garbear - 2024-01-16

And yet another round of test builds. For my v20 line I updated Kodi to the final 20.3 release, and I updated LibreELEC to v11.0.5.


This time I added the keyboard and mouse to the Player Viewer:


Image

Image


It should highlight the keyboard/mouse when used, just like controllers.


Complete changelog


Fixes
 

Additions
 

Grab builds for v20.3 and v21 Beta 2 from here: https://github.com/garbear/xbmc/releases

RE: RetroPlayer Test Builds (updated for Nexus) - Clutz450 - 2024-01-16

Just downloaded and installed your newest version for 64 bit Windows and the first thing I noticed is that I can no longer map my XBOX One S Controller buttons.  Button presses do nothing.  But they worked on your last versions.  I uninstalled and reinstalled both versions to test and this version my controller worked (KodiSetup-20231231-a166cf01-retroplayer-20.2-x64.exe) but this version (KodiSetup-20240115-b2db485c-retroplayer-20.3-x64.exe) my controller didn't work.

RE: RetroPlayer Test Builds (updated for Nexus) - garbear - 2024-01-17

(2024-01-16, 16:04)Clutz450 Wrote: Just downloaded and installed your newest version for 64 bit Windows and the first thing I noticed is that I can no longer map my XBOX One S Controller buttons.  Button presses do nothing.  But they worked on your last versions.  I uninstalled and reinstalled both versions to test and this version my controller worked (KodiSetup-20231231-a166cf01-retroplayer-20.2-x64.exe) but this version (KodiSetup-20240115-b2db485c-retroplayer-20.3-x64.exe) my controller didn't work.

Thanks for reporting. I found the issue, the Nexus retroplayer branch of peripheral.joystick has an incomplete backport from Omega. I fixed the problem, and I'll pump out newer Windows builds.