Learning modern OpenGL. The first two quads I rendered on screen.
Five more quads (1 ground, 4 walls) added to scene. Added textures.
Loading a weird heptagon shape from .obj file, and more random walls.
Spheres, some debug UI with various edit modes (translate, rotate, etc.) Editor is entirely hotkey based.
I think this was Blinn-Phong lighting with specular. IMO, one of the best looking screenshots during the first year of development.
Translate widget, and a few additional properties in the read-only debug UI.
Hilarious rendering bug. Probably just some misalignment of vertex attribute pointers.
First time I added buttons you could actually click to the UI. I made some nice icons, but they didn't do anything. At one point the first button made a "ding" sound when you clicked it.
The first time I played around with colored lights. Three basic point lights; no shadows.
The first scene with working point light shadows. Dynamic shadows via shadow mapping to a cubemap texture.
A slightly more complex scene, with multiple colored point lights, a single directional sun light (no directional shadows it looks like), textures and point light shadows.
A single large level mesh loaded from .obj. First decent screenshot from the new Talaria engine, which is a from scratch endeavor. Inspiration from RicoTech but very little code sharing. Weird bar chart thing on the top; was going to use it to display FPS but it was never important enough. Top left is a second viewport with a different camera angle.
An incorrect bounding sphere, and incorrect normals (face normals) on sphere making it look faceted. Top left viewport also a weird top-down camera with incorrect aspect ratio.
Better bounding spheres; some basic rigid body properties (the small yellow spheres are debug viz for center of mass, and the small green spheres are debug viz for point of contact with the floor). The floor is represented as an infinite plane, which isn't a great idea in a real rigid body physics simulation. Top left viewport is a correctly scaled minimap or sorts.
I think this was the first decent-ish screenshot of the initial PBR material shader. Still looks quite awful at this point.
Hard edged point light shadows! Adds a ton of depth to the scene. The lighting in this screenshot is a noticeable improvement from the previous one.
Point light shadowmap (cubemap) debug viz in upper left corner. Demonstrating hard-edged shadows (comparison shot; see below).
Taken immediately after the previous screenshot, but with percentage-close filtering (PCF) enabled. First time I ever rendered smooth shadows.
First pass at a better UI framework. Four buttons, each of which has a 16 button child grid that pops out when the respectively menu button is selected (outlined in yellow).
Top left is a first pass at a very rough text edit field. Weird test material that has metallic letters on it. Looks cool.
The return of the debug text UI, but with an, albeit very primitive, menu. A kinda funky outline shader effect for the currently selected object (the blue sphere with yellow outline).
Editor UI evolving slightly. The tiny boxes are the top are actually the in-game HUD and each one represents a single bullet in the imaginary gun. You can also see a slightly better cubemap debug viz when a light is the currently selected object.
Editor UI has a background and some more colors. The green rectangles are button, some of which are toggle buttons (e.g. V-Sync). Different random test materials. This is the first normal mapped material screenshot. The debug text in the top right has also evolved to show slightly more information.
Top right UI evolved slightly more. Cameras now have "debug channels" you can enable which alters the shader output to display useful debug info like only vertex normals, normal maps, metallic values, etc.
Editor UI significantly improved in this screenshot. Started to actually be a real tool.
Editor even more complex here. Admittedly, I've let the layout slip a bit. It was more important to have access to the rigid body properties than it was for it to be perfectly aligned.
A new level mesh I made in Blender, inspired by a screenshot of a puzzle game I saw on Twitter. Shadows, and a light blue glClearColor to represent a sky.
Temporary editor and debuz viz for testing ray casting (ray vs. obb) and point of contact calculations.
Same as above, but for ray vs. quad.
More amusing bugs. Vertex attributes messed up again, rainbow UI.
Debugging and fine-tuning hitboxes for translate widget.
Proper skybox. Tinted the sun lamp blue to give a more moody feel. The little box and arrow above the gray sphere is a debug viz for the player camera (which folows the ball around). The scene is taken from the viewpoint of a free-flying debug camera.
OCD code formatting. Inspired by FMOD headers.
Translate widget video (I don't know if MP4s work in Markdown, visit link if it doesn't).
https://i.imgur.com/3iORSwU.mp4
Rigid body simulation of sphere vs. three OBBs and another sphere (the two columns, the floor, and the other ball).
Same as above but with physics engine debug viz enabled. Tight-fitting spheres and OBBs are narrowphase, loose-fitting boxes are broadphase AABBs. Broadphase is still O(n^2) brute force, but using AABBs to allow for a future AABB tree optimization.
"Dude" model and button model. Can't remember if .obj or .gltf at this point.
First "animation", in quotes because I'm manually setting the weight via a slider.
First morph weight "animation". Also manually animated via a slider (engine doesn't know how to do playback).
Another editor UI screenshot. This time with a texture selection view, inside of a scrolling panel and with a tooltip. All a custom UI lib.
