[karloss]

Thanks for doing that jason, i will git pull for the update, really enjoy what your doing…

if we could get some of the additions people have suggested, mine :) then this thing would be awesome..

keep up the great work :)

[karloss]

If u press start in emulationstation u can change volume of emulationstations volume, but I don’t think we can control “system” volume via controls..sadly

Sent from my Nexus 5 using Tapatalk

[karloss]

any ideas how to get this to run at boot? I have tried, but only seem to be able to get it to run as root, and it then doesn’t seem to run properly…

if i work it out, i will post back..

thanks

[karloss]

I can’t seem to get this theme to install, i have over written all the folders in .emulationstation, but only some of the themes have chanage, e.g. megadrive is still in the old theme style, with none of the new wallpapers or anything.. :(

[karloss]

ok, i’ll have a look tonight for you mate.

[karloss]

Be careful not to just drag and drop this zip on to your install as this contains config files that will mess up your install..just a warning.

Sent from my Nexus 5 using Tapatalk

[karloss]

It should be easy, make a new folder in ROMs, open the es_systems file and copy the bottom entry and modify for your folder you created..

Then if you take the COMMAND line from Duke and put it in an sh file in the folder you created, it should work..like I said I will try and let u know, or you can try and let me know how it went :)

Sent from my Nexus 5 using Tapatalk

[karloss]

I think I know what to do, I will write you a guide tomorrow if I’m right mate.

Sent from my Nexus 5 using Tapatalk

[karloss]

+1

Sent from my Nexus 5 using Tapatalk

[karloss]

Thanks for sharing this mate! :)

Sent from my Nexus 5 using Tapatalk

[karloss]

That’s cool mate, I love it as well..

Sent from my Nexus 5 using Tapatalk

[karloss]

No problem..I never have any corruption issues, my pi and sdcard arnt readily accessible and I never have to touch the SDcard I just flash images to the media and then do this, works everytime no issues..

Sent from my Nexus 5 using Tapatalk

[karloss]

Just made a sticky for my method for you mate

[karloss]

Maybe see if the guy developing RetroPage can add it? I have suggested something similar to him already..

Sent from my Nexus 5 using Tapatalk

[karloss]

+1

Sent from my Nexus 5 using Tapatalk

[karloss]

I do something similar, but run the entire os from the USB, would that be something you would be interest in as I can post you the steps?

Sent from my Nexus 5 using Tapatalk

[karloss]

N64 emulator isn’t part of retroarch core, so doesn’t use the main config file, it uses its own in /home/pi/.configs (o believe off hand)

I don’t believe it possible to quite via.control yet, or no one has posted it..

Sent from my Nexus 5 using Tapatalk

[karloss]

I would have thought, if u can get it to compile and work, then it should be ok, though I think it only works in X and retro is setup to run from command line

Sent from my Nexus 5 using Tapatalk

[karloss]

do all updates via the retropie script

cd RetroPie-Setup
sudo ./retropie_setup.sh (i think)

then you can do a “source” upgrade, in there you can select what you want to update, as well as keeping the underlying os upto date

[karloss]

This looks really interesting, i assume i just need to gitclone your tree and run the command?

could this be used/extended to allow the editing of the gamelist.xml files, so we can “scrape” images and info for games?

keep up the good work :)

[karloss]

change your gpu ram to 128, i read somewhere that neither the psx/n64 can run with more than that, and running with higher than 128 cause swap file slow down..

[karloss]

HI pet,

I seem to have made some progress, though I don’t know why I need to do it, and I run into another issue..

I used to be able to burn the 1.9.1 image plug in pads and they work fine, but this doesn’t seem the case..

But if I use the rpi-update and update the pi kernel, on reboot the pads start working again, the only problem is, none of the emulators work, they all complain about eeprom error (picodrive) and not being able to read config file (snescore)

I rebuilt the system with a source install last night, and thought the pads still work, none of the emulators started working.

do you have any idea, why i would now need to do this for the pads to work? and if there is a way i can do it without having to update and stuff? as that doesn’t seem to be working right for me..

thanks

karl

[karloss]

well, last night I tried using a different usb hub, and that made no difference at all, so it wasn’t the hub..

I just can’t work it out, I installed debian into a virtual machine and plugged the gamepads in, and they both worked fine, so they are not at fault.

is there anyway for me to force the joy0/1? what infuriates me the most is the fact everything was working one night, went to play the next day, and nothing works, and no matter what i try, they do not work on the pi any-more, i have even tried a different pi, and like i said, re-imaged the sdcard, but no change..i have always used these gamepads and never had a single issue with them before..i guess if no one has any idea i will have to give up and scrap the table..

[karloss]

Could it be that my hub’s power isn’t working right, and though the device is being picked up on the pi, it is not being registered properly? i’m completly stumped at why this has as stopped working…

but it might answer why I get the same via the usb on pi and my hub?…i need my system to work again.. :(

[karloss]

Hey pet,

I have no idea why, but neither of my gamepads are now working or listed…they were listed and working fine last night, when i do lsusb i get

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 05dc:a815 Lexar Media, Inc.
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 006: ID 0d8c:000e C-Media Electronics, Inc. Audio Adapter (Planet UP-100, Genius G-Talk)
Bus 001 Device 007: ID 0079:0006 DragonRise Inc. Generic USB Joystick
Bus 001 Device 008: ID 0079:0006 DragonRise Inc. Generic USB Joystick

and when I do ls /dev/input

pi@raspberrypi ~ $ ls /dev/input
mice

So something has gone wrong, it seems strange that even reburing the sd-card hasn’t sorted it?

any ideas? I only managed about 4 days of my table act finished and now the controllers have stopped :(

[karloss]

Ok, i will check that once my kids are in bed…

they have been working fine, and all of a sudden stopped, but like i said, still work on win7, so they not broken per-say..

[karloss]

hey pet, how can i see if that is the case?

thanks mate

[karloss]

cacophony555 do you fancy sharing you console roms script?

Thanks

Karl

[karloss]

Thanks for re-posting mate :)

[karloss]

Great work Whise thanks for this :)

[karloss]

can this be re-posted somewhere so people can download please?

[karloss]

where are you guys putting megacd images for them to be picked up and work?

thanks

karl

[karloss]

Hi Guys,

Did anyone ever do this? when I reported this, I was running the 1.6 SD Image, and all was fine.

I have now rebuilt (finally got some time on table) and am using the 1.9.1 image, but the sound has lots of interference, and it was perfect before, petrock, has anything changed that could have caused this?

Thanks

Karl

[karloss]

I use these, i think they are great..

http://www.ebay.co.uk/itm/350885499052?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649

[karloss]

this a good idea, negates the need to run ES-Scraper..

would be interested in testing for/with you if you like?

[Author]

Posts