Opioid2D alpha 3
I've just uploaded the alpha 3 release of the Opioid2D framework. You can see the list of changes here. And download the release from the below links:
- Windows installer for Python 2.4 (187KB)
- Windows installer for Python 2.5 (187KB)
- Source Tarball (545KB)
The usual disclaimer about the framework's alpha status still applies. There are some big internal changes underway. I would especially appreciate feedback from Linux and MacOSX users, as I haven't been able to test the latest release under those platforms yet.
posted by shang at 14:06
15 Comments:
I'd be happy to test it on my Apple iBook again for you (still using that pygame hack to initialize things? lol Apple :(). Are there more test files I can run, or do I actually need to start playing with the framework?
steven: In addition to the example game in the 'examples' folder, the 'test' folder has several small test scripts that utilize a single feature.
I actually refactored all SDL calls to use pygame on all platforms, so the Apple-specific hack isn't needed anymore.
Hmmm.. this version of Opioid is behaving strangely for me -- everything works fine except that the game flickers like crazy. It looks like double buffering got turned off somehow.
I'm looking at display.cpp here, and all the code involving double-buffering and page-flipping has been commented out. What up with that?
chris: Most of the stuff in display.cpp has been moved to the Python side. But you are right, the DOUBLEBUF flag was lost in the refactoring (I wonder why it didn't flicker noticeably on my screen). The double buffering should be fixed in the SVN version now.
Ah, cool. I guess I've just gotta learn how to build Opioid now. Thanks for the quick fix!
chris: In case you need it, I uploaded a binary of the current SVN snapshot here
This comment has been removed by the author.
Alright, I'll give it a whirl once my dad gives me back my laptop... lent it to him and haven't seen it in a week, heh.
Can't believe I've been following this for nearly a year now. O_o
(Tis steven, if you care :P)
Hehe. I can't believe I've worked on this thing for over a year already (on and off). :p
Hopefully I can pick up the pace a bit and finally get O2D ahead of pygext feature- and stability-wise.
Well hey, it's coming along quite nicely. The particle effects are stunning. I'm also particularly interested in the camera functionality... parallax effects will make for vivid starfields in a game I'm designing with a friend. :)
By the way - Numeric seems to be deprecated to an extent. They don't seem to update it anymore and it's classified as "Old Numeric"... no executable for 2.5, either. :(
They seem to be actively developing it under the name "NumPy", though you probably know this already.
"Maintenance has ceased for Numeric, and users should transisition to NumPy as quickly as possible. There is a module called numpy.oldnumeric.alter_code1 in NumPy that can make the transition to NumPy easier (it will automatically perform the search-and-replace style changes that need to be made to python code that uses Numeric to make it work with NumPy)."
viserys: I'm sticking to Numeric mainly because of pygame.surfarray. There's been some work lately to convert pygame to be fully compatible with NumPy too, but the Numeric support is more mature and frankly, Numeric 24.2 seems fast and stable enough that I'm not too worried about it's deprecation status.
BTW. If you need Numeric for 2.5, you can get the binary I compiled from here.
Most excellent, thanks:D
This comment has been removed by the author.
Hate to keep spamming your thread, but I seem to have misplaced your email address and can't find it. :[
I just installed Pygame/O2D/Numeric for Python2.5, and ran your Invaders example. The following error displayed in the console (no stack trace at all):
"Fatal Python error (pygame parachute) Segmentation Fault
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
It works fine when I run it with Python2.4.
viserys: Do you get the error immediately or when example game ends? I'll try to replicate this, but the problem might already be fixed in the SVN trunk. I mainly use Python 2.4 still, so the 2.5 binary only gets some very basic testing.
PS. You can email me directly at sami.hangaslammi@gmail.com
Post a Comment
<< Home