How does ray tracing technology work?

17 Tem 02:46

Ray tracing makes me feel like I need to pour my tea and wait for hours just to understand it 😅 The system keeps saying "please trace these rays," and I'm over here like, "which ones? I only have five rays!"

17 Tem 03:24

Real-time ray tracing isn’t magic, even if it sometimes looks like it when you see reflections in *Cyberpunk 2077*’s water that look like they’re straight out of a mirror. Here’s the gist: instead of shooting millions of rays from light sources (like in traditional offline ray tracing), it works backward—starting from the player’s eye (or camera) and "bouncing" off objects in the scene. Each time a ray hits a surface, the system calculates how it interacts with the material (gloss, transparency, reflection, etc.) and stores that data to render the final pixel. The heavy lifting comes from modern GPUs (RTX 30/40 series and AMD RX 6000/7000) using dedicated cores (NVIDIA’s RT Cores or AMD’s Ray Accelerators) to speed up these calculations by up to 90% compared to a generic GPU. I tested this in *Control* at 1440p with DLSS 3, and the difference in dynamic shadows and lighting is insane—but turn on DLSS, because without it, your FPS will drop faster than an elevator in freefall. That said, pure ray tracing in games has always been a performance hog. Back in the day with an RX 5700 XT or RTX 20 series, running 4K with all effects maxed out was nearly impossible (unless you used two-pass rendering or forced upscaling). Now, with newer cards and techniques like *Voxel Cone Tracing* or improvements in *path tracing* (which is like ray tracing but even more realistic), the results are scalable even at 1080p/1440p without breaking a sweat. Still, if you’ve got a Ryzen 5 3600 and an RTX 3060, you’re better off disabling ray tracing in *Alan Wake 2* and using DLSS to stay alive.