Merge pull request #226 from stride3d/master

Initiating deployment of latest website updates to staging
stride3d · Nov 16, 2023 · a17c8ec · a17c8ec
2 parents 3e9067f + 79a7c6f
commit a17c8ec
Show file tree

Hide file tree

Showing 8 changed files with 190 additions and 82 deletions.
diff --git a/Stride.Web.csproj b/Stride.Web.csproj
@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk.Web">
 
     <PropertyGroup>
-        <TargetFramework>net7.0</TargetFramework>
+        <TargetFramework>net8.0</TargetFramework>
         <Nullable>enable</Nullable>
         <ImplicitUsings>enable</ImplicitUsings>
         <EnableDefaultContentItems>false</EnableDefaultContentItems>

diff --git a/_data/site.json b/_data/site.json
@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0.22",
+  "version": "2.0.0.23",
   "engine": "Eleventy 2.0",
   "title": "Stride Game Engine",
   "description": "C# Stride Game Engine is a powerful and versatile game development engine that is based on the C# programming language",
@@ -9,9 +9,9 @@
   "alert-banner": false,
   "docs-search": true,
   "google-analytics": true,
-  "download-version": "4.1",
-  "csharp-version": "C# 10",
-  "dotnet-version": ".NET 6",
+  "download-version": "4.2",
+  "csharp-version": "C# 12",
+  "dotnet-version": ".NET 8",
   "url": "https://www.stride3d.net",
   "twitter-username": "stridedotnet",
   "google-analytics-id": "G-Y9CVGC9YV1",

diff --git a/_drafts/2023-10-10-announcing-stride-4-2-in-dotnet-8.md b/_drafts/2023-10-10-announcing-stride-4-2-in-dotnet-8.md
diff --git a/download.html b/download.html
@@ -57,7 +57,7 @@ <h2 class="h1 mb-3">Frequently asked questions</h2>
                     %}
 
                     {% capture body %}
-                    <p>See the <a href="/features/">Stride features page</a>, the <a href="{{ site.links.docs-manual-url }}" target="_blank" rel="noopener">Stride documentation</a>, the <a href="/blog/">Stride blog</a>, and the <a href="{{ site.links.docs-release-notes-url }}" target="_blank" rel="noopener">Stride release notes</a>. If you can't find what you're looking for, ask on the <a href="{{ site.links.github-discussions-url }}" target="_blank" rel="noopener">Stride Github discussions</a>.</p>
+                    <p>See the <a href="/features/">Stride features page</a>, the <a href="{{ site.links.docs-manual-url }}" target="_blank" rel="noopener">Stride documentation</a>, the <a href="/blog/">Stride blog</a>, and the <a href="{{ site.links.docs-release-notes-url }}" target="_blank" rel="noopener">Stride release notes</a>. If you can't find what you're looking for, ask on the <a href="{{ site.links.github-discussions-url }}" target="_blank" rel="noopener">Stride GitHub discussions</a>.</p>
                     {% endcapture %}
                     {% include accordion-item-faq.html id:"question-features"
                     title:"Where can I learn about the Stride features?"

diff --git a/faq.html b/faq.html
@@ -31,7 +31,7 @@ <h2 class="h1 mb-3">General</h2>
                         %}
 
                         {% capture body %}
