Phew ... working my way through all the responses now. I'm busy for the rest of the weekend so I don't know how much stuff I'll be able to fix. Here's a few quick updates/responses, though. New binary attached.
I changed the base path for the browser to / instead of /dev_usb000 so you can select any device now. You might have noticed that emulation will ocassionally pause for a couple seconds - this is lag from saving the SRAM file to a USB device that's gone to sleep. I haven't tested but I don't think you should experience this if your games are on the internal drive.
New icon added thanks to rubixcube6
. Thanks! It looks spiffy.
There were a couple of comments regarding full screen scaling and higher resolutions. Basically the problem I have right now is that the method I'm using to render graphics to RSX sucks. I am setting up the rendering context like normal, but then instead of really doing anything with it, I just use cellGcmSetTransferData to send pixels directly to the frame buffer, and the scaling function I use is dumb so outputting at 1080p looks the same, just slower. Probably a better solution would be to render to a textured quad and then use hardware scaling or something like that. Once I get all of the setup for that working (it's fun fun to debug display setup issues with no debug hardware) more advanced UI and output stuff should be much easier.
Originally Posted by Mbb
Hm, really? There's probably a few issues like this on different hardware, since I've only tested on one configuration. For reference, my setup:
250GB PS3 Slim
USB thumb drive plugged into port 2
Teensy++ plugged into port 1
HDMI output (1080p)
If you're expriencing weird issues like this, send me what you can about your configuration and I'll see if I can take a closer look.
Originally Posted by tremendazo
Do you mean save states? Normal SRAM saving should work as long as your device is writable.