Warlocks - Day 7
mauve on 2013/04/21 09:58
of Wasabi/Idli
Things that dropped today included damage, death, AI, spell selection, more spells, music and sound, the latter taking only about half an hour thanks to the author of this pre-prepared pack of spell sounds I hit upon just when I thought it would be too late to get sound into the game.
The only final day snag was when my models started blowing up into a mangled mess of triangles as I was trying to add the death animations. I finally cracked it by baking bone envelopes into vertex weights and then doing weight painting. Make sure to keep vertex weights normalised!
I started the day with a small but significant improvement: the wizards have different robes, cloaks and different colour crystals in their staffs. This took a rewrite of the model/material loading code so that materials could be shared between models or not, while vertex lists remain shared.
This shield effect is probably the highlight of day 7 - it turned out to be relatively easy graphically - just a few lines of shader code and a light - but what really sells it is lepton's ability to make particles deflect off it:
This laser effect on the other hand isn't all I wanted; it doesn't have the sense of hurling energy at your foe.
There's a bunch that didn't get done. I had tons more ideas for spells, of course, but I was keen to get in a system of charging up a spell, costing more mana but getting more explosive effects. The scenery is also very barren; I was going to put in a grass texture and add a bunch more background flora.
All in all, I had a lot of fun this Pyweek. I've disclosed on the entry page that this built on the ramshackle collection of 3D code I'd pulled together pre-Pyweek. Nearly everything has been rewritten and improved, so it would be a shame to be disqualfied, but I'm not in it for the win this time. I've improved my 3D graphics knowledge, learned a few ounces more Blender, and battle-tested the scenegraph code which I hope to get documented soon. I look forward to playing everyone's games!
(log in to comment)
Comments
petraszd on
2013/04/23 22:27:
Game runs on 64bit Linux (OpenSuse) without any problems. Dependencies are a little bit tricky to install.
mauve on
2013/04/23 22:40:
petraszd on
2013/04/24 12:31:
Yeah, gletools is also small inconvenience. You need to download it by hand and python setup.py install.
reidrac on
2013/04/24 13:30:
pip install http://pyglet.googlecode.com/files/pyglet-1.2alpha1.tar.gz
For gletools:
http://hg.codeflow.org/gletools/archive/tip.tar.gz
As long as you install Pyglet 1.2 first it will work!
Tip: you can distribute the projects with your game IF they're pure Python (looks like is the case). You can do python setup build and it will generate a build/*/... directory. You can safely add the contents in you source code tree.
For example (gletools, my game in ~/mygame):
1. python setup.py build
2. cp -R build/lib.linux-x86_64-2.7/gletools/ ~/mygame
That's it! When you import gletools Python will search for the module in the same directory your script is running (ie. run_game.py).
I hope this helps!
reidrac on
2013/04/24 13:31:
For gletools:
pip install http://hg.codeflow.org/gletools/archive/tip.tar.gz
mauve on
2013/04/24 17:18:
I'm not honestly sure whether we require pyglet 1.2a or whether it will work on 1.1.4, I just haven't tested on anything older than 1.2a.
Ryan42 on
2013/04/29 03:32:
import error: no module named lepton.
I found lepton itself inside the package, so I don't understand why it can't seem to find it. Is there something else I'm missing?
drnlm on
2013/04/29 07:57:
<br>
You still need to install lepton - I think it was mentioned in the Readme.
mauve on
2013/04/29 22:19:
This requires a compiler. The way I do it on Windows is make sure MinGW in installed and on the path then run
python setup.py build --compiler=mingw32
python setup.py install
Other platforms may just be able to run
python setup.py install
I was going to put together a py2exe package, but the only Windows machine I have access to doesn't have up to date graphics drivers and prints a message about wrong OpenGL version. It also won't let me install what ATI/AMD claim are the current drivers for that chipset, so I'm afraid I'm stuck on that front.
(If you get messages about missing definitions in OpenGL, update your graphics drivers.)
Hugoagogo on
2013/04/21 11:57:
Awesome except for the mouse in the screenshots, I spent about 30 seconds shaking my mouse wondering why it wasn't working before I realised.I am going to have to have a look through your code to see how shaders and stuff works.