-                        <p>You can find information about Stride features on the <a href="/features/" target="_self">Stride features page</a>, in the <a href="{{ site.links.docs-manual-url }}" target="_self">Stride documentation</a>, on the <a href="/blog/" target="_self">Stride blog</a>, and in the <a href="{{ site.links.docs-release-notes-url }}" target="_self">Stride release notes</a>. If you can't find what you're looking for, ask us on the <a href="{{ site.links.github-discussions-url }}" target="_self">Stride Github Discussions</a>.</p>
+                        <p>You can find information about Stride features on the <a href="/features/" target="_self">Stride features page</a>, in the <a href="{{ site.links.docs-manual-url }}" target="_self">Stride documentation</a>, on the <a href="/blog/" target="_self">Stride blog</a>, and in the <a href="{{ site.links.docs-release-notes-url }}" target="_self">Stride release notes</a>. If you can't find what you're looking for, ask us on the <a href="{{ site.links.github-discussions-url }}" target="_self">Stride GitHub Discussions</a>.</p>
                         {% endcapture %}
                         {% include accordion-item-faq.html id:"question-what-features"
                         title:"What features does Stride support?"

diff --git a/posts/2022-02-16-community-meeting-february-2022.md b/posts/2022-02-16-community-meeting-february-2022.md
@@ -27,27 +27,27 @@ With a budget of **$4,220.48 USD** at the moment of the community meeting happen
 
 ## Funding for bug bounties
 * Fullscreen Vulkan support
-    * [Github ticket](https://github.com/stride3d/stride/issues/455)
+    * [GitHub ticket](https://github.com/stride3d/stride/issues/455)
     * Bounty: $200,- USD
     * AggrorJorn will provide the texts for the bounty and once approved by other contributors/developers in the team, this will be updated on the Open Collective project for [Bug bounties](https://opencollective.com/stride3d/projects/bug-bounties).
 * UI slowness bug
-    * [Github ticket](https://github.com/stride3d/stride/issues/455)
+    * [GitHub ticket](https://github.com/stride3d/stride/issues/455)
     * A smaller $50,- USD bounty for more research on this bug. If it can be pinpointed what exactly is causing this, we can also estimate better whether it is worth spending more money on it.
     * Depending on the outcome we might skip this bug and spend time researching/implementing a replacement UI.
     * AggrorJorn will provide the texts for the bounty and once approved by other contributors/developers in the team, this will be updated on the Open Collective project for [Bug bounties](https://opencollective.com/stride3d/projects/bug-bounties)
 
 ## Funding for features
 * Linux runtime support
-    * [Github ticket](https://github.com/stride3d/stride/discussions/1202)
+    * [GitHub ticket](https://github.com/stride3d/stride/discussions/1202)
     * Requires mores fleshed out details and deliverables   
     * Once that is done, we can decide on funding
         * Either fixed amount or use xx,xx amount per hour with a certain limit.
     * New Open collective project [Linux runtime](https://opencollective.com/stride3d/projects/linux-runtime-support)
 * Decal support
-    * [Github discussion](https://github.com/stride3d/stride/issues/24) requires more deliverables
+    * [GitHub discussion](https://github.com/stride3d/stride/issues/24) requires more deliverables
     * New Open collective project [Decals]( https://opencollective.com/stride3d/projects/decals) added and will be updated once deliverables are clear:]
 * Morphing target animation support
-    * [Github discussion](https://github.com/stride3d/stride/issues/339) requires more deliverables
+    * [GitHub discussion](https://github.com/stride3d/stride/issues/339) requires more deliverables
     * New Open collective project [Morhping Target](https://opencollective.com/stride3d/projects/morph-targets) added and will be updated once deliverables are clear:
 * Embed stride into UI frameworks
     * There already is a [work in progress PR](https://github.com/stride3d/stride/pull/1315) that allows developers to specify a custom render context.

diff --git a/posts/2023-11-10-investigating-spirv-for-the-shader-system.md b/posts/2023-11-10-investigating-spirv-for-the-shader-system.md
@@ -1,13 +1,12 @@
 ---
-title: "Investigating spirv for the shader system - Part 1"
+title: "Investigating SPIR-V for the shader system - Part 1"
 author: youness
 popular: false
 image: /images/spir.png
 tags: ['.NET', 'Shaders']
 ---
 
-In this first part of a new series of blog posts, we will learn more about Stride's shader system, its limitations and how to make it better thanks to very useful shader language called spirv!
-This will be the first step in implementing a new and better shader system.
+In this first part of a new series of blog posts, we will learn more about Stride's shader system, its limitations and how to make it better thanks to a very useful shader language called SPIR-V. This will be the first step in implementing a new and better shader system.
 
 ---
 
@@ -17,12 +16,11 @@ Table of Contents:
 
 The Stride engine has a powerful shader system, helping users build very complex shaders thanks to its language features like composition and inheritance, and its C# integration through the very powerful material system.
 
-## What are shaders ?
+## What are shaders?
 
-Simply put, they are typically snippets of codes that are run on the GPU, moslty written in C-like languages like GLSL and HLSL.
+Simply put, they are typically snippets of code that are run on the GPU, mostly written in C-like languages like GLSL and HLSL.
 
-When a game has to render on the screen, it starts by preparing the data on the GPU and then sends shaders with commands. The GPU then executes those commands and if everything goes well, the game ends with a lovely picture drawn on the screen !
-This single call of a GPU is called a `draw call`.
+When a game has to render on the screen, it starts by preparing the data on the GPU and then sends shaders with commands. The GPU then executes those commands and if everything goes well, the game ends with a lovely picture drawn on the screen. This single call of a GPU is called a `draw call`.
 
 ![shader overview](/images/blog/2023-11/shaders-explanation.png)
 
@@ -38,11 +36,11 @@ In game engines, objects being drawn the same ways are grouped into `materials`.
 
 Having many different materials implies creating many shader source code, and depending if you use [forward or deferred shading](https://learnopengl.com/Advanced-Lighting/Deferred-Shading), you might need to reuse code from one file to another leading to lots of duplicate code 👩‍💻👨‍💻.
 
-To solve this problem, all game engines have developped shader systems that help create permutation of shader code depending the material you're using. It helps re-use code you've already written, which speeds up development gives you the power to organize your code in more manageable ways!
+To solve this problem, all game engines have developed shader systems that help create permutations of shader code depending on the material you're using. It helps reuse code you've already written, which speeds up development and gives you the power to organize your code in more manageable ways.
 
 A good example of that are [shader graphs from Unity](https://unity.com/features/shader-graph) or [the material editor in Unreal](https://docs.unrealengine.com/5.0/en-US/unreal-engine-material-editor-ui/), whenever you add a block/function to the graph, it reuses shader code already written, to create a new permutation.
 
-## How does it work in Stride ?
+## How does it work in Stride?
 
 Stride has its own shader language called SDSL which stands for **S**tri**D**e **S**hader **L**anguage.
 
@@ -52,17 +50,15 @@ SDSL uses a very smart system of composition and inheritance, similar to object
 
 To create permutations you need to be aware of the many limitations you will face while writing code for GPU.
 
-
 ### GPUs are all different
 
 As obvious as it sounds, it needs to be reminded. Whenever you write code for your GPU you have to be aware that it will not work for all other GPUs.
 
-10 years ago, two languages were the most used for writing shader code : HLSL and GLSL.
-In the case of OpenGL, GPU vendors would provide you with their own GLSL compilers to work for their GPUs through different drivers. A valid code for one compiler would be a syntax error for another. It was a big mess 💩, but a manageable one!
+10 years ago, two languages were the most used for writing shader code: HLSL and GLSL. In the case of OpenGL, GPU vendors would provide you with their own GLSL compilers to work for their GPUs through different drivers. A valid code for one compiler would be a syntax error for another. It was a big mess 💩, but a manageable one!
 
 Stride was created during this period and it was designed to run on a wide variety of devices 🎮 🕹️ 💻 🖥️.
 
-The solution chosen for creating code permutations that could work on many different machine was transpilation. Text would be parsed in abstract syntax trees and the text would be translated from one language to another by manipulating those trees. [To have a better idea of how abstract syntax tree work, this playlist of videos will definitely help !](https://www.youtube.com/watch?v=cxNlb2GTKIc&list=PLTd6ceoshpreZuklA7RBMubSmhE0OHWh_&pp=iAQB)
+The solution chosen for creating code permutations that could work on many different machine was transpilation. Text would be parsed in abstract syntax trees and the text would be translated from one language to another by manipulating those trees. [To have a better idea of how abstract syntax tree work, this playlist of videos will definitely help](https://www.youtube.com/watch?v=cxNlb2GTKIc&list=PLTd6ceoshpreZuklA7RBMubSmhE0OHWh_&pp=iAQB).
 
 ### Drivers are not all the same
 
@@ -71,42 +67,94 @@ Drivers can be seen as a front-end API to use the GPU. They have different parad
 Here's a table of which language is supported by which machine depending on the driver used. I chose the most used machines for gaming.
 
 Note that some APIs are tied to the machine you're developing for, adding more complexity to the shader system, needing to handle GPUs that have very specific features. Vulkan and OpenGL can be used on Mac and iOS but OpenGL is deprecated and Vulkan run on MoltenVK, a Vulkan implementation on top of Metal.
-<br/>
-
-|                 |   Direct3D   | Vulkan    | OpenGL | Metal | PSGL | NVN |
-|-----------------|--------------|-----------|--------|-------|------|-----|
-| Windows/XBox    |     HLSL     | HLSL/GLSL | GLSL   |       |      |     |
-| Linux           |              | HLSL/GLSL | GLSL   |       |      |     |
-| Mac/iOS         |              | HLSL/GLSL | GLSL   |  MSL  |      |     |
-| Android         |              | HLSL/GLSL | GLSL   |       |      |     |
-| Playstation 4/5 |              |           |        |       | PSSL |     |
-| Nintendo Switch |              | HLSL/GLSL | GLSL   |       |      |  ?  |
 
-<br/>
-<br/>
+<table class="table table-striped table-sm">
+  <thead>
+  <tr>
+    <th></th>
+    <th>Direct3D</th>
+    <th>Vulkan</th>
+    <th>OpenGL</th>
+    <th>Metal</th>
+    <th>PSGL</th>
+    <th>NVN</th>
+  </tr></thead>
+  <tr>
+    <td>Windows/XBox</td>
+    <td>HLSL</td>
+    <td>HLSL/GLSL</td>
+    <td>GLSL</td>
+    <td></td>
+    <td></td>
+    <td></td>
+  </tr>
+  <tr>
+    <td>Linux</td>
+    <td></td>
+    <td>HLSL/GLSL</td>
+    <td>GLSL</td>
+    <td></td>
+    <td></td>
+    <td></td>
+  </tr>
+  <tr>
+    <td>Mac/iOS</td>
+    <td></td>
+    <td>HLSL/GLSL</td>
+    <td>GLSL</td>
+    <td>MSL</td>
+    <td></td>
+    <td></td>
+  </tr>
+  <tr>
+    <td>Android</td>
+    <td></td>
+    <td>HLSL/GLSL</td>
+    <td>GLSL</td>
+    <td></td>
+    <td></td>
+    <td></td>
+  </tr>
+  <tr>
+    <td>Playstation 4/5</td>
+    <td></td>
+    <td></td>
+    <td></td>
+    <td></td>
+    <td>PSSL</td>
+    <td></td>
+  </tr>
+  <tr>
+    <td>Nintendo Switch</td>
+    <td></td>
+    <td>HLSL/GLSL</td>
+    <td>GLSL</td>
+    <td></td>
+    <td></td>
+    <td>?</td>
+  </tr>
+</table>
 
 ### Performance Cost
 
 Managed languages like C# are well known to be slower with string objects since they treat them as immutable. On top of that, tree structures, especially the one used for shader compilation in Stride, tend to perform very slowly and are prone to be slow and work against the GC.
 
-## Why investigating spirv?
-
-Three things happened in the past 10 years :
-
-* Vulkan was released with a new kind of bytecode shader language called spirv
+## Why investigating SPIR-V?
 
-* .NET core came out with a new high performance feature for operating on slices of array (something that C# is way better at than processing string objects), namely `Span<T>`
+Three things happened in the past 10 years:
 
-* Most importantly, tools like [spirv-cross](https://github.com/KhronosGroup/SPIRV-Cross) and [naga](https://github.com/gfx-rs/wgpu/tree/trunk/naga) were created as a mean to translate shaders through spirv.
+* Vulkan was released with a new kind of bytecode shader language called SPIR-V
+* .NET Core introduced a new high-performance feature for operating on slices of array (something that C# is way better at than processing string objects), namely `Span<T>`
+* Most importantly, tools like [SPIRV-Cross](https://github.com/KhronosGroup/SPIRV-Cross) and [Naga](https://github.com/gfx-rs/wgpu/tree/trunk/naga) were created as a means to translate shaders through SPIR-V
 
-It was clear for everyone that we had to investigate how we could compile SDSL to spirv and use all those very performant tools to transpile SDSL to other languages.
+It was clear for everyone that we had to investigate how we could compile SDSL to SPIR-V and use all those very performant tools to transpile SDSL to other languages.
 
 SDSL is a very peculiar language and shifting from processing tree structures to processing segments of byte code is a great endeavor, especially for an engine.
 
-The following parts of this series of blog posts will focus on how such system can be made thanks to many new C# and .NET features that came out since .NET Core.
+The following parts of this series of blog posts will focus on how such a system can be created, thanks to the many new C# and .NET features that came out since the release of .NET Core.
 
 ## Summary
 
-Embracing spirv for Stride's shader system will hopefully empower us with a better control over the shader language but also improve performance for shader compilation!  💪💪
+Embracing SPIR-V for Stride's shader system will hopefully empower us with a better control over the shader language but also improve performance for shader compilation 💪💪.
 
 Thank you for reading!