<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>gpu on TutorialEdge.net</title><link>https://tutorialedge.net/tags/gpu/</link><description>Recent content in gpu on TutorialEdge.net</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 10:02:00 +0000</lastBuildDate><atom:link href="https://tutorialedge.net/tags/gpu/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 2 - The Render Pipeline</title><link>https://tutorialedge.net/projects/graphics-with-wgpu-in-rust/part-2-the-render-pipeline/</link><pubDate>Fri, 29 May 2026 10:02:00 +0000</pubDate><guid>https://tutorialedge.net/projects/graphics-with-wgpu-in-rust/part-2-the-render-pipeline/</guid><description>In Part 1 we opened a window. In this part, we connect that window to the GPU and draw our first frame — a solid colour fill. It&amp;rsquo;s a modest result, but it means the full rendering pipeline is working end-to-end.
##How the GPU Pipeline Works Before writing code, here&amp;rsquo;s the mental model you need.
Your CPU sends commands to the GPU. It doesn&amp;rsquo;t tell the GPU to draw individual pixels — it records a list of operations into a command encoder, then submits that list to a queue.</description></item></channel></rss>