>>107846997
I could Vibe Code that with Claude Opus in like 10 minutes tops.

>>107846997
That's neat.
However, considering the framerate, it seems like you're doing something very wrong. You should get more like 2,000 fps, not 20 fps.

>>107846997
kek I know you vibe coded this b/c I unironically just did the exact same project a couple days ago

>>107846997
very cool anon

>>107846997
in the 90s you'd get immediately hired for valve or idsoftware, now it's just ai react app slop

>>107846997
Based vibecoder

>>107847035
prob lack of culling, since there's not (supposed to have) much logic going on every frame at that point in the game.
or doing a bunch of draw calls using the same texture but binding it every time, setting the shader program every draw call, etc. but I don't know shit about graphics

>>107846997
Nice 20 FPS, faggot.

>>107847140
It's not doing draw calls for every block, it's doing meshing but it isn't greedy meshing and there isn't any frustum culling yet

>>107847178
You only need to mesh once unless a block gets removed or added.

>>107847027
>>107847036
>>107847058
Yes it is vibecoded using GPT-5 mini

It took about three days to get to this point

>>107847198
It actually is meshing once and then reusing the meshes. Idk at the moment what the performance bottleneck is but I'm going to figure it out at some point. It is rendering a 7 x 7 x 7 cube of 16 x 16 chunks so obviously there are a lot of vertices

>>107847237
>obviously there are a lot of vertices
there shouldn't be. anyway there are some great tools that will tell you exactly how much time is being spent in what function and when called from what other function, so it'll give you an idea pretty quickly about what's wrong

>>107847237
honestly good job!
3 days is not bad, and way better than most programmers could do

>>107846997
>really basic minecraft clone with two blocks
>20fps
The fuck have you done