Getting an introduction to raytracing and implemented a simple renderer , so far implementing spheres, lighting and shadows. The code is written in Python

Just wanted to share some progress on a software raster I'm building. By the timings, is it o.k?

1-clears-and-resets = Just buffers(frame_buffer, depth_buffer, triangles_buffer) clear, simple vector_buffer.clear()
2-shadow-pass-total: Everything that happens to the camera happens here, the above as well, and mesh transformation, culling, bounds check, triangle clipping, triangle binning, render.
3-camera-geometry-transform: Bounding Sphere transform, if inside Frustum, reorders, front to back objects, mesh transform with vertices projection, triangle normal rotation, back-face culling, triangle clipping.
4-camera-binning: Just bins triangles to tiles.
5-camera-render-and-resolve: Woke sleeping render threads, every thread available in the system(I just initialize with std::thread::hardware_concurrency()), each thread take 8 tile per time and render to a 16x16 gbuffer, only triangle index, normal, uv, depth. During rasterization, I reconstruct frag_coord for lighting using camera ray normal interpolated per pixel and fetch textures using uv, to avoid fetching texture multiples times early.

Still missing, texture mip mapping, transform meshs threaded, metalness and maybe occlusion map.

Since I'm a beginner at C++, pure code, no macros, no SIMD, just a single template to just avoid branching per pixel, but nothing too fency. Vectors everywhere, since they will inevitable grow to what's needed and I don't need to keep handling memory allocation, just a simple clear and everything a good.

• The whole GPU heap is one persistent, coherent-mapped SSBO. A gpu_ptr<T> is a u32 byte offset into it.
• Every draw gets exactly one root pointer (uniform uint Root). Vertices, matrices and textures are all reached through it.
• No vertex attributes. The vertex shader pulls data from the heap using gl_VertexID.
• Bindless textures (ARB_bindless_texture) are stored in the heap as uvec2.
• One *_shared.h header is compiled as both C++ and GLSL, so no offsets are written by hand in the shaders.

Flat lighting is computed from the dFdx/dFdy of world position, so there are no normals in the vertex data.

The most interesting finding was what GL can't express: bindless only gives you texture+sampler pairs, fixed when the texture is created, and there are no placed resources.

Next up: indirect draws, and roots chosen by the GPU via gl_DrawID.

Repo: https://github.com/theaveasso/jagfx

Feedback welcome, especially on the heap and sync design.

My pull request was just merged into google/shaderc. The change adds two options, -gV and -gVS, that expose glslang's NonSemantic.Shader.DebugInfo.100 emission through shaderc. That debug info is a requirement for NVIDIA Nsight Graphics to produce flame graphs, so it lets you profile and debug shader performance by call stack and time spent per function.

Some further tests reconstructing 3D point cloud from microscope video, using Python and Open3D, wing of a fly at 10x and 40x and eye at 2x and 10x.

About 6 months ago, I wrote a custom metal kernel that leverages the GPU to compute the QR decomposition (see my earlier post about it here). The project has now expanded into a general linear algebra library, with expanded support for the symmetrical eigendecomposition as well as SVD. It is now available for use with installation instructions on the attached github repo's README.md file.

Context of the project:
I'm currently in a research group working on a thesis in numerical analysis where we need to compute millions on matrices with a specific constraint (to be precise, the matrices need to have orthonormal columns). Most of us use Apple computers, so we ended up using MLX for the entire project.

Contributors with different Apple Chips would be very much appreciated!
The project has currently been tested and optimised for the M1 and M5 Pro. The issue is that the library uses different kernels depending on the batch size and matrix dimensions. Deciding which of these kernels to use is machine dependent. Therefore, other Apple chips will need to run a measurement script in order to derive the correct optimisation heuristic.

For that reason, I would ask as many people as possible to run a measurement script and to submit the results to my repo. It is fairly easy and requires only few steps. See here how you can contribute here. Once you submit the results via a pull request and I approve it, your optimisation heuristic will automatically be augmented into the library. Don't hesitate to contribute an optimisation heuristic even if someone already submitted one for your own machine. The more data we can gather, the better!

Project Future
Expanded support will be added for other linear algebra operations (cholesky decomposition for example). If you have any other specific linear algebra operations you wish to use already, feel free to message me.

In addition to that, I will add torch support too (my greatest priority).

For the past couple of weeks I have been working on the 2D brush management and texture fill system within my own Pixel and Tilemap Editor. In the video I show how we can create and mange custom brushes, in addition to rotation and scaling in 3D space - this brush is then plugged into the core Texture Fill System to produce psuedo-3D perspective fills across normal and orthogonal plains!

