You need to use some kind of double buffering with hwsurfaces. This isn't anything special to the gp2x version, it's how SDL works. Easiest (and best) way is to ignore sdl_doublebuf (doesn't work well with tvout) and to write everything to your own surface, then blit that to the screen at the...
If it could charge from usb then it would be perfect. There's nothing more anoying than having to take a charger to and from work all the time. I virtually stopped using my Zodiac because of this.
Nice one :) I've not had any spare time for months to try and fix this, so I'm glad you managed to find a couple of days instead ;). Did you start from the kernel code, or did you have to throw that rubbish away and start again from scratch?
No, I'm pretty certain he meant he knows it exists on the gp2x. He mentioned hotkey, which is a gp2x app that runs in the background and executes various things when button combinations are pressed, and one of the included apps is a screen grabber. Which is why I don't understand what he's...
You didn't search very hard. Before you posted this, the topic about the firmware needed for SDHC would have been 3rd in the search results for SDHC on this forum.
Your first controller sounds more like a problem with the app rather than the controller (the analogue might be coded to only respond when fully pushed, and just because analogue works doesn't automatically mean the app has been coded for digital inputs too). Find out if the app you were trying...
Fenix uses SDL, and that first screenshot looks how early versions of SDL used to render on TVs. Any recent runtimes (within the last 12 months?, can't remember when SDL was fixed) should work much better.
There's keyboard and joystick (and probably mouse) code in duke that's left over from the original linux sdl port, but to be honest I've never tried seeing if it all still works.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.