sebt3
homebrew player (P. & C.)
May I see your pndrun_spi.snes.out file (in /tmp) ?Dosnt seems to work this way
May I see your pndrun_spi.snes.out file (in /tmp) ?Dosnt seems to work this way
Is there anything I can do to fix the issue if it's the latter? I've confirmed that the ROMs work in other emulators at least.snes9x 1.53 is indeed more demanding. But listen carefully, you'll ear where all these cpu cycles are goingseems a little more demanding than the 1.39 & 1.43 based emulators
There's 2 potentials reasons why it wouldnt list your rom : either you have multiple copies of the same rom (aka same CRC32) and then the emulator will always use the same file (the 1st one found while scanning) or the file cannot be loaded during scaning and thuss is not recognized as a rom.I'm liking the emulator a lot, but I noticed that it doesn't seem to detect all of my ROMs (they're all in the same folder if it matters). Is there a way to manually add them?
I would bet it's the former.To be sure, you can actually start the emulator on this ROM manually :Is there anything I can do to fix the issue if it's the latter? I've confirmed that the ROMs work in other emulators at least.
/usr/pandora/scripts/pnd_run.sh -p <path-to-pnd> -e scripts/interface.sh -a <path-to-rom>
/usr/pandora/scripts/pnd_run.sh -p "/path/to/spi.snes.pnd" -m
cd /mnt/utmp/spi.snes
./bin/interface /path/to/rom.zip
/usr/pandora/scripts/pnd_run.sh -p "/path/to/spi.snes.pnd" -u
geez, that's indeed a bug on my side. thanks for pointing this to me.... also fixed (was an easy one)EDIT: instead of renaming, just zip the romThanks! Found out the issue. Bit embarrassed I hadn't noticed before, but games that weren't showing up had a .sfc extension as opposed to a .smc one. Looks like it should just be an issue of switching that around and then I'm good to go.
For .sfc rom files yes.You'll also need to rescan. Remove the "userdb.eet" file from the appdata directory and restartSo if i just zip my roms, it should also work for me??
also this would be awesome if possible^does it have superscope via touchscreen support?
Controler configuration should come with next release. Albeit I'm more playing Torchlight2 these days than codingAnyone got a controller setup recommendation for this emulator? I really like using my Wii U Pro controller with a Mayflash adapter, but it doesn't seem to work natively or with QJoyPad.
Correct, got a hub for it. I've gotten it to work with other emulators and programs, but QJP doesn't recognize it. It's not a big deal though, I'll just use another gamepad for now.I'll assume you've made sure it's not a USB1 device you're plugging into the big USB port without using a hub.
I did, but with no luck due to the PIN. Also tried pairing the Wii U Pro controller with the OUYA controller method detailed on the wiki, but that didn't work either.QJP recognizes other controllers though? That is interesting. Have you tried using the controller over Bluetooth?
Looked at this at all? Could be helpful.I did, but with no luck due to the PIN. Also tried pairing the Wii U Pro controller with the OUYA controller method detailed on the wiki, but that didn't work either.QJP recognizes other controllers though? That is interesting. Have you tried using the controller over Bluetooth?