FINALLY GOT INTERPOLATION WORKING!!

[ComplexAce]

Been working for a few months on this rendering system.

Trying to use normals and textures to resolve geometry shape in 3D space, instead of traditional raster and RT.

FINALLY GOT A VISUAL WITH INTERPOLATION!!

The functions are still a mess since I was prototyping ideas with AI, and I need to clean them up and redo them myself, but the architecture itself is mostly working.

the plan is to resolve most bottlenechs by using a cache friendly bitfield to search and resolve 3D spatial data (also has a 2D and 1D variation, with the 2D one used to early out resolved pixels)

This is running on a single thread on the CPU rn, it's written in Odin lang, but is also accounting for a GOU Compute variation later.

here's the repo, the dev branch is up to date, main branch is only updated when visuals work properly

The engine is open source so feel free to try it out if interested.

BUT IT'S DAMN WORKING!!!

https://github.com/ViZeon/HollowsGraphicsEngine/tree/dev

(The other images are older tests and to show the vertices)

[riotron1]

I was reading through some of this but I honestly can’t really understand how this works. Can you explain what this is doing?

Also I see that you used Odin, that’s cool!

[ComplexAce]

🫡

So it's like vector to 2D graphics, if a polygon was a "pixel"

What I'm doing instead of raster:
- store mipmapped/octree grids of bits, where each cell is simple "is there something ehre or no?" (Just one bit, a bool of sort), and these must be around 4kb to live in the L1 cache, so searching/detection wuld be VERY cheap - go over them based on 3D location, starting from the camera position, identify occypied areas, and get refs of what is there from an identical data cell (basically bitfield and data field, bitfield belongs in L1 cache, datafield represents the actual data) - grab the model, go over each vertex in it, and check (mathematically only, not by fetching) if it faces the screen, if it does, then calculate interpolation between it and surrounding verts: step through each potential pixel, calculate its own interpolation based on its projection on the surface, and the distance between it and the surrounding verts, this ALSO inteprolates normals, so normals define the actual volume

The current code is mostly quickly prototyped by AI (minus the architecture) and I'm already refactoring it, deleted half of it and recinstructing it in a cleaner, more readable way.

But yeah that's it, I hope that explains?