Posts made by michael-murphy

https://www.youtube.com/watch?v=dsrxdCtNzLg Just showing some of the early results I am getting with my Pi 3.

@Voljega Can you give me edit rights to the compatibility document?  I have gotten in my raspi 3 overclocked it and am testing with compatibility for games that were known to work poor or just not work on the raspi 2.  email is darkbrokenheartz@gmail.com Maybe add a raspi 3 column?

Is it a first or second generation X-Arcade I saw confirmation earlier that Only third generation X-Arcade is supported.

Honestly Recalbox has the answer for almost everything. The only thing I am finding problematic is limiting my romsets for mame/FBA/PiFBA  to be only roms that work and work well. I want all the roms on there, because I can tinker in my own time in seeing if I can add them to the support list by changing settings trying a different core if an overclock brings it to workable but when I leave it for my friends to play on I don't want them to launch a game that will crash the box or just does not work. Now we have good documentation with googledocs showing the known working and games with problems.  And as a community we do fine editing that. Would some kind of exclusion option in Recalbox be viable. For example kind of a like a exclusiongamelist.xml file that could sit inside the roms directory. That file could be auto-populated from the google docs containg rom compatibility or manually edited by the user.  It would contain only known working roms for its companion emulator Then I would want a enable/disable option in the main start menu which allowed to hide known non-working roms that option would enable and automatically only show files in the .xml file as those are the authorotative list of guranteed working roms. When its disabled I could tinker as I want and then if something became working we can then edit the google docs list.   Thoughts opinions? Do we have something that already does that?

Couple of questions, Did you enable Twin Arcade support in your config? https://github.com/recalbox/recalbox-os/wiki/XArcade-configuration-(EN)

I can vote that hell yea it is long depending on how high you get. I have Recalbox 4.0 I have the Samsung Evo 64 GB SD card http://www.amazon.com/gp/product/B00IVPU7AO?psc=1&redirect=true&ref_=ox_sc_sfl_title_1&smid=ATVPDKIKX0DER All roms are on internal storage.  Full NES,SNES, MAME, FBA_LIBRETRO, PIFBA, GBA, FDS, Genesis, Sega32x, GameBoy, Gameboy Advance, and several Playstation cues.

Try this. Configure both controllers Then in controller settings define one as player 1 and the other as player 2 make sure each is defined to its own specific player assignment. Then test.

1. Github is standard, if there is something specific you are confused about the best resource and place to get clarification is in IRC which you can find the link for in the top bar. 4. It is a buildroot release, so the public edition is managed by the recalbox devs.  They maintain te installed packages and emulatores, if you want to modify it yourself totally possible just use https://github.com/recalbox/recalbox-os/wiki/Compilation-%26-Modifications-(EN) 5.  No need to edit that document as nothing changes, the partition should be fat32 at the start, the installation process wll modify the partitions as they are needed.  And the only directory that stores files is /recalbox/share which is a ext4 partition. 6. Dropbox saves are enabled in Retropie and I believe there is a request on github to add that into recalbox. While I personally have no issues with the downloading of roms the recalbox team is not going to open themselves up to that kind of risk. For example even linking to a roms location on the website is against forum rules as it should be so a world in where they provide a module in order to repo access roms is pretty much as likely as hell freezing over  Just going to have to keep with the tried and true google and torrent it yourself even if it is a minor hassle.

Need to make sure its bin and cue anything else wont work*

Great time to order a Raspberry Pi 3 then

Can you take a picture of how you wired it up? I think i might know what is going on.  Is it permanently soldered into the GPIO or are you using a ribbon cable? Can you make sure your wiring matches this http://www.davesclassicarcade.com/vpinball/pics/switches.JPG I am curious because what I think is happening is you are soldered to the wrong connection on the microswitch telling the button it is always on which could mess with boot.  But regardless let me just see a few pictures of how it is wired up.       Possible to check for shorts?   Do you have an extra sd card you can try putting a fresh copy of RBox on I would imagine something happened that messed up the config.  Or you could try to recover it with noobs but I do not know how successfull that would be. A few buttons working, does not mean the driver was enabled unless your sure that you edited the system file c<span style="font-family: Consolas, 'Liberation Mono', Menlo, Courier, monospace; font-size: 13.6px; line-height: 21.76px; background-color: rgba(0, 0, 0, 0.0392157);">ontrollers.gpio.enabled=1 </span>

Try using the SFTP option instead of SCP. I have noticed definite issues using scp with this version of recalbox, but SFTP has worked fine.

