I am improving my game design ability, did some brainstorming. Already have around 80 gameplay ideas ))
I want to have clear picture of gameplay before implementing something. After 2 or 3 project without gameplay at all ))
Here is my plan:
1) raw ideas in mind and pictures 2) design document 3) draft demo with simple graphics and animations 4) play testing 5) final graphics and animations

Spent day for implementing steering behaviors for horde.

Recast navigation + avoid nearest neighbor (with prediction, OpenSteer style) + avoid near walls

Recast navigation + avoid nearest neighbor (with prediction, OpenSteer style) + avoid walls only after collision + avoid dynamic obstacles

It needs time to update nav mesh (usually nav mesh updated with 0.5 sec intervals), so sometimes bots can go throw obstacle. Maybe for moving obstacles I need to use same steering behavior as for another bots. Does it look natural? Or need some enhancements?

http://forums.tigsource.com/index.php?topic=8625.0 very funny about indies style=”font-size: 13px;”>

finally understand, what is Velocity Obstacle.
it’s freakin simple ))
print of the source article helps a lot
it will be hordes of zombies!!!

path following force + steering behaviors + wall repulse force red line - path from Recast grreen line - resulting velocity blue line - wall repulse force

I added yesterday simple steering behavior for bots. Movement became more realistic than previous direct path following. Now bot has velocity and acceleration, and it tries to move along current path line.

Remaining task - dealing with walls (current bot position now not exactly on the safe path), moving obstacles.

If you have vector assignment in your code, use Swap member function of std::vector, if you will not need source vector anymore it will save you one memory allocation

void SetPath_Dirty(vec3& path) {
	m_path.swap(path);
}

Deferred shading (plus Doom3-like lighting for slow hardware), more than 1000 lights (without shadows) possible simultaneously, soft shadow maps for omni lights, attenuation maps, fog, bump maps, specular maps, ambient etc.

Some examples of using Recast dynamic navigation meshes in gameplay

</a>

Usually C++ uses linked list to holding free memory chunks, so searching for free chunk is not fast. Especially for small objects. So I decided to optimize allocating of memory using special pool allocator. All small objects in engine have base class, which get and release memory from pool allocator. 3x times optimization for memory allocation (small objects) Look Andrei Alexandrescu Modern C++ Design and in details here</span>