[garbear]

Hey charlie0440,

bet you weren't expecting things to get worse after a couple years

To add multiplayer support, I had to rewrite Kodi's controller handling from scratch. This turned out to be a bigger project than RetroPlayer itself, totaling thousands lines of code (~50%) greater than RetroPlayer.

The controller configuration utility was a proof-of-concept to get controller input testable. I'm rewriting this from scratch, so these errors shouldn't translate over when v2 hits. Hoping to finish this by january.

If you're wondering, here's what to expect: my plan for the new controller utility has the list of platforms vertically on the left, with a list of mappable buttons vertically on the right, and the controller image in between. The buttons will always be visible, as opposed to how they are now, shown in a dialog box only when a controller has been selected. Less activity = less complexity = less bugs.

That's my idea at least. any feedback is welcome.

[charlie0440]

bet you weren't expecting things to get worse after a couple years

No I would disagree. Once I manually configured the controller, it played all my Genesis games perfectly. Good work

One question, your first post states "OpenELEC includes N64 support!" I don't seem to have Mupen64 Plus or any n64 emulators installed. Where can I get these addons or do I have to compile them from https://github.com/kodi-game? Note I am not on a PI im running a generic build. Also my .n64 files are not listed in the directory structures. Thanks

[a1rwulf]

Hey, it seems n64 is disabled by now in the builds.
It's still in it's early stages and unfortunately I couldn't work much on anything for the last few months.
I guess it's still available in older builds if you want to try it, but it's not too exciting at the moment (besides for me as it took me quite some time^^).

[garbear]

The Mupen64 emulator started throwing compile errors, so I don't think it's included in OE atm. x64 builds should still contain a1rwulf's GL work, so you could use a current build but copy Mupen64 over from an older one. Note that GL only works on x64, no ARM support yet, so no n64 on RPi

[Rollingstone]

Hi guys,
I'm looking forward to gaming on my Generic OpenElec system. However, the builds for Generic OpenElec are .zip files that contain only SYSTEM and KERNEL files. How do I tranform them into a bootable USB-stick?

Rollingstone

[charlie0440]

if you aren't running OpenElec at the moment, download it from their website. Put it on a USB and boot up a plain OpenElec.

Now update OpenElec to garbears version by, unzipping and copying the all the files (SYSTEM & KERNEL) to the Update folder on OpenElec. Full instructions here: http://wiki.openelec.tv/index.php/Updati...g_OpenELEC

[Rollingstone]

if you aren't running OpenElec at the moment, download it from their website. Put it on a USB and boot up a plain OpenElec.

Now update OpenElec to garbears version by, unzipping and copying the all the files (SYSTEM & KERNEL) to the Update folder on OpenElec. Full instructions here: http://wiki.openelec.tv/index.php/Updati...g_OpenELEC

Thanks! That is easy. I have copied the files to the update directory on my current openelec.
However, I got an error while updating: Check Filesize... Check failed and it boot to my current OpenElec installation. I'm currently running OpenElec 6.0.0 (Linux kernel 4.1.12), is that a problem? I use the confluence skin, because I read somewhere that is mandatory for Retroplayer. Any thoughts?

[Solo0815]

just copy the TAR-file into the Update folder, NOT System and Kernel!

[charlie0440]

just copy the TAR-file into the Update folder, NOT System and Kernel!

The files garbear has provided is a zip which I believe does not work like the tar which OE will extract for you. You have to extract the SYSTEM KERNEL and md5s to the update archive.

[garbear]

Should i upload the tar next time I do a round of builds?

[Rollingstone]

just copy the TAR-file into the Update folder, NOT System and Kernel!

The files garbear has provided is a zip which I believe does not work like the tar which OE will extract for you. You have to extract the SYSTEM KERNEL and md5s to the update archive.

Thanks @charlie0440 This works for the OpenElec generic build: extracting the .zip including the .md5 files to the OpenElec /update directory.
@garbear: the .zip is just fine, but one just has to know to extract the contends in the update directory. Should I write a short text about installing the builds? Maybe you could add it in the first post?

[Martijn]

Should i upload the tar next time I do a round of builds?

yup just upload the .tar file and users could just put it in /update/ and reboot

[garbear]

New builds for windows and OSX uploaded.

Major changes to how button map XML data is handled. XML is split into one file per device. The joystick add-on scans the buttonmaps folder for new files. XML files added/modified while Kodi is running will be automatically loaded the next time Kodi starts a game.

This marks the final button map schema change. Good time to start collecting button maps. If you want your button map included in the add-on, send a pull request to peripheral.joystick: https://github.com/kodi-game/peripheral.joystick

[iainmacleod]

How can I go about making a build for OpenELEC, raspberry pi 2 and Chromebox platforms?

[Heat]

Been a while since I checked here, been to busy to test stuff.

garbear, I found this guy is making a steam controller driver, can it be added to kodi once its complete? Have one and its become my favorite controller.

link: https://github.com/ynsta/steamcontroller

Also got a question, how easy is it to update the cores? The PSP one seems to get frequent updates, so I wondered how hard it is to do it. Wonder if it is easy one can make a program that detects when a stable build is up and updates the retroplayer cores...