So if I got you right, you are wiring the buttons straight to the GPIO controller? Does it boot without anything connected to the GPIO and only not boot with the GPIO cables connected?   Did you edit the recalbox.conf to enable the GPIO driver? Follow the wiring diagram and configuration protocols found here? https://github.com/recalbox/recalbox-os/wiki/Gamecon-controllers-(EN)

Check the wiki, for the instructions on how to change the driver you use for your ps3 controller. Browse to the Webpage http://yourip Go to edit your config file try editing the official driver to one of the other ones and test.

Will you look to integrate the Reicast, Saturn, and gamecube emulators with the extra speed boost? Cannot wait for mine to come in.

1.) Sourcecode is documented on github https://github.com/recalbox/recalbox-os  fully open source project, it uses some dependencies like emulation station and others but those are all on github as well and listed on the dependencies page.   2.) Support for controllers comes as the devs get their hands on controllers.  If it does not work out of the box with something like a standard ps3 driver and requires adjustment just because of the nature of recalbox no access to apt natively.  But you can defenitely checkout the mini howto page to look at using things like JSTest.  You can look at the log files like /var/log/messages and look on the issues page to see if someone has posted a request for support for that controller or ask.  I have seen some of the devs offer to build support in if someone was to send them the controller.  Since they really can't get their hands on one of each type.   So as a community we should do a better job of enabling them to help us.   I have a few controllers I was going to try to send to them and a mayflash.  But if you want to see support move forward engage in the github issues tracker. 3.) Usb Hubs are both supported and recommended.   Works just like any other raspi though need to make sure it is a powered USB hub.   4.) Can you be more specific I know you can set gameboy to split screen.  But most 4 player games are one single screen with all players rendered.  Maybe goldeneye and a few other  N64 multiplayers have 4 splits.   Which emulator and which games are you talking about?  I know that you can edit recalbox.conf from the webui and enale as may controllers as you want though the most players I think you can get in something would be Xmen 6 player version.   5.) Recalbox 4.0.0 Beta uses Ext4 so no more need for fat32  the installation should change everything around so the partitions created are properly /ext4   6.) Define plugin, recal box is a buildroot release so adding a package and with the read only file system yea it can be a little precarious but you can recompile yourself, and commit pull requests upstream in github that is the proper channel to add functionality to recalbox.   There is an API so theoretically easy to create web tool plugins to do different things but I am still searching for full api documentation.   7.) While a cool idea for legality reasons will probably not be picked up by the recalbox dev team. I know kodi has a plugin internet archive manager or something that is trying to do the same thing but all my testing of it has been s**t.  And that is all well for small nes and snes roms but for big boys like sega cd, psx, dreamcast, saturn, just not going to work well to much bandwidth.  I mean theoretically if they were to add some form of Cloud connector which allowed for the rom directory to be configured as Amazon S3 or Rackspace Openstack Swift Storage you could upload your own roms to those diretories but in those scenarios you are opening yourself up to more risk.  So probably best we kind of keep that part on the user but that is just my opinion.

That is helpful, but all my files roms, parents, everything is in lowercase  .zip Can you just confirm for me your simpsons and X-Men is working if I know it is my romset and not something in the compiled emulator I can just download a few different .78 romset versions and try them out.

Wondering if anyone has seen anything funny with a few roms in mame 2003 I have a mame .78 romset that has been working really well, I had sorted it out to match the compatibility list in mame 2003 In the previous release of recal box 3.3.0 17 I had X-Men, Simpsons, Sunset Riders most of the 4 player games working without a problem. But after the upgrade Simpsons, Sunset Riders, Xmen do not work, most all of the other games I have tested work fine, street fighters neo geo games . Simpsons has no parent, and or required bios so not sure what else to try.   Anyone have them working in their version?

Possible to update to Recalbox 4.0? ALso check your configuration file, do you have xboxdrv enabled?  If so do you have ps3 driver disabled?

Can you post the output of your /var/log/messages Also the logs from the web interface   Ssh to your recalbox cd /var/log cat messages   Try assigning a fixed ip from your router to your recalbox     <ul class="inline-list" style="box-sizing: inherit; margin: 0px auto 1.21429rem; padding: 0px; font-size: 14px; font-family: 'Lucida Grande', Helvetica, Arial, sans-serif; line-height: 1.6; list-style: none; overflow: hidden; color: #222222;"> <li style="box-sizing: inherit; margin: 0px 0px 0px 1.57143rem; padding: 0px; display: block; float: left; list-style: none;">