12-25-2018, 12:01 PM
Xenko 3.1 Beta Released
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/12/xenko-3-1-beta-released.png" width="356" height="400" title="" alt="" /></div><div><p>Xenko 3.1 beta has <a href="https://xenko.com/blog/release-xenko-3-1-0-beta/">just been released</a>. This is the first major point release since the Xenko project <a href="https://www.youtube.com/watch?v=3_C6xmwHLTc">went open source</a> this summer. The primary focus of this beta is reorganizing Xenko to make it play nicely with the NuGet distribution system, although this refactoring has some very cool side effects. Now you are able to use individual components of Xenko on their own. For example, if you wanted to use the Xenko graphics library on it’s own, you can, independent of the rest of the Xenko game engine. This release also moves towards Xenko using .NET standard.</p>
<p>Details of the release from the Xenko blog:</p>
<blockquote>
<p>Xenko was always a big proponent of NuGet: since first version, Xenko was distributed as a NuGet package.</p>
<p>However, due to limitations (hello packages.config and project.json!), we were leveraging NuGet more as a distribution medium than proper NuGet packages: Xenko 3.0 is still a monolithic single package and it would not work out of the box when referenced from Visual Studio without using Xenko Launcher and Game Studio.</p>
<p>Xenko 3.0 paved the way by making Xenko compatible with the new project system (game projects were referencing Xenko using a <code>PackageReference</code>).</p>
<p>Today, Xenko 3.1 brings Xenko as a set of smaller NuGet package, each containing one assembly, with proper dependencies:</p>
<p><img alt="GitHub" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/12/xenko-3-1-beta-released.png" /></p>
<p>As a result, it is now possible to create a game project that references only the packages you want. Here are a few examples of “core” packages:</p>
<ul>
<li><code>Xenko.Engine</code>: allows you to use core engine runtime (including its dependencies)
</li>
<li><code>Xenko.Core.Assets.CompilerApp</code>: compile assets at build time
</li>
<li><code>Xenko.Core.Mathematics</code> or <code>Xenko.Graphics</code>: yes, if you want to make a custom project only using Xenko mathematics or graphics API without the full Xenko engine, you can!
</li>
<li><code>Xenko.Core.Assets</code>, <code>Xenko.Presentation</code> or <code>Xenko.Quantum</code>: all those piece of tech being used to build Xenko tooling are also available for reuse in other projects. Nothing prevents you from generating assets on the fly too!</li>
</ul>
<p>Then, various parts of the engine are distributed as <strong>optional</strong> packages:</p>
<ul>
<li><code>Xenko.Physics</code></li>
<li><code>Xenko.Particles</code></li>
<li><code>Xenko.UI</code></li>
<li><code>Xenko.SpriteStudio</code></li>
<li><code>Xenko.Video</code></li>
</ul>
<p>If you don’t reference those packages, they won’t be packaged with your game either. In many situations, it results in a smaller packaged game and improved startup time.</p>
</blockquote>
<p>In addition to the above changes, you can take a look at the <a href="https://github.com/xenko3d/xenko/commits/master">commit log on GitHub</a> for other aspects that made it into the 3.1 release.</p>
<p align="center"><iframe class='youtube-player' type='text/html' width='1280' height='720' src='https://www.youtube.com/embed/2dWELSNkzUE?version=3&rel=1&fs=1&autohide=2&showsearch=0&showinfo=1&iv_load_policy=1&wmode=transparent' allowfullscreen='true' style='border:0;'></iframe> <br />
</p>
<p class="under"> <span class="categories"><a href="https://www.gamefromscratch.com/category/GameDev-News.aspx">GameDev News</a></span> <span class="tags"><a href="https://www.gamefromscratch.com/?tag=/C%23" rel="tag">C#</a> <a href="https://www.gamefromscratch.com/?tag=/Paradox" rel="tag">Paradox</a> <a href="https://www.gamefromscratch.com/?tag=/Engine" rel="tag">Engine</a></span>
</p>
<hr />
</div>
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/12/xenko-3-1-beta-released.png" width="356" height="400" title="" alt="" /></div><div><p>Xenko 3.1 beta has <a href="https://xenko.com/blog/release-xenko-3-1-0-beta/">just been released</a>. This is the first major point release since the Xenko project <a href="https://www.youtube.com/watch?v=3_C6xmwHLTc">went open source</a> this summer. The primary focus of this beta is reorganizing Xenko to make it play nicely with the NuGet distribution system, although this refactoring has some very cool side effects. Now you are able to use individual components of Xenko on their own. For example, if you wanted to use the Xenko graphics library on it’s own, you can, independent of the rest of the Xenko game engine. This release also moves towards Xenko using .NET standard.</p>
<p>Details of the release from the Xenko blog:</p>
<blockquote>
<p>Xenko was always a big proponent of NuGet: since first version, Xenko was distributed as a NuGet package.</p>
<p>However, due to limitations (hello packages.config and project.json!), we were leveraging NuGet more as a distribution medium than proper NuGet packages: Xenko 3.0 is still a monolithic single package and it would not work out of the box when referenced from Visual Studio without using Xenko Launcher and Game Studio.</p>
<p>Xenko 3.0 paved the way by making Xenko compatible with the new project system (game projects were referencing Xenko using a <code>PackageReference</code>).</p>
<p>Today, Xenko 3.1 brings Xenko as a set of smaller NuGet package, each containing one assembly, with proper dependencies:</p>
<p><img alt="GitHub" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/12/xenko-3-1-beta-released.png" /></p>
<p>As a result, it is now possible to create a game project that references only the packages you want. Here are a few examples of “core” packages:</p>
<ul>
<li><code>Xenko.Engine</code>: allows you to use core engine runtime (including its dependencies)
</li>
<li><code>Xenko.Core.Assets.CompilerApp</code>: compile assets at build time
</li>
<li><code>Xenko.Core.Mathematics</code> or <code>Xenko.Graphics</code>: yes, if you want to make a custom project only using Xenko mathematics or graphics API without the full Xenko engine, you can!
</li>
<li><code>Xenko.Core.Assets</code>, <code>Xenko.Presentation</code> or <code>Xenko.Quantum</code>: all those piece of tech being used to build Xenko tooling are also available for reuse in other projects. Nothing prevents you from generating assets on the fly too!</li>
</ul>
<p>Then, various parts of the engine are distributed as <strong>optional</strong> packages:</p>
<ul>
<li><code>Xenko.Physics</code></li>
<li><code>Xenko.Particles</code></li>
<li><code>Xenko.UI</code></li>
<li><code>Xenko.SpriteStudio</code></li>
<li><code>Xenko.Video</code></li>
</ul>
<p>If you don’t reference those packages, they won’t be packaged with your game either. In many situations, it results in a smaller packaged game and improved startup time.</p>
</blockquote>
<p>In addition to the above changes, you can take a look at the <a href="https://github.com/xenko3d/xenko/commits/master">commit log on GitHub</a> for other aspects that made it into the 3.1 release.</p>
<p align="center"><iframe class='youtube-player' type='text/html' width='1280' height='720' src='https://www.youtube.com/embed/2dWELSNkzUE?version=3&rel=1&fs=1&autohide=2&showsearch=0&showinfo=1&iv_load_policy=1&wmode=transparent' allowfullscreen='true' style='border:0;'></iframe> <br />
</p>
<p class="under"> <span class="categories"><a href="https://www.gamefromscratch.com/category/GameDev-News.aspx">GameDev News</a></span> <span class="tags"><a href="https://www.gamefromscratch.com/?tag=/C%23" rel="tag">C#</a> <a href="https://www.gamefromscratch.com/?tag=/Paradox" rel="tag">Paradox</a> <a href="https://www.gamefromscratch.com/?tag=/Engine" rel="tag">Engine</a></span>
</p>
<hr />
</div>