The pyDDR people didn’t want to integrate this.. and, honestly, it is a bit slow.. However, if you want to expand on it, please go ahead.. PLEASE. Many people would be grateful. Personally, I’m not interested in working on this anymore, but would be willing to give some pointers to anyone who is.
The biggest difference between this and the original pyddr is that instead of directly using the pygame function for updating a surface, it uses an internal one which either wraps around the pygame function or uses glDrawPixel. Since glDrawPixel isn’t accelerated, it is slower than it should be.. but it does work pretty well.
Since there isn’t anything using 3d in pyddr, it wasn’t accepted.. kinda a chicken and egg senario ;) Also, at the time, there weren’t many modules for importing 3d models or doing skeletal animations.. and I didn’t want to do that myself.
