[lrusak]

I have some instabilities where certain roms combined with certain cores cause Kodi to crash entirely, I guess the wonderful tight integration causes us to lose some memory isolation of the processes. We're based off of alpha 1 of Leia here so I'm hoping it's just alpha bugs not related to the retro player stuff, so I'm not too worried at this point. If it becomes a problem I'll investigate more and post debug logs.

What platform are you running on?

Posting debug logs and crash logs is always welcome.

[cmiller1]

OS X. And I'll post a log if it happens again, I have thousands of roms and only a tiny tiny number of them had any issues, so if I can remember one that caused it I'll get more info for you guys.

[lefty420]

Is there a way to install the game cores using leia 18.1 on ubuntu 16.04 I have the Game menu via the konami code but not cores. I tried to build myself from some forum posts but I'm not getting anywhere. Any help would be appreciated.

[MrTarantula]

Is there a way to install the game cores using leia 18.1 on ubuntu 16.04 I have the Game menu via the konami code but not cores. I tried to build myself from some forum posts but I'm not getting anywhere. Any help would be appreciated.

If you're on x64, you can take the cores from my builds in the Linux Testing thread. After extracting the zip file, take all the game.* files from share/kodi/addons and place them in your share/kodi/addons folder. Alternatively, you can just use my build as directed in the thread.

[lefty420]

Thanks MrTarantula That worked a treat

[bite_your_idols]

I installed latest millhouse build in my pi2, activated game section with konami code and downloaded some cores/emulators (nes, snes and mame2003). But when I try to run my roms, I select the emulator and an error appear: "Addon couldn't be loaded. Can't load shared library."

Here is my log: https://pastebin.com/86T8QHD7

any idea about what am I doing wrong?

[MrTarantula]

I installed latest millhouse build in my pi2, activated game section with konami code and downloaded some cores/emulators (nes, snes and mame2003). But when I try to run my roms, I select the emulator and an error appear: "Addon couldn't be loaded. Can't load shared library."

Here is my log: https://pastebin.com/86T8QHD7

any idea about what am I doing wrong?

Can you try an earlier Milhouse build, before April 29? There's some instability around addons in Leia at the moment. This is to be expected in alpha software. Also, where did the cores come from? Did you compile them? Or do they come with Milhouse builds?

[bite_your_idols]

OK, thanks. I tried the build from April 28 and it works. I am going to try Retroplayer a bit.
By the way, I downloaded cores using kodi emulator addon section.

[lefty420]

Had the same error as bite_your_idol on ubuntu 64 after updating to the latest 18 nightly. Like MrTatantula said There some instability around addons in Leia at the moment. Pvr and joystick suffered the same affliction but fixes have been pushed to the ppa. Joys of an alpha build I'm not sure if building the new addons will fix the issue atm I'm still learning.

[robweber]

I installed latest millhouse build in my pi2, activated game section with konami code and downloaded some cores/emulators (nes, snes and mame2003). But when I try to run my roms, I select the emulator and an error appear: "Addon couldn't be loaded. Can't load shared library."

Here is my log: https://pastebin.com/86T8QHD7

any idea about what am I doing wrong?

Can you try an earlier Milhouse build, before April 29? There's some instability around addons in Leia at the moment. This is to be expected in alpha software. Also, where did the cores come from? Did you compile them? Or do they come with Milhouse builds?

I don't have any logs since I'm at work but can confirm the same behavior. Prior to April 29 build it was working. I'm getting the same "can't load shared library message". The cores and the shared libretro lib addon come from a repo included with the build. I thought to check the log yesterday and saw a message when trying to load the .so library "/storage/.kodi/addons/game.libretro/game.libretro.so.1.0.1: undefined symbol: ADDON_GetTypeVersion" I had cut/pasted that into notepad to try and search out later, no luck though.

[Milhouse]

I guess all the addons will need to be rebuilt. In the case of libretro etc. that's not likely to happen until LE master is updated with latest Kodi, which should happen in a few days and then the add-ons can be built following that, so most likely another week or two. Stick to the last working test build during this bumpy ride.

[Qwijibo]

I'm having problems gettings controllers to work.

I have tried several different controllers, ps3 over bluetooth, n64, even a keyboard and no games will recognise any input from these.

All roms load with no problems and my keymaps are fine. Have fine tuned them with debugs just to make sure.

Using Milhouse build #419 at the moment but the problem exists even when compiling from Libreelecs master.

Is this a known problem?

[linkinsoldier]

I have also found that some games are not working for me and created a bug ticket some time ago:

https://github.com/kodi-game/game.libret...2/issues/3

I would propose to try a different game

[Qwijibo]

I've tried many, different games, different emulators, different platforms.

On some games I can get maybe one or two buttons to work, but not all.

[Qwijibo]

I have also found that some games are not working for me and created a bug ticket some time ago:

https://github.com/kodi-game/game.libret...2/issues/3

I would propose to try a different game

The issue appears to be that my kodi remote is taking on the Controller 1 position as default.
Anything else I try to connect is falling back into the "Player 2" position. If i completely remove my remote or any other devices and then pair a ps3 controller only then will it connect as "Player 1".

This is not prevalent on other libretro builds which use udev i'm starting to think it could be an issue with peripherals.joystick on the pi.

Hopefully garbear can provide a bit more feedback on this? Normally you would be able to make changes to bluez to force this but obviously isn't the case here.