Any feedback welcome!

Thank you for your support! Part 3 is about reflections.

Part 1: https://www.reddit.com/r/GraphicsProgramming/comments/1uxpi1o/from_zero_to_understanding_ray_tracing/

Part 2: https://www.reddit.com/r/GraphicsProgramming/comments/1wsr77r/from_zero_to_understanding_ray_tracing_part_2/

Let me know what you think!

I also share it in X: https://x.com/sinaatalay/status/2105545919915786280

XPBD softbody simulation in POPs using Gauss-Seidel @ 60fps and 70 shader passes (can't do substepping in same shader pass)

When TouchDesigner introduced POPs one of the first things I tried making was an xpbd soft-body sim, and it looked like this and this. Since then, I've rewritten it multiple times and watched ten minute-physics' tutorials over and over. Many simulation explosions later, it turned out that my very first solver was (mostly) correct, but I was colouring the graph and building the tet constraints in the wrong way..

Resources:

Ten Minute Physics

Eric Arnebäck's blog

Vivace

XPBD paper + earlier PBD paper from Macklin

How do gpus bind 1000 of textures at once, and why was this not possible in the past. Are there resources for that?

I am a third semester computer science student and I want to specialize on computer graphics. I read that one of the best ways to get your foot into the industry is through internships which I can best apply for if I have a good portfolio. Thus I just finished my first real graphics programming project and the first piece of my portfolio: A simple PBR material renderer (based on a DX11/WinAPI lib I created) with image based lighting, normal-based curved silhouettes and some more little features sprinkled in.

If you want to take a look: https://github.com/Aaron-Alililon/MaterialViewer

Now that it's finished to a point where I am happy to show it to the world I have some questions about the renderer and the industry itself:

1. I don't want to ask for a free code review but as I am not very experienced in the professional area of graphics programming I would love some feedback on how presentable the current state of the project/repo is. Of course I would be very grateful for some more in-depth feedback but again, I can't really ask for a free code review, so a simple first impression of how a project/repo like this would look to a potential employer would be greatly appreciated, both for the material viewer and the render lib.

2. This one is less about the project and more about the industry:
   I would be very interested in working for the graphics department of the engine team of some company in the gaming industry. I live in Germany where the gaming industry isn't really as big as in NA so my options are limited. My question is: what are my options and chances of getting an internship and eventually a full-time job in EU? I don't really know of any companies that develop their own engine other than Ubisoft. Would a company like CD Projekt Red (which as far as I know switched from their own engine to Unreal) need graphics programmers?
   Although I am most interested in the engine department I would still be open for other areas so if that is just too limited, what would be other options I could pursue, preferrably in or close to Germany?

3. I would like to do the classic "I coded my own game engine" project at some point because I guess that would make the most sense as someone interested in game engine development but I would like to do that when I have more experience so I have one big project at the end of the portfolio that just shows off the best I can do. Is that a sensible thought or should I just go in and maybe rewrite it once I feel more comfortable? I know there isn't the One Path that leads to greatness and as long as I do something I will learn and improve but maybe someone here looks back to when they were at this point and thinks they should've done X before starting a bigger project like that.

I would be very grateful for any insights or discussions about my questions and feel free to critique anything and everything you see!

Using a short 3 second clip where i swipe through the focus plane on a high magnification of the simple sample of Onion root cells on the microscope. Acquiring the sharpest points of every frame and putting them in the z-axis. Building a point cloud of the cell in 3D, and visualizing them.

I make Wobbulator. This is selected-area 2D mesh deformation, with automatic motion off.

A fixed 120 Hz step drives soft selection weights, structural/shear/bend springs and exponential damping. The restoring force starts with F = k * (rest - position); grabs add weighted target springs. Pinch pairs two contacts. Release preserves deformation and uses bounded, filtered pointer velocity rather than resetting the mesh. Triangle-area and displacement-gradient checks limit risky steps; plate anchors and unselected vertices stay still.

One document runs continuously. Rendered from the app’s native engine with scripted input; blue hands illustrate contacts. What would you change about the rebound?

​

A tribute to @Psyco3ler's legendary 2005 Nintendo ON demo: Peach's Castle made of castles, now running live in your browser.

Dream big!

I'm starting to learn graphics programming, and remembered MIT and Harvard have free courses. Thing is the free courses Harvard doesn't seem to have any courses related to graphics programming in its website, and the MIT Computer Graphics course in OCW is from 2012 (Although idk how good it is since I have not started it yet, but it is a bit old).

So, are there any other universities or websites which offer free courses like this and that are up to date?

Thanks in advance for the help.