[a1rwulf]

bibi, I made that OE build and although I am not running that exact one at the moment, I tried a SNES game on my current build last night and all worked fine.

I'll upload a new build for you to try in a few days. Was hoping to get the analogue stick working on n64 games with latest mupen64 before uploading a build, but I have no idea what is wrong.

I'll try to have a look at it.

[bibi]

Thanks Charlie0440 !
I can test on x64_linux and raspberry pi 2.

Here is my Logitech_Logitech_Dual_Action_12b_6a.xml, i dont know how to push it on git repository :

Code:

<?xml version="1.0" ?>
<buttonmap>
    <device name="Logitech Logitech Dual Action" provider="linux" buttoncount="12" axiscount="6">
        <controller id="game.controller.default">
            <feature name="a" button="1" />
            <feature name="b" button="2" />
            <feature name="back" button="8" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="leftbumper" button="6" />
            <feature name="leftstick">
                <up axis="-1" />
                <right axis="+0" />
            </feature>
            <feature name="lefttrigger" button="4" />
            <feature name="right" axis="+4" />
            <feature name="rightbumper" button="7" />
            <feature name="rightstick">
                <up axis="-3" />
                <right axis="+2" />
                <left button="2" />
            </feature>
            <feature name="righttrigger" button="5" />
            <feature name="start" button="9" />
            <feature name="up" axis="-5" />
            <feature name="x" button="0" />
            <feature name="y" button="3" />
        </controller>
        <controller id="game.controller.gba">
            <feature name="a" button="0" />
            <feature name="b" button="2" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="leftbumper" button="6" />
            <feature name="right" axis="+4" />
            <feature name="rightbumper" button="7" />
            <feature name="select" button="8" />
            <feature name="start" button="9" />
            <feature name="up" axis="-5" />
        </controller>
        <controller id="game.controller.genesis">
            <feature name="a" button="0" />
            <feature name="b" button="3" />
            <feature name="c" button="2" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="mode" button="8" />
            <feature name="right" axis="+4" />
            <feature name="start" button="9" />
            <feature name="up" axis="-5" />
            <feature name="x" button="1" />
            <feature name="y" button="4" />
            <feature name="z" button="5" />
        </controller>
        <controller id="game.controller.n64">
            <feature name="a" button="1" />
            <feature name="analogstick">
                <up axis="-1" />
                <right axis="+0" />
            </feature>
            <feature name="b" button="2" />
            <feature name="cdown" axis="+3" />
            <feature name="cleft" axis="-2" />
            <feature name="cright" axis="+2" />
            <feature name="cup" axis="-3" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="leftbumper" button="6" />
            <feature name="right" axis="+4" />
            <feature name="rightbumper" button="7" />
            <feature name="start" button="9" />
            <feature name="up" axis="-5" />
            <feature name="z" button="8" />
        </controller>
        <controller id="game.controller.nes">
            <feature name="a" button="1" />
            <feature name="b" button="2" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="right" axis="+4" />
            <feature name="select" button="8" />
            <feature name="start" button="9" />
            <feature name="up" axis="-5" />
        </controller>
        <controller id="game.controller.ps">
            <feature name="circle" button="2" />
            <feature name="cross" button="1" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="leftbumper" button="6" />
            <feature name="lefttrigger" button="4" />
            <feature name="right" axis="+4" />
            <feature name="rightbumper" button="7" />
            <feature name="righttrigger" button="5" />
            <feature name="select" button="8" />
            <feature name="square" button="0" />
            <feature name="start" button="9" />
            <feature name="triangle" button="3" />
            <feature name="up" axis="-5" />
        </controller>
        <controller id="game.controller.snes">
            <feature name="a" button="2" />
            <feature name="b" button="1" />
            <feature name="down" axis="+5" />
            <feature name="left" axis="-4" />
            <feature name="leftbumper" button="6" />
            <feature name="right" axis="+4" />
            <feature name="rightbumper" button="7" />
            <feature name="select" button="8" />
            <feature name="start" button="9" />
            <feature name="up" axis="-5" />
            <feature name="x" button="3" />
            <feature name="y" button="0" />
        </controller>
    </device>
</buttonmap>

Bibi

[charlie0440]

New OpenElec Generic 64 build here, based on tip of OpenElec 6.0 and garbears kodi from retroplayer-15.2 branch

There are some slight alterations, mainly caused by me enabling mupen64, it compiled fine but the analogue stick is not working for me.
Build details can be seen from my https://github.com/CharlieMarshall/OpenE...player-bk2repo:

@a1rwulf if you have a minute can you look at my repo and see if my changes would cause the analogue stick to stop working?

@bibi, I just quickly tested snes, nes, n64 and genesis and they all worked fine.

@garbear, since the splitting of bsnes-mercury to accuracy, balanced and performance, can you tell me how to compile it. I have created what I believe are the necessary scripts (here) for the game.libretro.bsnes-mercury-etc but since the recent commit which changes:

Code:

-find_package(libretro-bsnes-mercury REQUIRED)
+find_package(libretro-bsnes-mercury-accuracy REQUIRED)

where can I find libretro-bsnes-mercury-accuracy, while previously libretro-bsnes-mercury was being sourced from https://github.com/libretro/bsnes-mercury. any help appreciated

[garbear]

@garbear, since the splitting of bsnes-mercury to accuracy, balanced and performance, can you tell me how to compile it. I have created what I believe are the necessary scripts (here) for the game.libretro.bsnes-mercury-etc but since the recent commit which changes:

Code:

-find_package(libretro-bsnes-mercury REQUIRED)
+find_package(libretro-bsnes-mercury-accuracy REQUIRED)

