eidolon @shaderphantom@awoo.space

feedback loop in which the image data from a render target is reinterpreted as vertex data for the next frame

the goose is loose

@flussence@nulled.red software is so incredibly bad

goose praxis

so, The Surge is okay.

@Wunkolo wb

@roxy@snouts.online for localization reasons, it might be preferable to use a real font

oh i guess that's what frame graphs are for huh. task scheduling.

i've been squidward "FUUUTUUURRRE"-ing all weekend over graphics programming shit

@hyperlink@snouts.online "almost all my games in the last 20 years have been painfully mediocre..."

@hyperlink@snouts.online why are you like this

in Vulkan, after mapping your vertex buffers to host-visible memory, you could create command buffers for each which signal fences to tell the game they're ready to draw with, and submit them on every other queue not being used for rendering. on my GPU that'd be possibly 18 parallel queues just for uploads 👀

with modern OpenGL you might be able to use mapped buffers and fence objects to manually double-buffer chunk vertex buffers, but it would heavily depend on driver support

my hypothesis was proven true: the main bottleneck of a minecraft-like is in uploading chunk vertex buffers to the GPU, not in generating the meshes themselves

the surge is only 8.5 gigabytes... how...

Minecraft 3: Warped