I've just finished implementing screen spaced grass effect in my octree renderer.
It works only with materials tagged with "terrain" and it generates and distributes grass blades on the fly using screen spaced 4x4 Bayer Matrix as threshold, for now a hard-coded density parameter, global wind vector for animated sway effect and triangles' UV for screen placement and 1/z information for perspective correction.
What do you think?
Added full 8-band terrain texture blending today.
The system uses a painted blend map (0-255 values) to control mixing between 8 different texture bands on top of the existing heightmap terrain.
Works nicely with the in-engine CyberEdit (same 320x240 Mode X viewport setup).
We paint the blend map in GIMP, use on world quads, then bake it for octree sidecar file.
Screenshots:
Multi-view editor with brush and quad mode:
Terrain Blend Bands window showing the 8 layers + ranges combined with material window:
In-game 3D view with the new blended terrain:
Still targets real 486+ hardware (and the Win64 port of course :) ).
Feels like a big step for terrain editing while keeping it all under intended hardware constraints.
Let me know what you think!
A new version of CyberVGA released on itch!
This version has:
Static octree based renderer
A separate 64-bit Windows port
You can use editor, save the world you created and see in action using VIEWER module.
I really like the idea of putting a subtitle for CyberVGA.
“Engine Of The Past”
What do you think?
Just locked in the full mocap workflow for CyberVGA vertex key animation.
Raw capture synced side-by-side against the in-engine playback — timing, vertex deltas, and playback precision all holding under the fixed-point pipeline.
This slots straight into the existing entity/component system and Play Mode testing. No floating point. No modern crutches. Pure C89 + NASM constraints, delivered.
#gamedev #indiedev #retrodev #DOS #vertexanimation #engineprogramming