where can I find libretro-bsnes-mercury-accuracy, while previously libretro-bsnes-mercury was being sourced from https://github.com/libretro/bsnes-mercury. any help appreciated

The upstream is the same libretro-bsnes-mercury repo. It is passed a profile name at compile time, see https://github.com/kodi-game/game.libret...511c3ccR21

Libretro add-ons have two parts: the add-on fluff, game.libretro.bsnes-mercury-accuracy, and the libretro core libretro-bsnes-mercury-accuracy. You've missed the second part at packages/mediacenter/kodi-binary-addons/libretro-bsnes-mercury-accuracy, et. al.

When you copy-paste the package.mk for https://github.com/CharlieMarshall/OpenE...package.mk , change the command "make" to "make profile=accuracy", and balanced and performance for the others.

[garbear]

Also, in case you missed it, new builds have been posted with additional cores. Including the three bSNES Mercury profiles, Snes9x and Snes9x Next, and MAME as well.

[garbear]

Here is my Logitech_Logitech_Dual_Action_12b_6a.xml, i dont know how to push it on git repository :

Added in https://github.com/kodi-game/peripheral....it/36c69a0 . thanks

[grumpygamer]

When as core port says "included in Linux and OSX" does that include Openelec?
Thanks

[bibi]

I just tested your last build, i get the same issue. Wonder if it isnt because my roms are on a nfs share...
Will try again this afternoon

[bibi]

Ok, with roms in local, it works!
For now, Nes, SNES games works.
GameCube games works a little bit, mainky access to the menu.
Playstation games are in good shape, only issue is wth bios not found, i put them in the same directory than the roms.

In general, its really in a good shape, strange to find back the old games, specially on a big screen.
Thank you all.

Bibi

[holydhaliwal]

Testers: I've rebased on 15.2. Windows and OSX have been built by jenkins and are being uploaded to the mirrors

For some reason when opening a .bin PS1 rom from kodi I don't get a dialogue asking which emulator to use to handle the file, thus it seems to default to Atari 2600 and tries playing the rom with the Stella emulator. I believe the relevant info starts at line 35 in this log http://xbmclogs.com/p8x2aymoy#line-53. What is also strange is that if I use the Internet Archive Rom Launcher to launch a PS1 game it seems to work fine http://xbmclogs.com/pcr1ods8z. Opening an .iso rom doesn't seem to do anything http://xbmclogs.com/pcahlcr2k. Opening a .img rom also doesn't seem to do anything http://xbmclogs.com/pihbdunqy.

EDIT: This is on the latest OSX build by the way.

I'm getting the same behaviour on the latest OS X build.

I still get the same behaviour on the latest OS X build. Sorry if it seems like I'm pestering haha, just curious as to where the problem lies. Is there some option to manually assign specific file extensions to specific emulator cores? Or some other way to force kodi to attempt to open a specific file with a specific emulator?

[charlie0440]

When you copy-paste the package.mk for https://github.com/CharlieMarshall/OpenE...package.mk , change the command "make" to "make profile=accuracy", and balanced and performance for the others.

Thanks, thats what I needed. Got the mercury split all compiled now.

Next issue ...

Adding the snes9x & snes9x-next cores, I added these under this commit

The libretro-snes9x and libretron-snes9x-next cores compiled fine and the .so files are there. But when it comes to the game.libretro.snes9x & game.libretro.snes9x-next I get a compile error,

Code:

-- Install configuration: ""
CMake Error at cmake_install.cmake:44 (file):
  file INSTALL cannot find
  "/mnt/Disk11/github/OpenELEC.tv/build.OpenELEC-Generic.x86_64-6.0-devel/game.libretro.snes9x-next-edbfb04/game.libretro.snes9x-next.so".


Makefile:61: recipe for target 'install' failed
make[1]: *** [install] Error 1
make[1]: Leaving directory '/mnt/Disk11/github/OpenELEC.tv/build.OpenELEC-Generic.x86_64-6.0-devel/game.libretro.snes9x-next-edbfb04/.x86_64-openelec-linux-gnu'
Makefile:9: recipe for target 'release' failed
make: *** [release] Error 2

log files: snes9x & snes9x-next

[Rollingstone]

Ok, with roms in local, it works!
For now, Nes, SNES games works.
GameCube games works a little bit, mainky access to the menu.
Playstation games are in good shape, only issue is wth bios not found, i put them in the same directory than the roms.

In general, its really in a good shape, strange to find back the old games, specially on a big screen.
Thank you all.

Bibi

I have the same experience with roms on my samba-share. Isn't it weird that roms should be local?

[Scourge]

Havent tried OE builds lately, but on my Windows machine, this is not the case. Playing roms from my NAS works just fine.

[Rollingstone]

Havent tried OE builds lately, but on my Windows machine, this is not the case. Playing roms from my NAS works just fine.

I can't verify on windows, but both my OSX and OpenElec builds (most recent) won't work. Nevermind, I can play from local roms.

[Rollingstone]

I have my MSX games working now, BIOS is installed (and I can make a package or something to make it installable like an addon if somebody tells me how to do this). However, my controller doesn't work. So still I cannot play my MSX games!

There is no controller to configure under the input menu, I think that is the problem. Should I manually add my Xbox360 controller to a configuration file? I have found that every controller configuration goes to an .xml file under addon_data/peripheral.joystick/resources/buttonmaps/xml/cocoa and then there is Xbox_360_Wired_Controller_v1118_p654_15b_6a.xml with all the configurations. However, no msx controller is defined, so I concluded that could be the problem.

Anybody an idea what lines I could add to the xml file to control BlueMSX?