{{{
#!html
}}}
= import soy =
PySoy is a 3d cloud game engine for [http://python.org/ Python]. It's object-oriented API is designed for rapid game development while speed critical functions, such as physics processing and rendering, are implemented in C.
Cloud games can be played without having to wait for downloads or managing updates. [http://python.org/ Python]-based games will run on a server and be playable on Android phones, embedded in web pages, [http://www.lightmelody.org/ XMPP] chat clients, and even game consoles.
Our [wiki:License copyleft licensing] protects players ability to download and modify PySoy-based games even when they are run in a cloud environment.
= @hardware_requirements =
Our goal with PySoy is to target the accelerated 3d hardware available to casual game players including netbooks, tablets, and cellphones. This way, any PySoy-based game should be able to run on any device PySoy has been ported to. We believe it is more important for a game to be fun and available to a wide audience than employ cutting-edge shaders.
As part of the [http://copyleftgames.org/ copyleft games community] we know the importance of [http://fsf.org/ free software] driver support. While most cards on the market have basic 3d acceleration available in a free software driver, many still lack stable OpenGL 2.0 support. By targeting lower-end video hardware we ensure that playing a PySoy-based game will not require players to download proprietary drivers.
Thus, our base-line video hardware includes:
* '''AMD/ATI Radeon 9000'''
* '''Intel i915'''
* '''nVidia geForce2'''
* '''Qualcomm MSM7201A (early Android)'''
For game developers we recommend an [http://www.amd.com/ AMD] Radeon-based video card (up to [http://en.wikipedia.org/wiki/Comparison_of_ATI_graphics_processing_units R600 series]) due to the tremendous support they've given the free software gaming community.
= trouble = Ticket () =
As beta-stage software, PySoy is being promoted in order to solicit community help in polishing our API and documentation prior to 1.0 release. We are primarily interested in questions about how to use the engine so that we can clarify or expand our documentation, modify our API to make it more intuitive, or modify the engine's functionality to make it run more smoothly.
If you run into a problem please register an account (doesn't even require email verification) and open a new ticket for it. Be sure to include your CPU, number of cores, video card, driver, and other critical information along with a way to contact you if you don't intend on checking the site often. We'll do our best to resolve every issue before the next release.
= print release_schedule =
We've been working on PySoy since June 2006. We're close to a complete engine but we need your help with testing and feedback. Each 1.0_beta release adds new features and improves past features based on input and bug reports from the community. Our current Beta release schedule is:
* [milestone:beta1 PySoy Beta-1] released in early July 2007 with basic physics and rendering for X11 (GNU/Linux, BSD)
* '''[milestone:beta2 PySoy Beta-2] released in January 2008''' with basic input (keyboard) and native support on Microsoft Windows
* [milestone:beta3 PySoy Beta-3] expected Fall 2012 with stable multithreading (using new libsoy backend) and [milestone:beta3 much more]
* [milestone:beta4 PySoy Beta-4]
* [milestone:beta5 PySoy Beta-5]
* [milestone:1.0-rc1 PySoy 1.0 Release Canidate] for final testing and feedback before 1.0 release
* [milestone:1.0 PySoy 1.0] with solid 1.x API that game developers can rely on
Access to the development tree is available via mercurial. See the [wiki:Download download page] for how to use it.
= contact (us) =
PySoy developers can be found on [http://www.freenode.net/ irc.freenode.net] in the #PySoy channel. If you need help, have questions, or are interested in getting involved there's a growing community on IRC to be part of.
We also have a [http://lists.pysoy.org/mailman/listinfo/pysoy-dev developer mailing list] and an aggregate [http://planet.pysoy.org/ development blog].