Search results

No problem, no offense taken -- I'm not just looking at TinyGL -- I've also compiled up Klimt, which looks promising (already has support for Fixed point, for example) and seems to run faster than TinyGL (though the jury's still out, and real-life has intruded on my play time with the 2X :-( )...

I certainly understand the benefits of Python -- my day job involves programming almost exclusively in Python. However, for the things that I'm working on, it's just not an option. For one, I'm not using SDL (bleh), I'm using rlyeh's minlib. Second, I'm playing with multiprocessor code and...

Currently, my edit-compile-debug cycle works something like this: On PC (winXP), edit code, build code. Once code is built, put GP2X in USB mode. On PC, browse to appropriate directory, drag target files to GP2X On GP2X, end USB mode, On GP2X, browse to /mnt/sd/Serial (games->Serial) and...

Let's not get too far ahead of ourselves :-) First, this is TinyGL, it's not a full OpenGL implementation. Also, since there's no hardware acceleration available for 3d, it's always going to be pretty slow (I'll do what I can, but there's only so much that can be done) On the other hand, I...

I've ported TinyGL (Homepage here) to the GP2X. My port is very basic right now, and uses rlyeh's minlib for drawing. Future improvements will include fixed point support and probably offloading most of the computation to the second processor. The 'gears' sample runs at about 10 fps. The...