georginikolov
georginikolov on Hacker News
WebGL 2.0 physically-based renderer featuring IBL with environment map convolution, HDR tone mapping, analytical lights, and the metallic-roughness PBR workflow. Implementation based on LearnOpenGL's PBR theory.
Posted by
georginikolov on Thursday December 18, 2025 @09:20AM
from the show-hn dept.
I always enjoyed reading video game frame graphics analysis articles and thought it would be cool to write one myself in the hopes that others find it informative and hopefully entertaining.
It covers all the steps needed to produce a single frame in my WebGPU deferred renderer demo. Additionally, it talks about the WebGPU API itself and how it differs in some ways from Metal.
you really think that? I typed it manually myself :D
hey, I turn things off dynamically if the framerate dips below 60fps for longer than 2 seconds. Some people will have them unchecked automatically (and of course have the ability to turn them back on if they really want to)
WebGPU tech demo running in modern browsers showcasing various rendering techniques like deferred rendering with 400+ dynamic lights, Hi-Z screen space reflections and cascaded shadow mapping.
Posted by
georginikolov on Thursday December 19, 2024 @12:14PM
from the gnikoloff.github.io dept.
Posted by
georginikolov on Tuesday October 15, 2024 @02:44AM
from the github.com dept.
I've put everything I've learned while developing graphics for Apple Vision with the Metal API and Compositor Services in writing. It covers foveation, vertex amplification, stereoscopic rendering, and more techniques that extend beyond this particular device.
All of the game graphics, state and logic are written in WebAssembly Text. The host environment (Javascript) is responsible for:
Game tick loop
User input
Providing characters "0123456789GAMEOVER" byte data on game startup
Blitting the pixel buffer to the display with WebGL2
The game uses 3 virtual pages of memory (64kb each) for a total of 192kb. Within those exist the pixel buffer contents, the characters data and snake positions. For more detailed breakdown you can check src/snake.wat.
The memory is shared between WASM and JS. On each game tick, the pixel buffer region of the memory is transferred to a WebGL2 texture, uploaded to the GPU and blitted to the screen.
For more info you can refer to the repo - https://github.com/gnikoloff/wasm-snake
Posted by
georginikolov on Monday March 04, 2024 @11:51AM
from the github.com dept.
Followed "Raytracing in a Weekend" books and at some pointed ported them to WebGPU.
Rays are path-traced in a compute shader, bouncing around the scene and accumulating color.
The frame renders are accumulatively added to achieve denoising and blitted to the device screen. This provides for interactive framerates in the demo.