Were I a better man, I would have just hacked the gem installation to want the most recent stable version of OGRE. For the moment, I'm playing nice.
The current stable OGRE gem is 0.2 (and is named ogre.rb), and it wants ogre-1.4.4, which you can get reasonably easily by following the OGRE source installation directions and string-substituting appropriately. 0.3 is unstable and I was unable to install it on 64-bit Hardy.
I also needed to install osi-1.0.0, which is available on sourceforge. http://downloads.sourceforge.net/wgois/ois-1.0.tar.gz?modtime=1182593947&big_mirror=0 The installation procedure for that is directly analogous to the installation steps in the ogre install docs.
Additionally, I needed to muck around in the gem directory itself in order to be able to run any sample code. Specifically, plugins.cfg and resources.cfg needed to be moved into the gem root and resources.cfg needed /samples prepended to the path. The plugin folder needed to be /usr/local/lib/OGRE, although I think that I only needed to edit that because I had previously edited it on some wild goose chase.
With that, I was almost able to run the samples, but it resulted in a black screen that just wouldn't die. (Q, esc, C-c, CAD all failed) Turns out that I needed to adjust the settings: RTT Preferred Mode of PBuffer did the trick. (samples needed sudo to execute successfully) Exiting the rendering was accomplished via Q and arrow keys plus my touchpad allowed to to pan and zoom.
I'm not convinced that OGRE is intrinsically the way to go, but it certainly is getting the most attention from the Ruby community (the ruby irrlicht bindings are over a year old, and almost certainly out of date by now), and it seems like it would have a pretty strong symbiotic relationship with pyOGRE. Also, Google likes it enough that they gave it Summer of Code(rs). Rubygame seems like it might be too low-level, and Shoes doesn't seem capable enough at the moment.
As an interesting aside, Perl is apparently the best language for OpenGL development, running fully as fast as C. This raises a fairly compelling argument to have a compiler for a scripting language with a higher-level interface to OpenGL to target Perl for OpenGL apps. I may look into that project, as it seems potentially sexy as all hell.
The advantages that Python can currently cite for graphics dev over Ruby are largely documentation advantages, although Blender is also potentially a moderately big deal. Pygame is also probably somewhat more mature than Rubygame. That said, the incentives for using Python as a SDL API apply at least as strongly (and probably more so) to Ruby, so it still seems like a good route to go down if you want to do rendering/game dev using a high-level language.
If I end up using it seriously, I'll try to correct the heinous lack of docs.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment