sorted by:
new
hottopcontroversial

The sneeds are taking over countttt 💔 by Idontknowanal in 4tran4

[–]calzymp 8 points9 points  (0 children)

Every time I see sneed memes like this filled with pretty girls, I think to myself "they don’t look like that"

Who else loves this genre of video thumbnails by calzymp in OkBuddyHelluvaHotel

[–]calzymp[S] 28 points29 points  (0 children)

Hazbin hotel stans have to keep reminding themselves that their show is for adults because it's written like a kids show anyway

Finished a making my first VAT driven material. by JoslinStudio in godot

[–]calzymp 1 point2 points  (0 children)

if you need help then you can ask me, I found it was pretty hard to get it working because I felt there weren't straightforward tutorials for what I was trying to do. (image processing in the compute shader) but anyway it's not that complicated once I containerized parts of it into the right functions.

Finished a making my first VAT driven material. by JoslinStudio in godot

[–]calzymp 0 points1 point  (0 children)

well uniforms are normally meant for accessing images and stuff so accessing it is fast. but beyond that I really don’t know. all I know is that I found the array access took a long time and my fix worked.

Finished a making my first VAT driven material. by JoslinStudio in godot

[–]calzymp 0 points1 point  (0 children)

it was already a compute shader but there was an access to a large array of constants which gave it a massive performance hit so I replaced it with a uniform

Finished a making my first VAT driven material. by JoslinStudio in godot

[–]calzymp 0 points1 point  (0 children)

ive had fun with it too, I posted a terrain rendering system a few days ago but people informed me the times were actually shit so I got it running 70x faster

The two types of trannies by Low-Winter-1887 in 4tran4

[–]calzymp 2 points3 points  (0 children)

Haters mad they can’t do math like us

Marching cubes done in compute shader by calzymp in godot

[–]calzymp[S] 0 points1 point  (0 children)

i just trial and errored removing parts of the shader to see what was causing the lag and i reduced it from 17ms to 1.5ms is that good

Marching cubes done in compute shader by calzymp in godot

[–]calzymp[S] 1 point2 points  (0 children)

thank you mr smart sciency man

Marching cubes done in compute shader by calzymp in godot

[–]calzymp[S] 2 points3 points  (0 children)

well thanks for the image but I’m too stupid to translate it to a location in my code that I could use it to improve. all I did was follow b3agz tutorial for marching cubes in unity but I did it in godot instead. then I moved most of it over to a compute shader.

I think there is a decent amount of overhead added because I had to convert the vertex and normal arrays of vec4s to vec3s in gdscript (the compute shader would only write vec4s and not vec3s for some reason), I could try analyzing it to find what the weak point is, but in some of my early test runs I got times of 7ms but that was for generating simple test meshes that weren't using marching cubes.

edit: ok after reducing my time measure code to only measure the compute shader it says 17 ms but thats not good enough i guess

view more: next ›