Irrlicht Engine

Digging out an undead project, worked some on the terrain. Before:


Optimized the triangle placing - more tesselation closer, less far, and the flat ground uses less tris. With this move also moved from one generated block to six of these manual blocks, which gave 20% more fps simply by frustum culling the blocks (manually in 2d, due to the bounding box not representing a gpu-generated terrain but the flat block). I guess I could manually tweak the bounding boxes and leave the culling to irrlicht, but since I draw the terrain manually instead of the scene manager anyway, it would only save me from writing some custom code instead of copy-pasting parts of the isculled function. After:

ARSA Framework rendering pass.

interesting....

Sooo many passes! XD

I often use less render passes in Blender Compositor! XD

ARSA Framwork - Feature

Finally! Staying out of these things for a few months really makes it hard to get back to speed.

Pathfinding via bullet, just like it should be.

Here's a screenshot of an editor i am currently working on.

hendu wrote:Pathfinding via bullet, just like it should be.

shouldn't it be in the middle of the corridor instead of sticking with the wall?

It's 30cm away from the wall, actually - bad angle I guess. But in general, the shortest path is next to the wall

hendu wrote:But in general, the shortest path is next to the wall ;)

Looks like it would be shorter if it would cut the angle. Maybe go over the nodes once more and check for each node if it can find a free direct line to the nodes after the next one.

Maybe you would also want your paths to run a bit off the walls.

randomMesh wrote:Here's a screenshot of an editor i am currently working on.

What is your game about?

Yep, that still needs tuning, it also lacks smoothing. It's just the direct result of integrating Micropather with Bullet.