Tuesday, August 25, 2009
Not much in the way of changes from 3.38 from a players perspective - I've just recoded some of the engine stuff - treat as a beta-ish release since all manner of bugs can crop up (although I think I've squished them all so far). Main reason for release is so the dll pack isnt needed.
Tuesday, August 18, 2009
I've just uploaded a 1Mb zip file of dlls for the windows version of plague. Unzip them into the same directory as the plague.exe. This fixes the missing "mixer" error message.
This seems to be caused by developing on Win7 - weird. It's kind of ugly having all the dlls there, so I will probably compile on winxp from now on (doesnt seem to be a quicker answer for sorting this out, but I'm happy to be proven incorrect).
Sunday, August 9, 2009
So I've just picked up Code Complete, and I'll be reading through that before working on Plague - see if I can learn some stuff to reduce the complexity in Plague to increase the speed of development.
I'll probably then refactor/recode large amounts of Plague with better coding practices which will mean no visible development for a while - hopefully there will be speed improvements though and the end product should be much easier to continue development on.
The plan is then to stop working on the "battle" simulations and get onto the strategic game layer. Adding features to the battles can resume once theres some more context for them.
I've also picked up a couple of AI programming books. Once I've worked through those I'll upgrade the AI infrastructure from a state machine.
As always, if anyone wants to work on this, feel free; either drop me a line in the comments or send me a gmail to benedictnz.
One thing that would be particularly good is a fast implementation of an A* like pathfinder - I've got one written in python, and its good (and since its written in python, easily modified) but with 10AI using it things get kinda slow.
The other issue thats been bothering me for a while is the simulation will "pause/lag" for a fraction of a second every couple of seconds when doing grunty calculations (eg: calculating partitions during the tech demo). I have no idea why. Does this happen to you? If so, do you know why? If so, can you provide advice or a fix? If it doesnt happen to you, can you let me know your system specs and OS?
- Finally fixed annoying ammo bug (I think) - still some other bugs to do with removal of shrubs and rocks, but not worth worrying about right now.
- Added smoke trail to Rocket Launcher.
- Altered petrol dispersal from molotov grenade.
- Updated "kill" method of Sim.check_boundary()
- changed the way sim command destinations are updated (to decrease and distribute cpu cost)
- corrected 2 errors in resources.py that led to incorrect images for memorised pistols and shotguns
- improved manual map building functionality
- rocks create smoke when destroyed
Monday, August 3, 2009
- Fixed Bug: items could be dropped from inventory after they had been removed, leading to AI bugs where the AI would try to pick up the item (but it wasnt possible, so they'd become stuck). Similar bug (to do with blocks/hives/shrubs) may still be present... nasty bug!
- Survivor AI: Will now turn and fight if pressed too hard by zombies
- Ammo: Ammo generated as part of level recharges (eff. ammo crates)
- Survivor AI: Will now not try to pick up ammo which is mostly empty
- Rocket launcher now has a min_dist before explosion
- Survivors now start all over the map
- Floating point maths error with shadowing fixed (so shadowing always work properly now)
- Tweaked flamethrower stats
- Saved survivors now join your squad (max 4 for speed)
- Improved demo to include survivors and zombies (battle but without the player)
- Need to reduce path finding updates (/or some other path finding speed optimisation)
- continue removing stupid ammo and block bug (grrr)