From e7d32625befb85e5b40380de20c62172e7275c5e Mon Sep 17 00:00:00 2001 From: jantari Date: Fri, 29 Jan 2021 19:06:36 +0100 Subject: [PATCH] Fix pixel shader typo in README (#8949) Fixes a typo in the README regarding pixel shaders. --- samples/PixelShaders/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/PixelShaders/README.md b/samples/PixelShaders/README.md index 8497356ba..72fe9e80c 100644 --- a/samples/PixelShaders/README.md +++ b/samples/PixelShaders/README.md @@ -58,7 +58,7 @@ If your shader fails to compile, the Terminal will display a warning dialog and ## HLSL -The language we use to write pixel shaders is called `HLSL`. It a `C`-like language, with some restrictions.You can't allocate memory, use pointers or recursion. +The language we use to write pixel shaders is called `HLSL`. It's a `C`-like language, with some restrictions. You can't allocate memory, use pointers or recursion. What you get access to is computing power in the teraflop range on decently recent GPUs. This means writing real-time raytracers or other cool effects are in the realm of possibility. [shadertoy](https://shadertoy.com/) is a great site that show case what's possible with pixel shaders (albeit in `GLSL`). For example this [menger sponge](https://www.shadertoy.com/view/4scXzn). Converting from `GLSL` to `HLSL` isn't overly hard once you gotten the hang of it.