Currently, the development focus for engine is implementing the debug cube. It is meant as a safe fallback for any erronious setpiece generation. If there is a fault in generating mesh, loading asset data, shader generation or program compilation, it all should revert to the cube.
One of the larger changes to the project has been an entire switch performed from C++ to Zig. This was not a choice made lightly, or for little gain.
Not quite a year later. Many things have shifted, and of that which has remained I see with a new perspective.
This is an exceptionally busy time, it seems. Been attempting to find some amount of time to work on development. Unfortunately a trip has been planned that will most likely consume the next two weeks. A small amount of progress has been made in having the chunk keep the VBO data. When an alteration occurs it should now update the VBO data directly, modify what has been altered, and pump the update to the GPU. “Should” is the key word here, as it currently does not appear to function as it should. It is likely an issue with the -512,+512 worldspace coordinates being confused with the 0-1024(5) coordinates needed for calculating position in a data array.
Emulating human communication in a digital medium is… interesting. We are built and bred to identify threats, including from members of our own species. We immediately recognize and detect certain body motions and facial expressions as being on a sliding scale of dangerous to not. Our linguistic capabilities also follow something of that trend it seems, with certain phrases clearly being those of a threat, even if not written so. Dialogue in video games is an interesting problem, as it must be meaningful yet dynamic. Ideally, the player must have every one of their own thoughts repesented to an accurate enough degree that they can be themselves, or adequately be the character they wish to represent.