<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compute on Jan Kelemen - Personal site</title><link>https://jk.rubberdax.xyz/tags/compute/</link><description>Recent content in Compute on Jan Kelemen - Personal site</description><generator>Hugo</generator><language>en</language><copyright>© [Jan Kelemen](https://www.rubberdax.xyz)</copyright><lastBuildDate>Sun, 25 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://jk.rubberdax.xyz/tags/compute/index.xml" rel="self" type="application/rss+xml"/><item><title>I See Spheres Now</title><link>https://jk.rubberdax.xyz/post/2024-08-25-i-see-spheres-now/</link><pubDate>Sun, 25 Aug 2024 00:00:00 +0000</pubDate><guid>https://jk.rubberdax.xyz/post/2024-08-25-i-see-spheres-now/</guid><description>&lt;p&gt;Since I had never actually written a raytracer, I wanted to learn about this topic by following along with the popular
&lt;a href="https://raytracing.github.io/books/RayTracingInOneWeekend.html"&gt;Ray Tracing in One Weekend&lt;/a&gt; book.
The title doesn&amp;rsquo;t lie, my first CPU raytracer did take only one weekend.&lt;/p&gt;
&lt;p&gt;Afterward, I tried making the same raytracer using a compute shader and with the possibility to move around the scene in real time.
Results are in the video below, link to the source code: &lt;a href="https://github.com/jan-kelemen/graphics-demos/tree/master/beam"&gt;jan-kelemen/beam&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>