Posts about the helios C++23 game framework - architecture, implementation, and technical deep dives
View All Tags
helios now has core vector operations: subtraction, dot product, cross product. The lookAt function constructs view matrices from eye, target, and up vectors, following standard methodology.
Following up on my article on Model Matrices, I've written about matrix composition in the context of Model and Rotation matrices.
translate, rotate, scale - done. They now live in helios.math.transform.
I standardized on post-multiplication (M' = M * T) to stay consistent with glm. Transformations are applied in local space.
While porting the rotation matrices for helios.math.transform, I took a detour to understand the underlying linear algebra - I wanted to move beyond treating the rotational part of the model matrix as a black box.
Over the weekend, I focused on refactoring mat4 and vec3. Additionally, I've made some adjustments to my toolset.
import {SocialLinks} from "../../src/components/SocialLinks";
For a game engine, the first step isn’t rendering a scene or simulating complex physics - it’s laying the foundational bricks. This weekend, I eased dove headfirst into that foundation for my personal C++ engine project, Helios, and it was a fantastic journey through the nuances of modern C++ design.
My background is in the web world - I've spent years wrangling Java, JavaScript (and countless frameworks based on it), PHP (from Zend to Laravel over Symfony and self-written solution), and the closest I ever got to the metal was writing C, of which I thought it would give me a head start for a game engine project. In a way, it did: I wasn't scared of pointers. But it also gave me a false sense of security.
Hi everyone!
I've been working in software development for a long time now - mostly frontend architecture, large-scale web applications, that kind of thing. I care a lot about software craftsmanship and building systems that actually make sense.
But then Day 15 of Advent of Code 2024 happened.