question for the fedi hivemind:
currently i'm following the glium tutorial, after part 4 i tried to seperate the libary code from the actual game code.
It somewhat works right now (meaning the window with a blue background opens) but the triangle doesnt render and opengl panics (GL_INVALID_OPERATION in glUniformMatrix(program not linked))
What have i done wrong?
thanks in advance!
here's the code:
Hey #OpenGL and #graphics people, are there any graphics profiling/instrumentation/frame debugger solutions which work with OpenGL on modern non-Windows systems? Something à la #RenderDoc but that works on #Wayland or Apple Silicon Macs. To do frame debugging right now I have to log out of my Wayland session on my #Linux desktop and log in to #X11, which is uber-broken on my mixed DPI fractional scaling multi monitor setup... #programming #graphicsprogramming #macdev
Jet lag! Not so great for sleep. But certainly great for getting a few last-minute features into my vacation software rasterizer project. Now it has (hacky) specular lighting and voxel shadows.
It was refreshing to have some time and energy for hobby coding. It is pretty much complete I guess. Back my normal busy schedule starting today.
You ever go down a soft body physics academic papers rabbit hole?
In standard C, without architecutre-dependent intrinsics, what is the most performant way of unpacking a 32-bit 8-bpp RGBA value into a 64-bit 16-bpp RGBA value? I need something that will CLEARLY compile into a SIMD instruction, but in standard C.
Question for Vulkan people: Is it possible to usefully use vkCmdDrawMeshTasksIndirectEXT? gl_InstanceIndex seemingly isn't available in task or mesh shaders so I can't figure out how the shaders are meant to know which instances they belong to
Am I missing something here?
#vulkan #graphics #graphicsprogramming #3dgraphics #gpu
I published the source for my simple software rasterizer written in Rust here: https://github.com/mdesmedt/swraster-viewer
It's far from perfect, and I haven't even done any performance analysis on it, but I'm happy with releasing it in this initial state. Maybe I'll get to adding texturing support to it at some point as that would be fun.
Just added a new combined view mode that combines texture details with lighting info.
This makes inspecting surface interaction way more intuitive. 
Finally got around to post an new article on my blog today! Wrote about the rasterizer i'm currently tinkering with in rust, as well as the algorithm I've used (barycentric coordinates), as well as some optimizations that can be used early on so it dosn't run at 1 FPS for a couple of triangles x3
https://blog.lapyst.dev/posts/12-software-rasterizer-in-rust---part-1
Lol, I knew that debug vs release builds have some performance impact but never thought THAT much. So aparently my rust rasterizer can render 250 moving triangles at ~7 FPS in debug builts but a whoping 40 FPS (!!) in release builds. That's just: WTF? x3
Had the itch to get back to basics with graphics this week so I wrote a software rasterizer in Rust. The rasterizer SIMD approach is based on @rygorous 's excellent tutorial series here: https://fgiesen.wordpress.com/2013/02/17/optimizing-sw-occlusion-culling-index/
Plenty of work to do like some kind of multithreading scheme and perhaps even textures. But it's always satisfying to see shaded triangles. I'll share the code at some point if I clean it up 
Just rendered my first Vulkan triangle in raw x86-64 Assembly.
No C, no C++, no Rust.
Pure MASM64. Pure pain. Pure control.
This is what it means to go full bare metal.
More to come. 
https://github.com/IbrahimHindawi/masm64-vulkan
Currently working on a little #rasterizer after watching the fantastic video from Sebastian Lague on yt.
Decided to write mine in #rust with some other techniques than the ones in the video, like using Barycentric Coordinates and calculating an AABB of an tri before iterating over the pixels. The video below showcases the rasterizer trying to process 250 random triangles. (Windowing and the FPS counter are done with #raylib)
Some artifacts here and there due to Z-ordering issues, but I hope to fix this soon.
End goal is to write it in such a way that I even might someday can use the rasterizer inside an custom rust #kernel / #os for basic 3d graphics, ofc to run
#doom on it!!
Vulkan and Win32 APIs ready.
Time to mov some data
#Vulkan #Assembly #GameDev #EngineDev #Debugging #Handmade #LowLevel #masm64 #gametech #graphicsprogramming #vulkanengine
Just added Vulkan validation layers and debug callbacks to my assembly-based engine! Catching issues before they crash—because debugging raw x64 is fun, but not that fun.
#Vulkan #Assembly #GameDev #EngineDev #Debugging #Handmade #LowLevel #masm64 #gametech #graphicsprogramming #vulkanengine
500 lines of pure x64 assembly.
Just to create a Vulkan instance.
No helpers. No C. No safety nets. Just raw MASM64 and the Vulkan headers.
This is what low-level graphics looks like when you go all the way down.
Next up: surface and device creation.
I've set up a Github repository to build Google ANGLE binaries for Mac (Metal), iOS (Metal) and Windows (D3D11) automatically.
These are going to be used with my engine Ceramic (using GLES3 for rendering), but other engine or game developers might be interested too 
Is it possible to make a bullet hell on a fragment shader?
Me after realizing why my depth write wasn't working:
(Yes, I forgot to bind a depth attachment to the frame buffer)
#
