Stride Game Engine

Stride 4.1 is now live!

Sat, 16 Jul 2022 00:00:00 +0000

Stride 4.1 is here and ready for the future!

Stride contributors are proud to announce a new release now running on .NET 6 supporting the latest C# 10. That means you can now head to the download page and start developing your games using the latest .NET technologies.

Stride On .NET Live

We had the pleasure to be on a live stream with the .NET team! We gave an introduction, overview and some live demos:

Improvements Summary

Here’s a non-exhaustive list of new improvements:

.NET 6 support and VS 2022 plugin
- Stride 4.1 leverages the power of .NET 6
- Support for C# 10
Dithered shadows for semi-transparent materials
Physics constraints
- Bullet constraints wrapped around in easy to use functionality
- Editor gizmos for physics constraints
Physics performance optimization
ACES tonemaping
Fog image effect
Outline image effect
Improved editor gizmos
C# Intermediate tutorials project
- This Open Collective sub-project was successfully funded by the community. All related video recordings are available on Stride’s Youtube channel and the tutorials page in the documentation will also be update to reflect the new project.
Many more minor fixes and quality of life improvements
- Fixed sample game
- Simpler Procedural Model creation
- New math signatures (1122, 1121, 1090)
- Dispatcher/threadpool improvements
- Ambient Occlusion quality improvement
- And many other fixes

Improvement Details

Dithered shadows for semi-transparent materials

Produces semi-transparent shadows by poking more and more holes in the shadow map based on the transparency of the object, shadow map filtering will blur those holes with their neighbor which will result in those partially opaque pixels.

Physics constraints

Stride’s physics system Bullet comes with a set of constraints for you to use in your projects. These constraints are now all visible inside the editor, previewing the constraints using various editor gizmo.

For more information on all the types of constraints, you can read up about them in the Stride documentation or watch the video below.

Physics optimizations

Retrieving collision and contact information was previously done by re-testing all components for collisions, which, as one might expect, led to awful performance for physics heavy scenes (could take up to and above 90% of the frame).

Contacts are now lazily evaluated to reduce overhead when nothing ends up reading them. Users can now read and iterate over all collisions through Simulation.CurrentCollisions.

Improved editor gizmos

The old gizmos weren’t very nice to look at, so this feature makes them look better and more user-friendly. It also changes how the rotation gizmo works and adds scale planes to the scale gizmo.

This feature also updates the text on the CameraOrientationGizmo to be XYZ instead of right/left. Still prefer the old text instead of the XYZ coordinate? Don’t worry, there’s a setting under the viewport settings that swaps it back to the old text.

Intermediate tutorials

One of the first Open Collective sub-projects is the intermediate C# tutorials project. After discussion in community meetings and with various contributors donating directly to this project, the amount for this project to be included in Stride quickly became a realization.

With Stride 4.1, you will be able to select the C# intermediate tutorials project as a new template project. The template project contains (at the moment of writing) 11 topics that every developer will want to have a look at. 1. UI basics 1. Collision triggers 1. Raycasting 1. Projecting and Unprojecting 1. Async(hronous) scripts 1. Scene loading 1. Animation basics 1. Audio 1. First person camera 1. Third person camera 1. Navigation

Each tutorial has a video tutorial accompanying it, which can be found on Stride’s Youtube channel. Below you can find the full playlist.

Known Issues

Integrated C# Editor

The transition to .NET6 unfortunately broke the help tooltips and the code completion of the integrated C# code editor. But we decided to accept it for now, as everyone is using a proper C# editor anyways, such as Visual Studio, Rider or Visual Studio Code.

The reason for the error is that RoslynPad, the underlaying library, also needs an update or fix. We’ll adress this in one of the upcoming minor version releases.

A little help

We, contributors, believe that Stride can help .NET game developers make the games they want with ease using their favorite languages. We want to make sure Stride offers the most comfortable environment for developing games, and this takes time and effort.

Since the free and open-source release of Stride, the community has been growing slowly, so we have decided to open a fund to reward developers for any contribution they make to Stride. We set up an Open Collective page to manage our funds and allocate money for features that the community would like to see implemented.

We have various bounties for bug fixes and features (Vulkan support, decals, morph targets, and many others). If you have or know someone with the skills to tackle those bounties, please reach out to us through the respective Github tickets. You can also contact us through our discord server or on Github to propose new bounties.

Contributors

Many thanks to all the contributors who have donated their time and skill by adding features, fixing bugs, managing the build pipelines, adding documentation, and reviewing PRs.

Financial contributors

Also, a huge thanks to the individuals and companies who contributed financially to our Open Collective!

ORE System with a diamond sponsorship
xen2 Core contributor that donated a large portion of the previous Patreon back through Open collective
vvvv A visual live-programming environment for easy prototyping and development. It is designed to facilitate the handling of large media environments with physical interfaces, real-time motion graphics, audio and video that can interact with many users simultaneously. vvvv uses Stride
Vašo
Mitchel Albertz
Bill
Ideonella
Soul Rider
najak3d
Eideren
Jorn Aggror
Marian Dziubiak
Youness KAFIA
David Thunderclown
Christian Clavet
Marko Viitanen
Aaron Disibio
z16
Incognito
Walter Hulsebos
TheKeyblader
James Rinker
ztl
Bruno Garcia
BanditRevolver
EmmX
SeleDreams
Vignette
Longplay Games
Redberd36

Community meeting February 2022

Wed, 16 Feb 2022 00:00:00 +0000

Summary community meeting 2022

Hello there fellow Striders,

On February 16th we held another community meeting. A whopping 2.5 hours with various subjects. Here is a quick summary.

Current funding

With a budget of $4,220.48 USD at the moment of the community meeting happening, we wanted to decide on whether to allocate money for bugs and new features. So a big thanks to all those who are donating to this project. In particular:

VVVV
Vašo (vaclav)
ORE system with a diamond sponsorship

Funding for bug bounties

Fullscreen Vulkan support
- Github ticket
- 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.
UI slowness bug
- Github ticket
- 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

Funding for features

Linux runtime support
- Github ticket
- 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
Decal support
- Github discussion requires more deliverables
- New Open collective project 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
- New Open collective project Morhping Target added and will be updated once deliverables are clear:
Embed stride into UI frameworks
- There already is a work in progress PR that allows developers to specify a custom render context.
- New Open collective Project for Embedding Stride into UI frameworks
Silk.NET
- New Open collective project Silk.NET

Release 4.1

Release notes wip are prepared by Eideren/Vaso/Yka.
Final checks by Xen2: VS plugin

Additional task for Xen2

Documentation needs to auto-release when Release branch is updated
Ask previous implementer of SPIR-V shader system if he is interested in new work for Stride

Work in progress

Code only project: will enter beta phase
- When merged into Stride 4.2 beta, we will add an Open collective page for additional examples.
C# Pong game example: finishing touches (sound)
The following C# intermediate tutorials are written but not yet recorded:
- UI basics
  - Both via the editor as well as entirely through code
- Scene loading
  - Loading/Unloading
  - Reloading scenes
  - Child scenes
- Collision triggers
- Raycasting
- Animation basics
- Audio
  - Small tutorial really
- Navigation meshes and pathfinding
  - Both editor as well as code only approaches
- Sync vs Async
  - Difference and 2 examples

Epic grant

Yka and AggrorJorn have a look at Epic grant and make final proposal in the 3rd week of February

Community meeting November 2021

Mon, 29 Nov 2021 00:00:00 +0000

Hello fellow Striders,

November 29th we had another commmunity meeting. This blogpost summarizes the topics we talked about

A month of Open collective

After a month using the new sponsor platform, the Stride collective has reached a balance of $1,984.31 USD. We started discussing how and where the money should be distributed to. We want to do this with the help of Open collective ‘Projects’. These projects are listed on Stride’s Open collective page, and have their own tiers, targets and description. Users can sponsor projects directly instead of the main Stride collective if they want to.

We have come up with several projects that need to be written out in more detail before we will add them to the Open collective page. All tickets below have a Github disscusion for more details.

OC project: Bug bounties project
- Before starting on an issue, make it known on Github and Discord that your are willing to tackle the issue. It would be a shame if multiple people try to solve the same issue.
- Any PR to the Stride repo must be reviewed by a contributor and discussed if needed.
- Once a PR is reviewed and merged to the Stride repo, the submitter 60% of the bounty.
- The submitter receives the remaining 40% when stride release happens.
- Github Discussion
OC project: .NET 6 platforms support
- In order for proper support for macOs, we need hardware to test this on. Xen2 will look in to the hardware requirements for this.
- Github Discussion
OC project: Shader system
- Xen2 will gather info and budget requirements
- Github Discussion
OC project: Linux/macOS support’
- A rather large topic that require a lot of work is the the support for Linux and/or macOs. When worked out in more detail, it can be used in the plan for requesting an Epic grant. Subtopics to resolve:
  - Runtime/3d
  - Build tools (able to msbuild a Stride project and have the asset compiler work on it) requirement: FBX/Assimp
  - Editor
- Github Discussion

Preparing request Epic grant

For a while now we have been wanting to pursue the option of requesting an Epig grant. In order to do so however, we need to come up with a proper plan. The endgoal is to have a proper document explaining what we want to do, and how we plan to spend any given budget.

AggrorJorn starts a github ticket where we gather info on the request to Epic. He will contact others for proof read and further info. Github Discussion

Some of the topics mentioned: - Shader system - Editor rewrite - Megascan Integration - ECS rewrite/Run Update() and Render() in parallel

Other Action items

We close forum in December as there is almost no activity there. We want to utilize Discord and Github discussion for this. The forum will be read only but we will no longer refer to it from the website and Github.
Use a Github project for remaining tasks: Overview
Github ticket on a simple free community marketplace
- Github Discussion
- A lot of people have made usefull components/utilities/art and other usefull assets for in Stride projects. Right now we don’t have a quick and easy to import such assets in to an existing (editor) project.
- What we can do it is utilise the existing Nuget (tagging) system so that users can quickly add a component to their ongoing project in the editor.
Documentation on the stride source/new comers tutorial
- YKA, Manio143 and Tebjan collect some info for a tutorial: Github Discussion

Ongoing development

Manio143: finishing touches/documentation for Physics constraints
AggrorJorn: Splines
- Trying to finish the base splines which could be integrated in to the Stride source. Other Spline based components should be added later, so that we can have a milestone finished.
- Some tricky stuff with custom translation gizmo’s for controlling tangents in the editor are currently holding me back. If this isn’t resolved quickly I will make a PR without this (nice to have) feature
Release of 4.1 only held back by final .NET 6 related fixes. After that Xen2 will prepare release. AggrorJorn will aid in blogpost release notes

Open collective

Sun, 31 Oct 2021 00:00:00 +0000

Stride has been using Patreon and Github sponsors for a while now. However, in the recent community meeting of october 1st it became apparent that these donation platforms don’t really suit all of our needs. Both Github sponsors and Patreon don’t really show where the money is going. To solve this we have been looking at a different platform that allows us to communicate more openly on our expenses and where money will be spent. After some investigation and various registration and other formalities, we can now say goodbye to Patreon, as Stride will from now use the Open Collective platform.

Open (Source) collective

Open collective is similar to other sponsor platforms, but sticks out in the way it openly displays payments and expenses. Everything about it is open for everyone to see. Through various Tiers, people can sponsor the Stride game engine. Each tier will have its own reward(s). Some tiers for instance will have the reward that users are shown on the stride website as a thank you. This is being worked on.

We also needed a good way to deal with payments towards contributors and any tax related activities that come with it. Open collective allows the Stride collective to join a so-called ‘Fiscal host’ which takes care of all of that for us, for a percentage of the money contributed. After some communication and verification on the Stride github repository we are now also officially connected with the Open Source Collective. The Open Source Collective has various open source projects under its wing: WebPack, VueJs, OBS, Babel, Bootstrap and many more.

Payments and Expenses

Every payment made to a contributor will always show up on the Stride’s open collective. A Stride contributor can submit an invoice: for instance the cost of Google accounts or domain names. These invoices can be approved by the Stride contributors team. These are the same people that are active members of the Stride Contributors team on Github. Submitted invoices can be approved at any given time but allocating money for specific projects is done at the end of each month (or beginning).

Projects

The Stride contributors have the final call where all the collected money will be allocated too. This will be done with the help of Projects. This Open Collective feature acts as a sort of ‘Ledger’ where money can be stored until the time comes to pay the contributor(s) of a project. A project can have its own tiers and goals. Those projects could be all sorts of things: new engine features, research on new technology, high priority bugs or documentation. These kinds of projects will be discussed at community meetings to get the input of the Stride community. Here is an example project.

People can also choose to donate to a specific project rather than the Stride collective in general if they want to. So if you only want to see your money being used for a specific cause, you are completely free to do so. You are more than welcome to do both of course. In the image below you can see an example of how money that has been donated to the Stride collective, has been partially allocated to a specific project.

What’s next?

We first want to see how this first month of the new platform goes. At the end of November/beginning December we will hold a new community meeting and we will discuss how things went and how we plan on distributing the donations.

There are also some remaining tasks regarding the Open Collective that will be taken care of in the weeks to come:

Setup webhook to Discord
Setup webhook to Twitter
Fully automate the website to show sponsors
Fully automate the Github backers.md file with sponsors
Write up blog on the entire process on how we spend money
Add open collective to sponsors.yaml on github

Community meeting October 2021

Fri, 01 Oct 2021 00:00:00 +0000

It has been quite a while since we had a community meeting with the Stride community. On the 1st of October 2021 we had a good 2 hour chat about various topics on the Stride game engine.

Access rights

First topic was about clearing up access rights of the Stride source contributors and how this can be displayed better to the rest of the world.

Github features a teams option, which is now free for open source projects. Xen2 made sure that those contributing to the engine are now part of the team on Github: https://github.com/orgs/stride3d/teams/stride-contributors. These contributors can review and approve pull requests in to the various stride projects (engine, website, documentation).
- When changes are merged into the website project and specifically the ‘release’ branch, an automated process will trigger the website deployment.
- Documentation is updated as well, although this is a manual process that needs to be triggered. Xen2 and Aggror will do some knowledge sharing in private, so that this process does not lie solely with xen2.
Social media access
- Youtube: xen2 and Aggror
- Facebook: xen2 and M0TH
- Twitter: xen2 and Aggror

Roadmap

The roadmap on Github hasn’t received an update in quite a while. The reason for this is that there simply is no capacity to pick up these kind of features like terrain editor, visual programming etc. What we see in the community is that various contributors work on useful features for their own games, and as a result these kind of features and bug fixes and up being merged in to the Stride repository.

As a result it has now been decided that we no longer will use the roadmap on Github. At the moment of writing this blog, the roadmap has already been removed. If, in the future, we have more funding and capacity, we can re-introduce it again.
Aggror will try to put out a blogpost once a month keeping the community up to date on features that community members are working on. This also requires some initiative from the community. So if you have something that you are working on, feel free to send a message to Aggror on Discord. That we can feature your screenshots, videos, PR’s in a blogpost on the stride website.

Funding

There were 2 ways to contribute to Stride financially: Patreon and Xen2 sponsorship on his Github account.

Both these donation services didn’t really give a clear overview where the money was being spent on.
Sponsoring Xen2 on Github would specifically and only go to Xen2. On top of that there is no easy way to use this as a marketing tool.
Only Xen2 had access to Patreon, making it another responsibility for him to:
- Post something interesting on Patreon (for which he has no time)
- Do tax related activities and payments.
Because of the above, Stride’s Patreon page will soon close (or already might be at the time of posting blog)
Aggror will look into setting up a more open way of viewing where money from donations is being spent on. The idea here is to have a look at Open Collective
- Aggror will present his findings to xen2. Once a decision has been made, the community will be informed.
.NET foundation
- Stride has joined the .NET foundation. The .NET foundation offers to host various services on their Azure subscriptions. That means that a majority of the costs when it comes to hosting is taken care of for us.
- As a result of this, Xen will move various services from Digital ocean to Azure. This will reduce costs. Money that is gained from donations can be spent on bug bounties, features and documentation. Once we have a new donation mechanism in place, we will have another community meeting on how to distribute money.
- Aggror will also be included in the communication with .Net foundation.
Xen2 gave a nice summary on the operating costs for various (web related)services
- Azure: used to be $50~$100 per month but now paid by .NET Foundation
- StackPath (CDN): $10 per month, can be moved to Azure
- Google Cloud Service: $5 per month
- DigitalOcean: $30 per month (teamcity and forums server), can be moved to Azure
- GitHub: $40 per month
  - Some demo’s use LFS. If .NET foundation were to cover those costs too, we could add additional demo’s.
- SSL: used to be expensive but now free (auto renew let’s encrypt or Azure)
- Domains: cheap, $10 per year
Applying for a grant with Epic, Microsoft etc.
- Although this is something that we want to pursue, we first want to have a new donation service in place. The next community meeting will cover this topic again.

Stride 4.1

Stride 4.1 is on its way, but when exactly and what can we expect this year?

Stride 4.1 BETA will include the upgrade to .NET 6
Stride 4.1 targeted around november/december 2021
Although full Linux support is not possible right now, we will look at having the Linux runtime working again with Stride 4.1
Aggror will start collect info for the release notes

Remaining topics

For the remaining topics, we ran out of time, so these will be picked up at another community meeting.

Stride 4.0 is now live!

Mon, 01 Feb 2021 00:00:00 +0000

Stride 4.0 has been around for a while, but it’s now time to remove the -beta tag!

Many thanks to the community and all the contributors who made this release possible!

Highlights

Xenko is now Stride!

The Xenko game engine has been renamed to Stride. From now on, all source code, blogs, and tutorials will use the name ‘Stride’ instead of ‘Xenko’.

Here is the new logo:

More details available on the dedicated blog post

Voxel Cone Tracing GI

Thanks to a substantial contribution from Sean Boettger and sponsored by David Jeske, Stride now supports Voxel Cone Tracing GI!

Here it is in action:

As you can see, there are many customizations and settings available in the editor:

There’s a documentation page explaining how to set up the project with Voxel Cone Tracing GI.

Here’s the original forum post and pull request. Thanks again for this great contribution!

.NET 5

Stride editor and toolchain is now running with .NET 5! Runtime has been working with .NET Core for a few versions already.

This allows us to have scripts and custom assets in a project targetting .NET Standard 2.1 or .NET 5.

If you have scripts or custom assets in a .NET Framework project rather than a .NET Standard project, you can still choose between .NET 5 and .NET Framework within the launcher:

The framework will also be displayed in the Game Studio toolbar for easier identification while both coexist.

.NET Framework version can be considered deprecated and will likely be removed in a future release (likely 4.1) to allow us to take full advantage of C# 8.0 and soon-to-come C# 9.0.

We also expect dropping .NET Framework and supporting only .NET 5 will greatly simplify our installation process since we won’t depend on specific workloads or packages of Visual Studio being installed anymore. This was a recurring issue with our users.

Flexible GPU Instancing

Aka geometry instancing. Thanks to another big community contribution sponsored by vvvv, Stride now supports GPU instancing per model.

The nice thing about it is, that it plays together with the entity-component system: Simply add an Instancing component to an entity with a model. Then you can choose between 3 ways of how you generate the instances:

EntityTransform, uses the transformation of other entities with an Instance component. This allows you to add components like physics, audio, etc. to each instance.
UserArray, for providing an array of matrices via script
UserBuffer, for providing a structured buffer (GPU resource) of matrices via script

UserArray and UserBuffer even allow you to specify how the matrix is multiplied with the parent transformation.

It even works with skinning:

Picking individual instances in Game Studio works as well and selects the entity with the respective Instance component.

There are also two new entity templates for easy setup:

An example project that shows the new features can be found here: StrideTransformationInstancing

Graphics API: different selection mechanism + Vulkan improvements

There’s been a big overhaul on Stride build system to make Graphics API selection work in a more future-proof way.

It was previously relying on the custom RuntimeIdentifier being set in the solution. This didn’t work very well because it was completely orthogonal to the existing RuntimeIdentifier, and sometimes not having good fallbacks.

From now on, the user project will use StrideGraphicsApi in the .csproj project file to specify the graphics API. We hope to expose this in the editor later.

We also took the opportunity to improve the state of Vulkan renderer (thanks to a switch to Vortice.Vulkan bindings from Amer Koleci) and automatize graphics unit tests, currently running for D3D11 and Vulkan.

It’s still a work in progress so expect more in future releases.

Documentation & Tutorials

The first 10 C# beginner tutorials are recorded and uploaded to the official Stride Youtube channel. You check out the playlist here.

These videos are the video equivalent of the existing online documentation for the C# beginner template tutorials and the ‘new project’ template when creating a new project from the Stride launcher.

The C# beginner series should be fully recorded by the end of July 2020. After those videos are done, Jorn will put his focus on the C# Intermediate project template. Here a is work in progress screenshot on the raycasting tutorial:

New Developers are Welcome!

The Stride GitHub repository has more closed pull requests than open issues. This is a good sign! But in order to move faster and adapt to new technologies, we would be very happy to see more new talents in our friendly and professional developer community.

There are several good reasons to join us:

Writing engine code in C# is fun and quite productive
Stride users will work with what you create
We are happy to help, should you get stuck
You can learn a lot, the Stride code base is very professional and has high-quality standards
An open-source contribution is a great addition to your portfolio

No matter whether you (or someone you know) can contribute documentation updates, UI improvements, bug fixes, or new rendering technologies, we welcome everyone!

vvvv releases VL.Stride

Fri, 02 Oct 2020 00:00:00 +0000

Helo Striders,

this is vvvv calling! We’ve just released a new 3d-engine for vvvv, our visual live-programming environment for .NET. We call it “VL.Stride” and it is basically a wrapper around the Stride engine, using it independent from the Stride Game Studio.

In this release blog post, we talk about some details.

Note that vvvv’s focus is not on creating games but rather on creative coding and interaction design style of applications. But due to its live-programming nature, using a state hot-reload approach, it may still be interesting for you to quickly prototype some functionality for your games. Also vvvv can help you explore all the different parts of the Stride engine and understand how they work together. Being able to touch all parts while they are running, allows to get an overview faster than just going through Stride’s documentation.

We’d like to invite you to play with it and hear your feedback. vvvv is free for non-commercial use, no strings attached. So please just go ahead, download vvvv gamma 2020.3-preview and let us know what you think!

NODE20

If you’re already convinced and want to learn more about vvvv, join us for 30 online workshops covering various topics, we’re running during the NODE20 - Forum for Digital Arts from October 3rd to 8th.

To give you an idea, the following workshops will be using VL.Stride:

As you can see, with vvvv we’re quite invested in Stride. We bow before everyone who helped to make it what it is today and want to do our best to contribute our share to give it a bright future.

Yours, vvvv.

Community Meeting May 2020

Fri, 08 May 2020 00:00:00 +0000

On May the 8th we held another community meeting in the Discord. Its main goal was to talk about the ongoing work on Stride and its first official release after the rename to Stride.

Summary

Official Stride 4.0 release. The plan is to release Stride 4.0 officially within the next 2 weeks. It depends a little on whether .Net 3.1 is going to be part of it. If this can be done within reasonable time than we rather incorporate this into the official release of 4.0
- The release notes will be written in a more friendly way.
- Aggror will look into making a video regarding the release as well as some of the new key features like VXGI cone tracing.
Xen2 has filled in the application for joining the .NET Foundation, a non-profit organization (NPO). At the moment of writing this blog, no response to this yet.
Roadmap The GitHub roadmap will be updated. From now on it will only contain features that Xen2 or others will actively work on. This means some epics will be removed from the roadmap, and some new ones will be added. The epics that are removed will still be visible as requests in Github issues.
There is now a stride tag on gamedev.stackexchange (tag might be changed to stride-engine soon btw). We can use this site for Q&A and additional “How to? questions. https://gamedev.stackexchange.com/questions/tagged/stride
Documentation
- Recording of C# beginner video tutorials is ongoing. Videos are listed on the official Stride Youtube account. Basically, every page will have an accompanying video. The playlist is being updated on the go.
- Started making the C# intermediate tutorial section.
- Continuation of the editor video tutorials once the programming tutorials are up to speed again.
Some people showed interest in working on a community showcase demo for Stride. A new discord channel #showcasing-team was created.

VVVV and VL.Stride

User Tebjan explained some more about VVVV and VL.Stride. Here is a short overview of what we at vvvv are doing and will release somewhen this year:

What is vvvv gamma?

vvvv gamma is a live programming environment for .NET
VL is our visual programming language that works with every .NET assembly
Development, compilation and state hot-reload at runtime, we believe this is the future of software development
You can see the data while you develop
Can export .NET executables
More info and download at: visualprogramming.net

What is VL.Stride?

Stride will be our 3d rendering library of choice
We are working on making the Stride features available as convenient nodes in vvvv gamma
High-Level nodes for: Mainloop, Windowing, Scene Graph, Materials, Models, Textures, etc.
Low-Level nodes for: Drawing API, Visual Shaders, Vector Math, etc.
Load a Stride project at runtime and use all content of it
You can see dev captures at: vl-xenko-3d-engine-update-3

We actively support the Stride open-source community and financially support the Stride development: vvvv-meets-xenko

Sponsoring and gold members

We welcome our new gold sponsor David Jeske. We would also like to thank him for contributing the work on VXGI last year. He is using Stride for one of his projects.

OUTDATED: As off November 2021, we will use Open collective Also, a friendly reminder, that if you sponsor Stride through Github, the reward is doubled by Github. ~~You can also still sponsor through Patreon~~

Xenko has been renamed to Stride

Mon, 20 Apr 2020 00:00:00 +0000

The Xenko game engine has been renamed to Stride. From now on, all source code, blogs and tutorials will use the name ‘Stride’ instead of ‘Xenko’.

Why the name change?

Changing product names always is a lot of work and comes with some downsides. However, we would not do this if there weren’t any good reasons for us to do so. Since 2019, xen2, has been trying to affiliate Xenko with the .NET Foundation, a non-profit organization (NPO).

There are various reasons for this:

We wanted to let the community know that Xenko is completely and 100% free and open in its development. This also means that any donations should always be made 100% visible to the public. This also includes what and where the donation money is spent on. Joining the .NET Foundation would aid in visualizing how this money would be spent.
Being able to tell possible investors/backers/companies that Xenko/Stride can be trusted. This can help with publicity and more funding.
They also provide help for opensource projects in various areas.

This sounded great, but unfortunately, there was a massive drawback to this: as long as the project kept the name ‘Xenko’ (trademarked by Silicon Studio), it would be difficult to transfer to the .NET Foundation. After a lot of back and forth between Silicon Studio legal department, xen2 and the .NET Foundation, we didn’t get any step closer to achieving our goals.

After several months without progress, we started to suggest the idea of a rename to the community. In the Discord server, we opened up the name change and logo suggestions to see how people would react and what their suggestions would be.

About 6 months later, several polls, logo proposal and a lot of brainstorming, we settled for the name: Stride.

New Stride Logo

The new Stride logo, designed by sebl (from schnellebuntebilder), was chosen after a process managed by Eideren consisting of several community votes. Also, tebjan is the one that came up with the name Stride. Many thanks to them, as well as to all the other people involved!

Without further ado, here it is:

Game Studio will use a red variant:

What does this mean for you?

The Xenko launcher will ask to install Stride launcher.
Stride will be available starting from version 4.0 (available shortly). This rename also applies to all websites, social media and documentation. It is possible that the name Xenko or its logo might still be drifting around somewhere in a screenshot here and there, but those will eventually be removed.
Stride 4.0 can opens Xenko 3.1 projects and convert them automatically. Please don’t forget to properly backup your projects, and report any issues you have during the automatic upgrade process.

What’s next?

Release Stride 4.0 within the next few days
A new application to join the .NET Foundation
A new effort to find new backers
The new Youtube channel will be the new hub for video tutorials. We will start with recording videos for the C# beginner section. After that, we will look at new editor video tutorials and extend the C# tutorials.

Here are the new links that you should be using:

Github: https://github.com/stride3d/stride
Website: https://stride3d.net/
Documentation: https://doc.stride3d.net/latest/en/manual/index.html
Twitter: https://twitter.com/stridedotnet
Youtube: https://www.youtube.com/c/Stride3d

Final notes

We would like to thank each and everyone involved in the long process of picking a new name, a new logo and other related media/art. A huge shoutout to xen2 for doing the renaming process.

January 2020 recap

Mon, 03 Feb 2020 00:00:00 +0000

Hi everyone,

Welcome to our January recap. Here is a quick recap on what’s going on with Xenko development and its community.

A new logo for Stride

We decided to contact substance/adobe at the start of January after seeing that many people felt that the most voted community logo for Stride was too close to theirs. We received a reply from their legal team which, of course, told us that we would need to change it. It’s the legal team, playing it safe is part of their job. They also told us that we could get in touch with their design team, we took that opportunity and sent multiple emails but they never got back to us.

Proposals are open again so if you think you have a logo that would fit with our new name (Stride), please fill in the picture attached below with your design. There’s also the Figma project 6 if you would rather work on that. For more information see the forum post

3.2 release

We are getting close to the 3.2 release. We hope to share some info on that soon. In the mean time we are also getting ready for the rename to Stride. This will happen after the 3.2 release.

Community picks

Check out these community projects that people are working on:

Project draco

User: Its me DIO!

Rollerghoaster

User: AggrorJorn

Download

December 2019 recap

Tue, 31 Dec 2019 00:00:00 +0000

Hi everyone,

Happy new year everybody. In this blog we do a quick recap of the final developments of Xenko in 2019 and what the community has been up to.

What is being worked on

The latest new features are being finished for the release of 3.2. This version should be released near the end of January.

Community meeting 3

On December 18th we held another community meeting. Check here for the summary. The most important thing here is that we are getting ready for the rename.

Stride logo

With ‘Stride’ being the new name for Xenko in the near future, the #logo-change Discord channel has been seeing a lot of suggestions and even a voting on some of the ideas from the community.

Community picks

Check out these awesome projects that community members have been working on:

MentalArray

User: MentalArray

Testing the Xenko game engine took only a week to do this that included learning the scripting system and all model building and texturing was really trying to figure out animations and happy with result

Fog of war

User: Jarmo

This is a fog of war system written for Xenko. Github project

Community Meeting #3

Wed, 18 Dec 2019 00:00:00 +0000

On the 18th of december 2019 we had our third and final community meeting for 2019. Below you can find a summary of what has been discussed.

Final Stride logo deadline: 22 december 2019
With the current amount of developers and resources, larger features like features are simply not possible. Features like cross-platform support, Visual studio Code, rebuilding the editor for Linux, Terrain and vegetation.
- If you have any programming skills and want to help out, have a look at the issues on github.
Roadmap 3.2 - Estimated by end of January 2020
- New feature: Url Reference
- New feature: HeightField property
- (optional) Debug Drawing
- (optional) LOD script
Roadmap 4.0
- This version will cover the rename of Xenko to Stride.
- Activating the first social media accounts.
- Joining the .NET foundation to become an NPO.
- Git/Patreon donations will have to be evaluated depending on NPO requirements.
- Contacting Microsoft/Partners for support/sponsorship.

Xenko 3.1 released!

Mon, 11 Nov 2019 00:00:00 +0000

It took some time to stabilize everything with the new Xenko packages, but we now feel confident enough to release Xenko 3.1!

One of the major change is turning the engine into modular NuGet packages, published on NuGet.org.

Please note that Visual Studio 2017 is not supported anymore, please upgrade to 2019.

Many thanks to the community and all the contributors who made this release possible: aggror, Eideren, alexb910, comradekingu, flabbie, CharlesWoodhill, Artaki, indigozero, dfkeenan, dominikjancik, erictuvesson, Hyperpred, louies0623, Lucifer2031, Ethereal77, mostafa901, Kryptos-FR, shinkitsunemaru, phr00t, Polymo, profan, xendez, Scorp-121, SleepyMode, tebjan, xen2, WhyPenguins, OoElectron, joreg, meriaizen86, rgawry, SantosSi, xwellingtonx, SilentCLD, HoSeCoin, Swann Martinet, WaldiS and pansan.

Highlights

Xenko 3.1 loves NuGet!

Xenko was always a big proponent of NuGet: since first version, Xenko was distributed as a NuGet package.

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.

Xenko 3.0 paved the way by making Xenko compatible with the new project system (game projects were referencing Xenko using a PackageReference).

Today, Xenko 3.1 brings Xenko as a set of smaller NuGet package, each containing one assembly, with proper dependencies:

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:

Xenko.Engine: allows you to use core engine runtime (including its dependencies)
Xenko.Core.Assets.CompilerApp: compile assets at build time
Xenko.Core.Mathematics or Xenko.Graphics: yes, if you want to make a custom project only using Xenko mathematics or graphics API without the full Xenko engine, you can!
Xenko.Core.Assets, Xenko.Presentation or Xenko.Quantum: 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!

Then, various parts of the engine are distributed as optional packages:

Xenko.Physics
Xenko.Particles
Xenko.UI
Xenko.SpriteStudio
Xenko.Video

If you don’t reference those packages, they won’t be packaged with your game either. In many situations, it will result in a smaller packaged game and improved startup time.

Also, you will be free to replace those functionalities with alternative libraries.

Package layout: following best NuGet practices

Previously Xenko references were added to the project using custom targets.

New packages are now be layout as NuGet/Visual Studio expects them, in folders like lib/net45 and lib/monodroid10.

We still have a few custom MSBuild targets but reduced them to minimum.

Xenko assets are also distributed as part of package

NuGet packages have a xenko folder containing Xenko assets. As a result, user are able to generate nuget package containing Xenko assets out of the box from Visual Studio and publish them on NuGet for general consumption.

Xenko Packages are now distributed on nuget.org

With all those changes, it makes sense to stop distributing Xenko on our custom nuget server and use nuget.org instead.

This will greatly reduce friction to try Xenko (any project would work out of the box in Visual Studio). This might also make our launcher completely optional in the long run.

Xenko tooling resolves assemblies dynamically using NuGet API

Tools such as GameStudio or Asset Compiler are distributed as NuGet packages. However, it won’t bundle Xenko Runtime, which will simply be encoded as dependency.

When running those tools, they are resolving Xenko runtime assemblies directly in the NuGet cache.

This allows for distributing those tools as very small and easy-to-upgrade packages, avoiding file duplications. This is similar to what dotnet-cli is doing with deps file.

This brings lot of technical challenges but should allow us in the future to be more flexible in the future to load the exact runtime and plugins that the user project reference rather than the one hardcoded with the tool.

Future: plugin support for editor

Xenko 3.1 editor will still be monolithic: editor support for UI, SpriteStudio, Video and other optional modules will be hardcoded.

However, the target is to get rid of them as soon as possible, and treat them as what they are: plugins.

Full switch to .NET Standard

Xenko supports .NET Standard for most of its runtime assemblies.

Xenko games can run on .NET Core for both Windows and Linux.

Tutorials

Xenko now has a tutorial section in the documentation!

The first project “C# Beginner”, demonstrates 12 beginner programming concepts.

Users will be able to select the tutorial template when creating a new Xenko project to practice and experiment with the code.

Additionally, the code used in the project is directly referenced by the new documentation section which explains each individual tutorial level.

The amount of tutorials, as well as intermediate and advanced tutorials, will be extended/added from now on.

BulletSharp update

Eideren worked on updating our old custom modified version of BulletSharp (the wrapper library we use for our physics engine).

Things should be much easier to maintain from now on.

Changelog

This release also contains numerous improvements, bugfixes and new translations.

Here is the full changelog in all its glory:

Alex (1):

Fixed spelling error in Quaternion.cs view commit

Allan Nordhøy (9):

Added translation using Weblate (Norwegian Bokmål) view commit
Added translation using Weblate (Norwegian Bokmål) view commit
Added translation using Weblate (Norwegian Bokmål) view commit
Added translation using Weblate (Norwegian Bokmål) view commit
Translated using Weblate (Norwegian Bokmål) view commit
Translated using Weblate (Norwegian Bokmål) view commit
Translated using Weblate (Norwegian Bokmål) view commit
Translated using Weblate (Norwegian Bokmål) view commit
Translated using Weblate (Norwegian Bokmål) view commit

Andrea Aruta (6):

Added translation using Weblate (Italian) view commit
Added translation using Weblate (Italian) view commit
Added translation using Weblate (Italian) view commit
Translated using Weblate (Italian) view commit
Translated using Weblate (Italian) view commit
Translated using Weblate (Italian) view commit

Charles Woodhill (1):

[UI/INPUT] Expose mouseOverElement view commit

Christian Georgiev (2):

Added translation using Weblate (Macedonian) view commit
Translated using Weblate (Macedonian) view commit

Cody Lee (4):

Added issue templates for bugs and feature requests (#327) view commit
Moved pull_request_template.md to correct location view commit
Removed any pluralization of the word question in the question_request.md for consistency view commit
Updated CONTRIBUTING.md and added a ‘submitting changes’ section view commit

Daniel Keenan (2):

Change the ObjectToTypeName value converter to give prettier C# names. (#400) view commit
[GameStudio] Improve “Add component” button usability. (#411) view commit

Dominik Jančík (6):

Initial SDL Finger Multitouch support view commit
Removed lastCtrl field view commit
FingerSDL GUID view commit
FingerSDL PointerID generator view commit
Renamed FingerSDL to PointerSDL view commit
SDL Touch>Mouse synth. disabled when PointerSDL is used view commit

Eideren (55):

Include nuget to proj view commit
Straightforward changes view commit
Potentially harmful changes view commit
Minor proj update view commit
Matrix conversion fix view commit
Main conversion done, next up the rest of the CharacterComponent view commit
Character component, waiting on bullet wrapper for the rest view commit
Static mesh base view commit
Static Mesh: Update shape factories view commit
[Core] ThreadPool: shutdown idle threads (#302) view commit
[Samples] Misc camera controller fixes (#359) view commit
Fix for #422 view commit
Revert nugget view commit
[Bullet] Update libs view commit
[Bullet] Update projects mapping view commit
[Bullet] Remove bullet refs within mathematics view commit
Merge branch ‘master’ into bulletsharp_nuget view commit
[Bullet] Rely on our bullet for math conversions view commit
[Bullet] Finish height field mappings view commit
[Physics] Remove unused enum and previous namespace import for inlining view commit
[Bullet] Update all platforms to latest libs view commit
[Physics] Reduced physics test allocations (#443), cleaned up Simulation view commit
[Physics] Implement ignore collision between two specific components view commit
[Physics] In-editor static mesh collider view commit
[Physics] Avoid duplicate allocations for colliders based on models view commit
[Physics] Fix initial collider scaling view commit
[Misc] Exception prone basic functions view commit
[Transform] Deal with ChildrenCollection todo view commit
Merge branch ‘master’ into bulletsharp_nuget view commit
[Physics] Use asset cloner for shape desc view commit
Merge remote-tracking branch ‘origin/master’ into bulletsharp_nuget view commit
[Physics] Replace ColliderShapes’ TrackingCollection view commit
[Physics] Replace Rigidbody’s hacky delegate usage view commit
[Physics] Rollback unused serialization workaround view commit
[Physics] Cleanup RigidbodyComponent view commit
[Physics] Clarify comments in StaticMeshColliderShape view commit
[Physics] Fix #463 view commit
[Physics] Fix very large meshes throwing view commit
[Physics] Expose Capsule’s readonly data view commit
[Physics] Provide read access to collider shape’s data view commit
[Physics] Split static mesh collider into new PR view commit
[Physics] Fix ShapeSweeps output view commit
[Physics] Provide public access to callbacks’ recycle and buffer view commit
[Physics] Clarify bullet lib’s usage and sources view commit
[Editor] Fix orbit editor camera stutter view commit
[Editor] Re-order code execution view commit
[SceneManagement] Assign Entity.sceneValue before firing events view commit
[Camera] Fix processor’s cameraSlotsDirty not being reset after process view commit
[SceneManagement] Fix loop skipping items when collection is modified view commit
Avoid unnecessary alloc view commit
Deal with Add(), sub-optimal implementation view commit
[Threading] ThreadPool refactor, reduce allocation, fix wrong argument view commit
Move PooledDelegateHelper outside lock view commit
Swap task factory view commit
[GameSystems] Fix removing systems not clearing it from update and draw view commit

Eric Tuvesson (1):

Assets Compiler Support MSBuild Toolset Version 16.0 (#421) (fixes #420) view commit

Félix Dion-Robidoux (1):

Update BACKERS.md view commit

Hyperpred (1):

Remove cast to Game in AudioSystem (#472) view commit

Jarrett Robertson (1):

Fixed issue with scene instance using the wrong collection in for loop count view commit

Louies (10):

Added translation using Weblate (Chinese (Traditional)) view commit
Added translation using Weblate (Chinese (Traditional)) view commit
Added translation using Weblate (Chinese (Traditional)) view commit
Added translation using Weblate (Chinese (Traditional)) view commit
Translated using Weblate (Chinese (Traditional)) view commit
Translated using Weblate (Chinese (Traditional)) view commit
Translated using Weblate (Chinese (Traditional)) view commit
Translated using Weblate (Chinese (Traditional)) view commit
Translated using Weblate (Chinese (Traditional)) view commit
Translated using Weblate (Chinese (Traditional)) view commit

Lucifer (8):

Added translation using Weblate (Chinese (Simplified)) view commit
Added translation using Weblate (Chinese (Simplified)) view commit
Added translation using Weblate (Chinese (Simplified)) view commit
Added translation using Weblate (Chinese (Simplified)) view commit
Translated using Weblate (Chinese (Simplified)) view commit
Translated using Weblate (Chinese (Simplified)) view commit
Translated using Weblate (Chinese (Simplified)) view commit
Translated using Weblate (Chinese (Simplified)) view commit

Mario Guerra (10):

Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit

Moustafa khalil (1):

Update README.md view commit

Nicolas Musset (10):

[Localization] Update extraction script view commit
[Localization] Update extracted strings view commit
[Localization] Update Japanese view commit
[Localization] Add French view commit
[Build] Update solution and project view commit
[Localization] Fix build for path containing spaces (#381) view commit
[Presentation] Bugfix/int3 editor (#387) (fixes #383) view commit
[General] Simplify editor and presentation project files view commit
[General] Fixup rule for .xaml.cs files view commit
Update .gitattributes view commit

Oscar Sanchez (9):

Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit

Phr00t (2):

[Graphics] Vulkan: add support for R10G10B10A2_UNorm and R11G11B10_Float view commit
[Input] Fix mouse VirtualButtons view commit

Polymo (1):

Translated using Weblate (German) view commit

Robin Hübner (2):

[Physics] correct userdoc for convex hull collider parameters. (#382) (fixes #372) view commit
Make SDL window user resizable. view commit

Rui Mendes (3):

Added translation using Weblate (Portuguese) view commit
Added translation using Weblate (Portuguese (Brazil)) view commit
Translated using Weblate (Portuguese) view commit

Scorp-121 (4):

Added translation using Weblate (Russian) view commit
Added translation using Weblate (Russian) view commit
Added translation using Weblate (Russian) view commit
Added translation using Weblate (Russian) view commit

Scorp121 (10):

Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit
Translated using Weblate (Russian) view commit

SleepyMode (1):

[Mathematics] Fixes for Color/ColorRGBA float/byte mismatches (#258) (fixes #251) view commit

Swann Martinet (2):

Translated using Weblate (French) view commit
Translated using Weblate (French) view commit

Tebjan Halm (6):

Quick fix as suggested by @xen2 in chat to avoid crash in shader compiler (#343) view commit
Added translation using Weblate (German) view commit
Translated using Weblate (German) view commit
Resetting shader key scope for multi pass materials (#456) view commit
added xenko-community-project to README.md (#514) view commit
Fix DataBaseFileProvider cast (#538) view commit

Virgile Bello (510):

[Design] VisualStudio.Project doesn’t need a reference to Solution anymore view commit
[Assets] Package can now also represent a csproj + package (only new game creation is working) view commit
[Assets] Removed AssetItem.SourceProject view commit
[Assets] Move assets to Assets folder for now view commit
[Assets] Fix project loading view commit
[Assets] Simplified Package.Profiles into Package.Profile view commit
[Assets] Removed PackageProfile.ProjectReferences view commit
[Assets] Removed PackageProfile.Name view commit
[Assets] Allow creation of samples (as long as they don’t use external packages) view commit
[Assets] Added the concept of Package container (project or standalone) view commit
[Assets] Turned Session.Packages into a readonly collection view commit
[Assets] Properly process dependency graph using remote info to perform package upgrades before downloading nuget packages view commit
[Assets] Removed LocalDependencies and fixed TemplateSampleGenerator view commit
[Assets] Fix platform update view commit
[Assets] AssetCompiler now works against .csproj view commit
[Assets] Fixed asset compiler get-graphics-platform view commit
[Assets] Fix view models to allow selection as current project view commit
[Assets] Properly regenerate platforms for sample templates view commit
[Assets] Ignore assets from executable projects (computed automatically) view commit
[Templates] Moved template packs assets from Assets/Shared to Assets view commit
[Assets] NewGameTemplateGenerator: assets were loaded twice, resulting in issues later with cloned AssetItem (fix asset packs) view commit
[Templates] Simplify platform projects view commit
[Templates] Moved templates packges asset folders from Assets/Shared to Assets and removed intermediate solution folders view commit
[Assets] Adjust PackageProfile.ResourceFolders during package upgrade view commit
[Templates] Sample Templates now works (asset packs are now ProjectReference and their assets are properly copied during template generation) view commit
[Assets] Properly get namespace from project view commit
[Assets] Fix CodeViewModel to use ProjectCodeViewModel view commit
[Assets] Fix platform updates view commit
[Assets] Rearranged templates for the new xkpkg = csproj change (note: project delete is broken) view commit
[Assets] Package.Profile is now properly deserialized by discarding default value view commit
[Assets] Removed PackageProfile.Platform view commit
[Build] Make sure Package.Id stays is in sync with .sln one view commit
[Assets] Removed Package.Id view commit
[Assets] Removed PackageProfile view commit
[Assets] Stop adding default folders in Package ctor view commit
[Assets] Reunified ProjectState and PackageState view commit
[Assets] Moved Package.Save() to PackageContainer.Save() view commit
[Assets] Avoid creating .xkpkg for projects without one in the first place (use implicit one instead) view commit
[Assets] Rework package dependencies view commit
[Assets] Also support loading sln with new csproj Guid view commit
[Assets] Support Packing and consuming simple NuGet packages with Xenko assets view commit
[Assets] New game template: set current project to Windows view commit
[Assets] Simplified NuGet package restore (only happens during PreLoadPackageDependencies) view commit
[Assets] Update Code library template to match others view commit
[Targets] Stop using XenkoDir.cache file during build view commit
[Build] Bump to 3.1.0.1 view commit
[Assets] Store pendingPackageUpgrades in PackageSession view commit
Merge remote-tracking branch ‘origin/master’ into onecsproj_onexkpkg2 view commit
Merge branch ‘master’ into onecsproj_onexkpkg2 view commit
[Assets] Process dependencies for RootAssets in view model view commit
[Assets] Made !file and !directory tags mandatory in Yaml for easier dependency analysis view commit
[Assets] Temporary fixes for root assets and default scene opening view commit
[Assets] Pack assets using actual package data rather than hardcoded rules view commit
[Build] Reorganize build system (WIP) view commit
[Build] NuGetAssemblyResolver WIP view commit
[Engine] Move default assets to individual assemblies rather than global Xenko.xkpkg view commit
[Assets] Compiler: can now properly compile existing projects view commit
[Launcher] Fix launcher build view commit
[Editor] Temporarily moved game studio shaders to Engine, until we have proper design-time package references view commit
Merge branch ‘master-3.0’ into onecsproj_onexkpkg2 view commit
[Build] Use RuntimeIdentifier to separate graphics API runtimes view commit
[Build] Improved cross compilation view commit
[Build] Renamed XenkoRuntime into XenkoNETRuntime view commit
[Build] Added XenkoRuntime flag view commit
[Assets] project.Type evaluation needs to be done after package are restored view commit
[Assets] Reorganized templates view commit
[Assets] Fix package upgrader view commit
[SpriteStudio] Added templates view commit
[Assets] Properly find ffmpeg.exe and msdfgen.exe view commit
[Assets] Move VHACD to Assets assembly and properly bundle C# wrapper view commit
[Assets] Compiler: use thread-safe version of NuGet (when writing lock file) view commit
[Deps] Switched to NuGet version of Xceed.Wpf.Toolkit/Datagrid/AvalonDock view commit
[Build] Bump to .NET 4.7.2 view commit
[Build] Adjust bindings for System libraries with 4.7.2 changes view commit
[Deps] Xenko.Metrics and Xenko.CrashReport are now packaged with NuGet view commit
[Build] Lot of adjustments for new NuGet resolver system (incl ConnectionRouter, VS Package, etc…) view commit
[Samples] Moved samples from Xenko.Assets.Presentation to a dedicated project to have faster rebuild view commit
[Assets] Some improvements so that unit tests can compile view commit
[Assets] Some improvements so that unit tests can compile view commit
[Build] Removed XenkoDir environment variable view commit
[Assets] Fixed templates to have proper assembly names and namespaces view commit
[Build] Readded support for UWP view commit
[Build] Readded support for Android view commit
[Build] Readded support for iOS view commit
[Build] Optimized ProjectReferences view commit
[Build] Check Visual C++ Runtime is properly installed as part of build targets view commit
[Build] Added Xenko.PackageInstaller to Xenko.GameStudio view commit
[Build] Use “XenkoPlatforms” to specify which platforms to build view commit
[NuGet] Upgrade to 4.9 and use RestoreRunner to have faster noop restore on second run view commit
[Tests] Fix build of some test projects view commit
[Build] Also deletes .nupkg.metadata on package auto deploy (https://github.com/NuGet/Home/wiki/Nupkg-Metadata-File) view commit
[Build] Make sure user projects are always built so that compiler app is checking assets again (until we feed “fast up to date” with proper inputs/outputs) view commit
[Assets] Make sure to explicitly include Xenko.Core for its targets until VS2019 enables it by default (https://github.com/NuGet/Home/issues/6091#issuecomment-438073285) view commit
[Assets] Don’t include package targets when evaluating project files view commit
[Assets] Order windows executable project first in solution files (sln) so that VS uses them as startup project by default view commit
[Build] Added some docs related to new build system view commit
Merge remote-tracking branch ‘origin/master’ into onecsproj_onexkpkg2 view commit
[Build] Fix iOS solution view commit
[Build] Moved PackAssets task in Xenko.Core.Tasks view commit
[Build] Use PackAssets as an exe rather than a Tasks so that MSBuild doesn’t lock the files (annoying when rebuilding) view commit
[NuGet] Log everything view commit
[NuGet] Restore inside assembly resolver to avoid deadlock and rewrote logging code view commit
[Build] Only build default graphics platform when opeining sln unless we explicitly set XenkoGraphicsApiDependentBuildAll view commit
[NuGet] Perform nuget resolve only for entry assembly view commit
[Assets] Better resolution of project platform (needed so that windows project is auto selected) view commit
[Build] Fix build when choosing a single graphics API view commit
[NuGet] Add dev store before trying to restore packets view commit
[Build] Removed Xenko.xkpkg view commit
[Build] Moved PackageUpdateVersionTask to a separate assembly to simplify build view commit
[Build] Unify version management in a single file (except for samples which will be versioned separately) view commit
Merge remote-tracking branch ‘origin/master-3.0’ view commit
[Build] Added package details view commit
[Build] Output nupkg in bin\packages view commit
[Build] Xenko.Samples.Templates: add missing dependency view commit
[NuGet] If restore failed, try to kill known blocking processes (Connection Router, CompilerApp, etc…) view commit
[NuGet] Improve logging if restore failed view commit
[Build] Remove non-existing files from Xenko.sln view commit
[NuGet] Use SourceCacheContext to avoid ArgumentException view commit
[Build] Sign dll/exe when building package view commit
[Build] Also sign Launcher executables view commit
[Build] Escape/Unescape XenkoPlatforms for properly passing info from Xenko.build to targets view commit
[Build] Package build improvements view commit
[Build] Package build improvements (part 2) view commit
[Build] Signing tool was mistakently always enabled view commit
[Build] Package build improvements (part 3) view commit
[Setup] Update to Advanced Installer 15.5.1 view commit
[Build] Remove invalid character from Xenko.build view commit
[Build] Fix Linux Vulkan build view commit
[Build] Added bin/packages/.gitignore file view commit
[Build] Fix restore phase in Xenko.build view commit
[Build] Removed Xenko.SamplesBootstrapper and fixed Xenko.Samples.Tests view commit
[Samples] Fixed Xenko.Shaders.Tests view commit
[Build] Use active build configuration rather than forcing Debug view commit
[Build] Stop using Bin\Windows for unit tests view commit
[NuGet] Couldn’t resolve EnvDTE.dll view commit
[Assets] Don’t try to load vcxproj as package view commit
[Samples] PhysicsSample: Update for Vector3 Gravity view commit
[Tests] Xenko.Assets.Tests: Don’t compile assets view commit
[Tests] Fixed some unit tests view commit
[Tests] Fixed folder for gold image view commit
[Launcher] Ignore server-side dev packages view commit
[Assets] Fixed TestBasicPackageCreateSaveLoad view commit
[Assets] Package upgrade is now working for 3.0 projects view commit
[NuGet] Update to NuGet 4.9.1 view commit
[Launcher] Ignore invalid NuGet sources (404, 401, etc…) view commit
[VSPackage] Fix build of test project view commit
[Launcher] Bump to 3.0.1 view commit
[Assets] User can now create GameSettings freely (need to display warning if nothing matching expected name?) view commit
[CompilerApp] Removed unused GetGraphicsPlatform code view commit
[Build] Removed obsolete target files view commit
[Build] Xenko.build now properly build Launcher view commit
[Build] Switching unit tests to new targets view commit
[VSPackage] Fix Xenko.build targets view commit
[Build] Clean packages before full package build view commit
[GameStudio] Asset editors close button is back view commit
[Graphics] Removed PreferredGraphicsPlatform from RenderingSettings view commit
[VSPackage] Fix build when using multiple XenkoPlatforms view commit
[Build] Adjust package versioning so that NuGetVersion doesn’t contain build metadata view commit
[Native] Explicitly require related Assembly when loading native library (we can’t use GetCallingAssembly as it might be wrong due to optimizations) view commit
[Native] PreloadLibrary: Use type rather than assembly (to avoid use of GetTypeInfo() everywhere) view commit
[GameStudio] About page: added markdown files to package view commit
[Launcher] Few fixes so that launcher properly separate view commit
[GameStudio] About page: display version with build metadata view commit
[Build] Force cross-targeting if there is multiple RuntimeIdentifiers view commit
[Launcher] Stay compatible with Xenko 1.x/2.x view commit
[Build] Properly fix how RuntimeIdentifier is used for multi graphics API per platform view commit
[Assets] Solution file was generated with empty DefaultVisualStudioVersion view commit
[OpenTK] Use win7 runtime rather than win view commit
[Assets] Made DefaultVisualStudioVersion public again view commit
[Build] Properly forward XenkoGraphicsApiDependentBuildAll view commit
[Build] Workaround: Remove RuntimeIdentifier from Solution references (https://github.com/onovotny/MSBuildSdkExtras/issues/139) view commit
[Assets] Make sure solution/project path use backslashes view commit
[Particles] Remove ambiguities in data member order view commit
[Assets] Keep solution folders, just remove package info view commit
[Assets] Improve package upgrade when there is no ProjectReference view commit
[Samples] Updated samples view commit
[Samples] Removed Xenko.Navigation where not needed view commit
[Samples] Removed Xenko.Physics where not needed view commit
[Assets] Make sure implicit packages have IsDirty set to false when loaded view commit
[Assets] Fix asset upgrade view commit
[GameStudio] Fixed template samples generator to work with updated project format view commit
[Samples] Updated with 3.1 (step 2) view commit
[Samples] Keep Xenko.Particles for now, until we have better extensibility in Graphics Compositor view commit
[Assets] Allow some assets to be non-referenceable (asset name collision is allowed in this case because they exist only at compile-time). This is used for scripts, otherwise they can’t have same name as an asset. view commit
[Assets] PackAssets: skip excluded files view commit
[Settings] Remove the !file when serializing setting keys view commit
[Build] Package necessary WindowsAPICodePack assemblies with Xenko.Core.Presentation.Dialogs view commit
[Build] XenkoPlatform was not properly set for Linux platforms view commit
[Assets] PackageUpgrader: react to multiple package names (to support renames and/or package splits in multiple parts) view commit
[GameStudio] Improve default asset selection to match opened asset editors view commit
[Assets] Compiler: Move default asset build path to obj\xenko\assetbuild view commit
[Build] Changed dev/beta versioning to permit upgrading between interleaved dev and beta releases (betaXX.YYYY format with XX = asset version and YYYY = git height) view commit
[Build] Generate ref folder for all platforms (otherwise Android/iOS/UWP might fallback to ref/netstandard2.0 of Linux) view commit
[Build] Fix Android build due to lack of NuGetRuntimeIdentifier view commit
[Templates] Remove the _Game from sample templates view commit
[Build] Adjust PackageVersion for sample templates according to XenkoOfficialBuild rather than XenkoPackageBuild view commit
Updated BACKERS.md view commit
[Launcher] Display source in tooltip for Xenko downloads view commit
[VSPackage] Various fixes so that shader highlighting/goto works view commit
[Build] Updated UWP to use uap10.0.16299 view commit
[UWP] Simplified some code (can now use Thread and other newer API) view commit
[Build] Hide Microsoft.NETCore.UniversalWindowsPlatform from references and update build doc view commit
[Build] Fix Xenko.Shaders.Tests name view commit
[Assets] New Game template was not properly copying asset package files view commit
[GameStudio] Use same build folder for game studio as for actual game build view commit
[Templates] Fixed Linux template view commit
[Templates] Fixed UWP template view commit
[Build] Use win instead of win7 runtime identifier view commit
[Templates] Additional fix for Linux template view commit
[Templates] Linux: adjust default runtime identifier view commit
[Launcher] Various fixes for downloading and error reporting view commit
[Launcher] Bump to 3.0.4 (3.0.3 was built with incorrect source changes) view commit
[VSPackage] Fix NuGet assembly resolve (avoid infinite loop) and handle properly non-Xenko solutions (fixes #298) view commit
[Editor] Properly report solution load/save exception to log view commit
[Reflection] Rewrote part of AssemblyContainer to handle deferred loading view commit
[Build] Updated to MSBuild.Sdk.Extras version 1.6.65 (compatible with VS2019) view commit
[Build] Use $(RoslynTargetsPath) rather than $(MSBuildBinPath)\Roslyn (which doesn’t work with VS2019) view commit
Change link+badge for chat from gitter to discord view commit
[Build] Use netstandard2.0 version of OpenTK view commit
[Build] Switch to netstandard2.0 wherever possible for the runtime view commit
[Build] Switch game projects to use netstandard2.0 view commit
[Build] Fix Windows+Linux build view commit
[Build] Hide Microsoft.NETCore.UniversalWindowsPlatform from references and update build doc view commit
[Build] Fixed build of RenderDocPlugin view commit
[Build] Additional fixes for single 3d graphics API build mode view commit
[Templates] Patching of TargetFramework section is now forcing netstandard2.0 view commit
[Templating] Switch to latest version of Mono.TextTemplating (t4) and add reference to netstandard view commit
[Build] Various fixes for .NET Standard build view commit
[Build] Bump Android SDK version from 5.0 to 8.1 (Google Play recent requirement for new app and .NET Standard 2.0 also requires 8.0+) view commit
[Build] Force references to be added only for direct and explicit package references view commit
[Build] Properly forward XenkoGraphicsApi when building a single graphics platform view commit
[Build] Make sure to override RuntimeIdentifiers on UWP otherwise it builds all CPU versions and result in write conflicts view commit
[Build] Use “any” instead of “win” view commit
[Build] Make sure “win” is the default when building a netstandard2.0 reference (to make sure a RID-specific project always use RID) view commit
[Build] Define output path (otherwise using a Platform might override them) view commit
[Build] Properly setup RuntimeIdentifier if it was not a Graphics-API-specific one view commit
[Build] Pack Xenko assets as part of NuGet packaging view commit
[Build] Fix the NuGet publish build file view commit
[Build] Removed unnecessary solution references view commit
[Build] Properly compute & restrict RuntimeIdentifier for ProjectReference view commit
[Build] Better detection of default RuntimeIdentifiers view commit
[Build] Fix RuntimeIdentifiers detection for graphics API mode view commit
[Build] Adjust RuntimeIdentifier and XenkoPlatform detection view commit
[Launcher] Remove custom Http code and decrease concurrency (which might be problematic since our packages are bigger than average) view commit
[Launcher] Switch from gitter to discord view commit
Updated BACKERS.md view commit
[Launcher] Bump to 3.0.5 view commit
Update Crowdin configuration file view commit
Update Crowdin configuration file view commit
[Launcher] Skip unlisted packages, and don’t use cache view commit
[Launcher] Also use normal output data for error output of PackageInstall.exe view commit
[Physics] Enable PhysicsShapesRenderingService only if there is a IGraphicsDeviceService view commit
Update BACKERS.md view commit
Merge remote-tracking branch ‘origin/master-3.0’ view commit
[Physics] Add comment for PhysicsShapesRenderingService creation view commit
[Build] Added option XenkoPublishSkipSamplesTemplates view commit
[Build] Adjust platform detection (broken for multiplatform) and preparations for OSX view commit
[Build] Additional fixes for computing runtime identifiers view commit
[Build] Further fixes for computing runtime identifiers view commit
[Build] Run Visual C++ checks only on .NET Framework MSBuild view commit
[Build] Additional setup for macOS build view commit
Merge pull request #323 from Kryptos-FR/feature/l10n view commit
[Build] Native: Generate only x64 for macOS (.NET Core only supports x64) view commit
[Graphics] Update to SDL 2.0.9 view commit
[Graphics] SDL: Load from proper directory view commit
[Shaders] Added macOS glslangValidator view commit
[Shaders] Vulkan: Add “NoSampler” to reflection view commit
[Core.IO] Disable LockFile code from macOS (not supported) view commit
[Core] Copy native libs for more platforms, and only if CopyLocalLockFileAssemblies is not set to false view commit
[Build] macOS: Update NativePath to latest version view commit
[Graphics] Update SharpVulkan (works on OSX and easier to access NativeHandle) view commit
[Graphics] macOS: Added MoltenVK view commit
[GameStudio] Added project template for macOS view commit
[Localization] Use $(RoslynTargetsPath) rather than $(MSBuildBinPath)\Roslyn (which doesn’t work with VS2019) view commit
[Samples] Templates: Added Cache to list of ignored folders (can be leftover from build during previous Xenko versions) view commit
[Graphics] macOS: Updated MoltenVK view commit
[Assets] PackAssets: Use proper asset path when computing resources relative paths (fixes #326) view commit
[VSPackage] Upgrade version to 3.0.3. Add support for VS2019. New release needed since RestoreHelper.cs was updated (fixes #324) view commit
Update license for 2019 view commit
Update BACKERS.md view commit
[Build] Copy .xml and .pdb from NuGet package references when using new csproj format view commit
[VSPackage] Run VSIX installer only for VS2017+ (fixes #332) view commit
[Build] Use latest version of Windows 10 SDK view commit
[Build] Update requirements view commit
[Build] Publish was not properly copying native libs and compiled assets (fixes #331 and #334) – thanks to jazzay for the initial implementation view commit
[VSPackage] Make ProjectReference between Commands and Package private so that it doesn’t exist as a NuGet dependency view commit
[VSPackage] Add TODO for restore log view commit
[Build] Native: use vcxproj directly to avoid TRK0005: Failed to locate: “link.exe” or “cl.exe” (fixes #337) view commit
[Build] Properly include install-prerequisites.exe next to Xenko.GameStudio packageinstall.exe view commit
[Install] Prerequisites installer: improve error reporting and retries (i.e. UAC not clicked) when installing Visual Studio or Build Tools view commit
[Install] Prerequisites: Update to VC++ 2017 prerequisites view commit
[Install] Prerequisites: Add “.NET Core 2.1 development tools” to list of Visual Studio prerequisites view commit
[Install] Prerequisites: Improve Visual Studio detection/update mechanism view commit
Update BACKERS.md view commit
[GameStudio] Switch to Roslyn 2.10 view commit
[Assets] PackAssets: properly copy RootAssets (fixes #347) view commit
[Assets] Perform null check before upgrading PackageProfile view commit
[Assets] PackageSession: Properly fallback to AssemblyName if PackageId is not set view commit
[Assets] Remove asset upgrader code for versions before 3.0 view commit
Explain how CLA is to be signed. view commit
Update BACKERS.md view commit
[Build] NuGetVersion reported to TeamCity was wrong view commit
[VR] Fix UWP build (#213) view commit
[Build] Add XenkoBuildDoc parameter to force TargetFramework even if not specified (seems necessary for older version of Roslyn used in docfx) view commit
[GameStudio] Add missing RoslynPad assemblies in the composition context view commit
[GameStudio] Allow drag & dropping of read-only assets (as long as they wouldn’t be modified) view commit
[GameStudio] CodeLibrary projects were not properly initialized (assets couldn’t be created) view commit
[Build] Sign packageinstall.exe view commit
[Build] Include RoslynPad assemblies with Xenko.Assets.Presentation package view commit
Update ContributorLicenseAgreement.md view commit
[Build] Unlocking C# 7.3! view commit
[Core.Design] AssemblyContainer: Process deps.json files (fixes #365, fixes #342) view commit
Merge branch ‘master-3.0’ view commit
[Physics] Fix ColliderShapeAsset upgraders (was previously enclosed in XENKO_SUPPORT_BETA_UPGRADE) view commit
Merge remote-tracking branch ‘origin/master-3.0’ view commit
Merge remote-tracking branch ‘origin/master-3.0’ view commit
[Build] Add option -NoSymbols to nuget push view commit
[Graphics] D3D: add support for using typeless textures view commit
[Reflection] AssemblyContainer: return already loaded assemblies if AssemblyName matches rather than loading new one (it seems that assembly is requested several times because we are not loading in the proper load context) view commit
[Build] runtime.json: fix spacing view commit
[Build] Added new CPU-specific variants to runtime.json (#370) view commit
[Build] Bumped LLVM to 7.0.1 view commit
[Render] Decouple RenderParticleEmitter from ECS view commit
[Render] Decouple RenderUIElement from ECS view commit
[Render] Decouple RenderMesh and others from ECS view commit
[Rendering] Remove various dependencies from lighting code to LightComponent view commit
[Rendering] Removed SceneInstance dependency from rendering code view commit
[Rendering] Removed dependency from VisibilityGroup to ShadowMapRenderView view commit
[Rendering] LightSkybox: Removed obsolete comment view commit
[Rendering] Moved RenderGroup class to Rendering namespace view commit
[Rendering] PostFX: remove dependency to CameraComponent view commit
[Rendering] ShadowMapRenderer: remove unused nested class view commit
[Rendering] ForceAspectRatioSceneRenderer: Made default aspect ratio local to remove dependency to CameraComponent view commit
[Engine] Moved IndexingDictionary to Xenko.Core view commit
[Rendering] EffectSystem: Remove dependency to Game class and move EffectCompilationMode in the same namespace view commit
[Rendering] EffectSystem: Moved CreateEffectCompiler in a separate static class outside of Rendering code view commit
[Rendering] Made ForwardLightingRenderFeature not dependent on LightProcessor anymore view commit
[Rendering] Made LightProbe code not dependent on LightProbeProcessor anymore view commit
[Rendering] Made LightShafts independent from LightShaftProcessor view commit
[Rendering] Fixed RenderContext.GetCurrentCamera() tag owner view commit
[Streaming] Removed dependency on Engine.Game view commit
[Rendering] Splitted most of low-level rendering code into a new Xenko.Rendering assembly view commit
[SpriteStudio] Fixes for SpriteStudio to work properly again view commit
[Rendering] Make Xenko.Rendering platform-specific view commit
[TextTemplating] T4: use a custom version of Mono.TextTemplating, including https://github.com/xen2/t4/commit/0d0b6db3ca3aba82fd7597951be2361265043e5e view commit
[Serializaton] Bump format version (Rendering split) view commit
[Build] Bump to beta02 view commit
[Build] Fix .usrdoc generation and copy (fixes #377) view commit
[NuGet] Remove deleted xenko sources during startup to avoid restore failures (fixes #338) view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[Localization] Added Russian as a supported language view commit
[Localization] Added a few missing important translations (which were omitted for ApplicationCommands) view commit
[CrashReport] Bumped crash report to 1.0.1 (force HTTPS), anonymize reports and make sure it doesn’t conflict with NuGetAssemblyResolver view commit
[Localization] Updated po files view commit
[Build] Regenerated sln (which were invalid since Xenko.Rendering was added) view commit
[Samples] Removed reference to RenderContext.SceneInstance (fixes #386) view commit
Merge remote-tracking branch ‘weblate/master’ view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[Localization] Only generated when building Release, and added Russian in Xenko.Editor view commit
[Localization] Added support for German and Spanish view commit
[Localization] Rearranged targets so that localization code is unified view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[Localization] Added support for Chinese (Simplified) view commit
[Setup] Don’t delete top level installation folder if not empty (esp. if it was installed in a root folder containing other programs by mistake!) view commit
[Launcher] Use cache but always refresh it, even when installing. view commit
[Launcher] Set LauncherApp as default project view commit
[Launcher] Bump to 3.0.6 view commit
[Templates] Fix version in reference to Xenko.Samples.Templates package view commit
[Rendering] Add Sprite to rendering only if it’s enabled view commit
[Rendering] Properly register Xenko.Rendering in AssemblyRegistry (fixes #409 and fixes #410) view commit
Update BACKERS.md view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[GameStudio] Fast-reloading for types such as Material and Texture were not working as expected, forcing a full model reload on every edit view commit
[GameStudio] Fix for fast-reloading view commit
[GameStudio] Rewrote and simplified code for fast reloading (also support cases such as material layers properly now) view commit
[GameStudio] AvalonDock: Fix a bug in AvalonDock 3.4.0 which sets CanClose to false once a LayoutAnchorable is dragged into a new floating window or a new pane. view commit
[Physics] CleanContacts was working on previousFrameContacts rather than currentFrameContacts, resulting in warnings “Pair not present”. Thanks @EternalTamago for the fix! (fixes #88) view commit
Update BACKERS.md view commit
[Graphics] D3D11: Begin/End were not reentrant because of how Query were used (#427 #428) view commit
Merge remote-tracking branch ‘origin/master-3.0’ view commit
[Audio] Encode little bit longer to compensate for encoding delay (fixes #350) view commit
[Build] Make sure _XenkoGenerateDependencies runs in all situations (otherwise unit tests won’t work) view commit
[Build] Make sure _XenkoGenerateDependencies runs also for C++ projects view commit
[Build] Readjust _XenkoGenerateDependenciesAfterBuild target/comments view commit
[Build] Unit tests: use proper xunit.console.exe depending on x86 or x64 view commit
[Tests] Fix sample games unit tests view commit
[Samples] Fix Sprite Studio demo (missing reference to SpriteStudio runtime) view commit
[Editor] Preview View Model was not properly removing event handlers (fixes #438) view commit
[Launcher] Improve log/error message in an attempt to investigate #310 view commit
[NuGet] Switch to NuGet 5.0 view commit
[Build] Require VS2019 instead of VS2017 to take advantage of new NuGet buildTransitive feature view commit
[Build] Removed obsolete props files view commit
[Build] Update NuGet.exe to 5.0 view commit
[Build] Update build instructions view commit
[VSPackage] Update to new AsyncPackage and upgrade/cleanup unecessary PackageReference view commit
[Build] Bump MSBuild.Sdk.Extras to 2.0.24 view commit
Merge remote-tracking branch ‘origin/master’ into vs2019 view commit
[AssemblyProcessor] Fix a case where ImportReference was not called for GetTypeFromHandle(). Bumped Cecil to NuGet 0.10.3 rather than custom one. view commit
[Assets] Added a new KeepReferences flag to AssetCloner view commit
[Build] Stop detecting Android NDK version using folder name (latest VS2019 uses “ndk-build” folder name without version) view commit
[Build] VS2019 now understand WindowsTargetPlatformVersion being set to 10.0 rather than a specific version. Also bump PlatformToolset to v142 view commit
[Build] Converted some design-time libraries to .NET Standard 2.0 view commit
Revert “[AssemblyProcessor] Fix a case where ImportReference was not called for GetTypeFromHandle(). Bumped Cecil to NuGet 0.10.3 rather than custom one.” view commit
[AssemblyProcessor] Fix a case where ImportReference was not called for GetTypeFromHandle(). view commit
[Assimp] Added error details if something went wrong (and test if scene is null to avoid NullReferenceException). view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[Build] Reorganized targets to more easily choose multiple graphics platforms at once. view commit
[Build] Bumped sln to use VS2019+ view commit
Revert “[Build] Reorganized targets to more easily choose multiple graphics platforms at once.” view commit
[Build] Reorganized targets to more easily choose multiple graphics platforms at once. view commit
[Build] Removed deprecated Android armeabi CPU architecture (fixes #461) view commit
[Vulkan] Back buffer: add missing ViewType parameter (2D) when creating back buffer view commit
[Build] Android: Bump TargetSdkVersion to API level 27 (matches VS2019 install and TargetFrameworkVersion set in csproj) view commit
[Launcher] NuGet: 1 hour timeout instead of 100 seconds as a workaround for https://github.com/NuGet/Home/issues/8120 (fixes #310) view commit
[Launcher] Bump to 3.0.8 view commit
Revert “[Assimp] Updated assimp to official 4.1.0 and updated references in projects (closes #458)” view commit
[Build] Removed armeabi libraries to completely fix #461 (fixes #470) view commit
[Build] Android: unify all minSdkVersion to 16 and targetSdkVersion to 27 (fixes #469) view commit
[VSPackage] Bump to 3.0.5 view commit
[Physics] Renamed NewShapeFromDesc to CreateShape view commit
[Launcher] Allow to select Xenko version view commit
[Build] Bumped Cecil to NuGet 0.10.4 rather than custom one. view commit
[Physics] Update README.md with new BulletSharpPInvoke repo location view commit
Merge pull request #289 from Eideren/bulletsharp_nuget view commit
[Physics] Fix typo in PhysicsEngineFlags.ContinuosCollisionDetection (fixes #152) view commit
[Build] Properly copy back IntDir/OutDir to IntermediateOutputPath/OutputPath for C++ project view commit
[Input] Fix SDL key mapping for 0 and 1 view commit
[Build] Updated editorconfig to contain VS2019 default style (which we use in Xenko) view commit
[Build] XenkoContent: do not include in NuGet package as Content view commit
[Graphics] Compare InputElements length before comparing elements view commit
[Graphics] Remove unecessary GraphicsDevice.ThreadCount view commit
[SDL] AppActivated and AppDeactivated were reverted view commit
[Vulkan] Fix validation for texture upload view commit
[Vulkan] Update glslang to 7.11.3214 (May 2019) view commit
[Vulkan] PipelineState: Entry point name could be GC before used view commit
[Vulkan] PipelineState: Properly set PrimitiveRestartEnable view commit
Revert “[Graphics] Vulkan: add support for R10G10B10A2_UNorm and R11G11B10_Float” view commit
[Vulkan] Fixed memory barriers for Clear functions view commit
[Vulkan] UpdateSubresource: Fixed memory barrier view commit
[Vulkan] Fixed mixup between Clear DSV and RT view commit
[Build] Android: Updated to NDK r19 (with proper version check) and remove our custom libc++abi (first step for #460 and #379) view commit
[Build] Android: Avoid “error MSB4044: The “FilterAssemblies” task was not given a value for the required parameter “DesignTimeBuild”.” with latest Xamarin.Android view commit
[Audio] Android: Updated OpenSLES header (which were incompatible with arm64 due to SLuint32 mapping to long instead of int) (fixes #379) (fixes #460) view commit
[Setup] Upgraded Visual C++ prerequisites to latest VS2019 ones view commit
[Assimp] Properly copy Xenko.Assimp.*.dll (fixes #465) view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[Build] Android: Workaround for https://github.com/onovotny/MSBuildSdkExtras/issues/174 view commit
[Build] Transformed Xenko.Core.BuildEngine into a .NET Standard assembly view commit
[Build] NETStandard: Switch from AssemblyBuilder.DefineDynamicAssembly view commit
[Build] NETStandard: Remove unnecessary using view commit
[Quantum] Renamed Index into NodeIndex to avoid clash with future System.Index view commit
[Build] NETStandard: Remove unnecessary using view commit
[Assets] Switch from implicit project to explicit project if necessary (fixes #442) view commit
[Build] Switched to MSBuild.Sdk.Extras version 2.0.41 view commit
[Build] Doc: Copy .xml file in ref folder view commit
Revert “[Build] Switched to MSBuild.Sdk.Extras version 2.0.41” view commit
[Build] Moved Microsoft.NETCore.Platforms reference from Xenko.Graphics to Xenko.Core (otherwise scenarios like referencing only Xenko.Core with win-x64 doesn’t work) view commit
[VSPackage] Syntax highlighting service was not properly registered asynchronously (fixes #651651) view commit
[VSPackage] Fix Xenko detection view commit
[VSPackage] Bump version to 3.0.6 view commit
[Build] Replaced to for shaders/effects [view commit](https://github.com/xenko3d/xenko/commit/6553d51fbb0455710a56790d6dccf757309bc0e3)
[VSPackage] Add a launchSettings.json with proper parameters for easier debugging view commit
[Input] SDL: fix OemPlus/Minus mapping (thanks nes) view commit
[UI] Fix comment view commit
[Vulkan] Fix some memory barriers in CommandList.Copy and CopyRegion view commit
[Vulkan] CommandList: Don’t use ImageView.Null in DescriptorImageInfo view commit
[Streaming] Load a few initial mipmaps for streamed texture (otherwise they start as completely uninitialized: bad for rendering, and causes crash on Vulkan) view commit
[Shaders] Fixed precompiled shader code generation view commit
[Shaders] Added ElementType info to reflection for buffers/textures view commit
[Vulkan] Properly store info if a texel buffer need to be integer or float. view commit
[Shaders] Make sure NoSampler is added before computing list of resource groups (otherwise it ends up having no location attribute) view commit
[Input] Fixed copyrights view commit
[VSPackage] Fix Xenko version detection to work not only with nuget packages but also solution projects, so that it works with Xenko solution itself. view commit
Merge remote-tracking branch ‘weblate/master’ view commit
[Localization] Added Italian view commit
[Localization] Added info in doc on how to translate and add new language. view commit
[Build] Remove the -beta02 version suffix view commit
[Shaders] D3D: Properly copy ElementType when duplicating resource binding per stage (fixes #515) view commit
[Samples] Updated to 3.1.0.1 view commit
[Setup] PackageInstall: check if VS Installer needs an update, and if yes try to do it automatically view commit
[Build] Temporary workaround for .NET Core 3.0 new runtime identifier system (credits go to Solr for finding this fix) view commit
[NuGet] Rewrote how assembly resolver is ordering assemblies found in nuget packages (there was a bug where it could select net46 instead of net461, resulting in crash) view commit
[Build] Moved Xenko.Samples.Templates version in a single unified location to simplify future maintenance view commit
[Setup] PackageInstall: Check VS Installer update if any workload needs to be installed (two UAC, but probably better than an error and extra step) view commit
[Build] Bumped MSBuild.Sdk.Extras to 2.0.54 view commit
[Build] Updated codesign certificates view commit
[Build] Android: Use AssemblyName rather than RootNamespace for Resource class otherwise it might clash between some assemblies (i.e. Xenko and Xenko.Engine) –> view commit
Revert “[Build] Remove the -beta02 version suffix” and bump samples accordingly view commit
[Build] Use default RuntimeIdentifier for default GraphicsApi, so that even if our custom RuntimeIdentifier are not merged properly, everything still work. view commit
[Build] Removed previous workaround for https://github.com/NuGet/Home/issues/7351 view commit
[Build] Bump NuGet.exe to 5.3.0 view commit
[Build] Improved behavior of XenkoGraphicsApiDependentBuildAll view commit
Merge branch ‘runtimeid_fixes’ into master-3.1 view commit
[Build] Android: Fix NDB platform versions view commit
[Graphics] Updated SharpDX to 4.2.0 view commit
[UpdateEngine] AssemblyProcessor was generating invalid ldftn for virtual/interface calls (causing crashes with .NET Core 3). Switch to ldvirtftn for those instead. view commit
[Graphics] Update D3D12 code for SharpDX 4.2.0 view commit
[Build] AssemblyProcessor task need to change identity on each change otherwise we can run into https://github.com/microsoft/msbuild/issues/663#issuecomment-310530046 view commit
[Graphics] Streamed compressed texture could end up having their initial texture size not multiple of 4, resulting in error at runtime loading. Skip these cases for now. view commit
[Fonts] Fix how matrix is computed and compute realVirtualResolutionRatio depending on actual requestedFontSize (fixes #314) (fixes #364) view commit
[Fonts] Dynamic fonts: use virtual resolution (otherwise real size changes on every camera move and requests new character, esp. if UI is in 3D) view commit
[Fonts] Do not alter fontSize view commit
[Fonts] Turned various internal parameters from ref to in (C# 7.2) view commit
[Fonts] Turned various internal parameters from ref to in (C# 7.2) (missing file) view commit
[Build] Added a trailing slash at the end of PackageOutputPath (maybe necessary since latest VS2019?) view commit
Revert “[Build] Add XenkoBuildDoc parameter to force TargetFramework even if not specified (seems necessary for older version of Roslyn used in docfx)” view commit
[Build] Separated XenkoGraphicsApis into one list per platform (otherwise we can’t really control properly and risk overriding a platform with nothing) (fixes #544) view commit
[Build] Remove GetSolutionConfigurationContents hack (which was necessary for WinStore/WinPhone port) (this allows command line build for Android/iOS #543) view commit
[Build] Remove the -beta02 version suffix and bump samples accordingly view commit
Updated BACKERS.md view commit

WaldiS (3):

Added translation using Weblate (Polish) view commit
Translated using Weblate (Polish) view commit
Translated using Weblate (Polish) view commit

WhyPenguins (1):

Add output merger UAV binding. (#478) view commit

Yuuki terumi (5):

Added translation using Weblate (Spanish) view commit
Added translation using Weblate (Spanish) view commit
Added translation using Weblate (Spanish) view commit
Added translation using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit

dfkeenan (5):

Allow spaces in TargetDir when building LauncherApp project. view commit
Update Roadmap url to github projects. view commit
Add tooltip status text for link buttons. view commit
Add patreon link to launcher. view commit
Remove AnswerHub link from launcher. view commit

ioc (1): * Fix broken link to Teamcity Android build in ReadMe view commit

joreg (1):

VR tracker support (#213) view commit

meriaizen86 (3):

Translated using Weblate (Spanish) view commit
Translated using Weblate (Spanish) view commit
Update XenkoDefaultSplashScreen.xktex view commit

pansan (1):

Translated using Weblate (Chinese (Simplified)) view commit

phr00t (2):

Make alpha optional in Color4 view commit
[UI] don’t invalidate text UI if we set it to the same thing view commit

rgawry (1):

Translated using Weblate (Polish) view commit

ssantos (1):

Translated using Weblate (German) view commit

tebjan (4):

[Assimp] Updated assimp to official 4.1.0 and updated references in projects (closes #458) view commit
[Assimp] Updated assimp to official 4.1.0 and updated references in projects (closes #458) view commit
fixed null pointer exceptions in render features view commit
removing a package did not fire an event, so all related assets where still in the dependency manager view commit

xwellingtonx (1):

Fix editor resizing and to insert auto hide minimum size (fixes #189 and #190) view commit

陈宇航 (1):

Translated using Weblate (Chinese (Simplified)) view commit

Generated using git shortlog origin/master-3.0..origin/master-3.1 -w0,0,0 --pretty=format:"* %s [view commit](https://github.com/xenko3d/xenko/commit/%H)" | sed -r "s/#([[:digit:]]*)/[#\1](https:\/\/github.com\/xenko3d\/xenko\/issues\/\1)/g"

October 2019

Thu, 31 Oct 2019 00:00:00 +0000

Hi everyone,

Welcome to our October edition. Here is a quick recap on what’s going on with Xenko development and its community.

Official 3.1 release

The 3.1 was originally scheduled for release this month, but some last minute breaking changes prevented the release. The official release is now in its final testing phases and should be released shortly. Once the release is final, we can focus on planning out tasks and the new roadmap for 3.2.

Git sponsorship

Next to Patreon you can now also sponsor Xenko development directly through Github sponsors. GitHub even doubles the money that is donated the first year up to $5000!

Possible name change

For those of you who have missed it: Xenko is looking for a possible rename of the engine. There have been lengthy discussions on Discord about the name we could pick. See the fixed topic in the Discord #name-change channel.

Documentation

The first tutorial project is almost ready. Users will be able to select tutorial templates from a Tutorial category in the project launcher. The first project “C# Beginner”, demonstrates 12 beginner programming concepts. The amount of tutorials, as well as intermediate and advanced tutorials, will be extended/added once the first release is done. Additionally, the code used in the project is directly referenced by the new documentation section which explains each individual tutorial level.

Community picks

Check out these awesome community projects that people are working on:

Voxel cone tracing based global illumination

User: Spike1

Forum post Github project

Heightmap terrain

User: SilentCLD

Github project

Xenko meets vvvv

Fri, 04 Oct 2019 00:00:00 +0000

Xenko and vvvv

When Xenko went fully open-source in 2018, one of my intent was to be able to engage directly with some of Xenko’s most enthusiast customers and power users. vvvv is definitely a perfect example.

vvvv is a hybrid visual/textual live-programming environment for easy prototyping and development.

vvvv has been using Xenko under the hood for a while, e.g. for the Ocean of Air project.

They also have various plans to leverage Xenko even further in the future gamma version.

That’s what led me to establish closer contact with them. One things led to another, and in May 2019 I jumped in with both feets and moved to Berlin. They’ve been graciously sponsoring Xenko and allowed me to use their office since then.

My sincere thanks to them for supporting both Xenko and me!

Please find vvvv announcement at https://vvvv.org/blog/vvvv-meets-xenko

Code signing certificates

A few days ago, Xenko code signing certificate expired, leaving the project in a tough situation, where smooth releases were not possible anymore.

vvvv graciously offered me to temporarily sign Xenko official releases with their own codesign certificate. So don’t be surprised to see their name popping up next time you upgrade Xenko!

This is only temporary and we are working to get our own code signing certificate as soon as possible. More to come soon on that front!

Contributor Meeting #1

Tue, 01 Oct 2019 00:00:00 +0000

Hi everyone,

Next to the community meetings were everyone can join in on the discussions, we now also have the contributor meetings. These contributor meetings are for the people who are actively participating in Xenko development. Last weekend we had our first gathering. Another thank you to all who participated!

Summary

Date of meeting: 28 September 2019

Official release of 3.1
- The release of 3.1 is imminent. More details on this will be provided soon.
- Nuget package creation is the biggest task to be completed.
General roadmap
- The roadmap currently planned on Github is outdated. It needs to be updated and become more relevant to the capacity we currently have as Xenko contributors/developers.
- New freedcamp tasks will come out of this that can be assigned to contributors. Some areas of contribution:
  - Xenko core (subsystems, frameworks, .Net version etc)
  - Editor improvements
  - Examples/Tutorials: C# coding, Models/materials setup from Import to Scene, Animation
Roadmap for 3.2
- Planning out the next features is a big challenge, because there are so many things wanted/requested. Since Xen is the only full time core developer, we can probably only toggle 1 major feature next.
- After the 3.1 is released the strategy on which core feature should be implemented. This has yet to be decided. The next developer meeting will go deeper in to this.
  - Example on what could be worked on: asset compiling/.NET Core 3
Release cycles
- We will try to adapt a more frequent official release strategy. Even if that official release contains few fixes or improvements. We do not want to plan releases on fixed dates, but instead we do want to keep the 3-4 months idea in our mind. This should provide the community more reliability.
- Depending on the amount of fixes/improvements this will major or minor.
Phr00t fork
- It has proven difficult to merge functionality from phr00t fork to main xenko, but there is ongoing progress!
- 2 users (Fdrobidoux and SilectCLD) are currently working on merging code. If you are interested in following the progress have a look at the task for this.
- Vulkan improvements will need to be done differently, and some work from xen2 has already landed for this.
Documentation
- The C# basics tutorials are making progress, but the sample project is not quite there yet.
- Some better screenshots and a base tutorial scene that looks a little bit more appealing could be really useful.
- Release for this is extended by 1 month.
Access rights:
- We can distribute some access rights among contributors to ofload some of task from Xen.
  - Social media: SyrikZero
  - Website deployment Teamcity/Azure: JornAggror
Name change
- Let’s take it one step at a time: first let’s see what possible name we can come up with.
- Check the voting topic by Eideren for more info.
General topics:
- We are aiming to do a contributor meeting every 2 months.
- This meeting was a long sit: 1.5 hours. Next meetings should be 1 hour at max, but preferable shorter.
- Using Discord for the meeting, was not ideal. We will try to see if we can use Google Hangouts for this.
- The timezone planning of the meeting did not go as planned even though Doodle does support this. This will be properly tested for the next meeting.
- Freedcamp will remain as the tool for planning generic tasks. Since most contributors have now joined, new members can only edit tasks if they are invited.

Want to join the contributors?

Whether you are a developer, designer, artist or writer, you are always free to create Pull Requests or add issues to the Xenko github project. If you are interested in participating in the contributor meetings and the Xenko Freedcamp project, please send a private message to AggrorJorn using the Xenko forum. All you need to do is send in your email address and what areas of contributing you are interested in. You will be invited to join the publicly viewable Xenko Freedcamp project which we use to keep track of all sorts of tasks that people are working on. We can then also have a quick chat to get you up to speed on any tasks.

September 2019

Mon, 23 Sep 2019 00:00:00 +0000

Hi everyone,

Welcome to the September blog post of Xenko. In this blog, we will have a quick recap on what’s going on with Xenko development and its community. From now on we will have a monthly recap blog to let the world know what we are up to.

Picking up speed

Since the last developer meeting in July, it was made clear that Xenko really needs the help of the community to improve. Part of improving is making sure that the community can help out on various aspects of Xenko. This is not just the development of the Xenko engine itself, but also all the other processes that are involved around it. You can follow the ongoing forum discussion here.

New project overview

As part of getting things done quicker, a new public project overview has been set up using Freedcamp. In this here we track of ongoing tasks, who is assigned to it and what possible milestones are. If you want to contribute to this project or just check out the current tasks, have a look.

What is being worked on

Here are some of the things that are being worked on:

New tutorials section for the documentation website. Starting with a section of C# basics with Xenko, we can start making it easier for people to get the hang of Xenko in no time. Here is a quick peek at how it is going to look like.
Phr00t fork merging: The Phr00t fork contains many features that the main Xenko engine could benefit from. From countless API improvements to bigger features like Vulkan improvements. Right now contributors are looking in which features and functionality to move to the main Xenko repository.

Possible name change

For those of you who have missed it: Xenko is looking for a possible rename of the engine. If you want to know more about the why and why not, have a look at this forum topic. Regardless of whether the name change will happen, we need to find a suitable candidate. In a few weeks, we will start a poll to narrow down the long list of suggested names. A more detailed blog on this will follow soon. In the meantime, if you have a great idea, feel free to make a suggestion in the topic above or in the Xenko discord channel “Name-change”.

Community Meeting #2

Fri, 19 Jul 2019 00:00:00 +0000

Time for our second community meeting.

Yes, it has been renamed from Developer meeting to Community meeting to better reflect the intended target audience.

This time, the idea is not only to find where Xenko should head next (I am sure there will be hundreds of ideas, many of them already waiting on GitHub issues!), but also to find more people volunteering to take over some of those tasks!

Here is a tentative schedule for this meeting:

UTC (GMT) Wednesday, 24 July 2019, 15:00:00 UTC
Berlin (Germany) Wednesday, 24 July 2019, 17:00:00 CEST
Paris (France) Wednesday, 24 July 2019, 17:00:00 CEST
Tokyo (Japan) Thursday, 25 July 2019, 00:00:00 JST
San Francisco (USA - California) Wednesday, 24 July 2019, 08:00:00 PDT
New York (USA - New York) Wednesday, 24 July 2019, 11:00:00 EDT
London (United Kingdom) Wednesday, 24 July 2019, 16:00:00 BST

It will be held on Discord in the #dev-meetings channel.

Please come define the future of Xenko with us!

Starbreach Demo

Fri, 31 May 2019 00:00:00 +0000

Hi everyone, Silicon Studio agreed to release the Starbreach demo from GDC 2017, along with all associated assets as open source (see license), for the Xenko community to use. Code in the project is released under an MIT license, the assets are released under a attribution-NonCommercial 4.0 International (CC BY-NC 4.0) license.

Starbreach was originally developed as the Xenko GDC demo for 2016 by Silicon Studio with art support from N-iX production studios. Virgile Bello (xen), Xenko’s lead developer has spent a chunk of time updating the demo and assets to work with the latest release of the Xenko.

You can find the demo and assets here: https://github.com/xenko3d/Starbreach

And more on the licensing here: https://github.com/xenko3d/Starbreach/blob/master/LICENSE.md

Xenko now has a great playable demo… Can we make it even better?

The community is doing a great job building out the xenko 3.1.0.1 beta release especially filling in gaps, fixing bugs and fulfilling the promise of a community led game engine - so special thanks to Tebjan, phr00t, dfkeenan, Eideren, Venthe, Aggror, Pred, Jarmo, dio and xen to name only a few.

With the release of Starbreach demo - we now have a great playable demo that shows off Xenko. xen’s thrown the glove down and done his part with getting release permission and updating - but can everyone in the community help make it even better? Maybe by adding additional AI, improving the game play or adding a new boss character or full levels? Source is on github and let’s discuss on Discord or in the Forum.

Welcome TurboPlay as Gold Sponsor!

Tue, 12 Feb 2019 00:00:00 +0000

We’re happy to announce TurboPlay is helping Xenko not only as a Gold Sponsor, but also have further plans to support Xenko in the future.

Our respective visions for a more open game engine and decentralized marketplace seem to have a lot in common.

Thanks TurboPlay for supporting Xenko and its community! This is a very exciting milestone and hopefully the beginning of a new era for Xenko!

Open the full post for the press release in all its glory.

Press Release: TurboPlay Announces Videogame Engine Support With Xenko

TurboPlay is pleased to announce Gold Sponsorship for the Xenko Game Engine and its Open Source Community.

“We’re pumped to have the opportunity to support the Xenko development team and work with them to develop amazing new technologies for their community and ours! Xenko is a modern game engine technology developed entirely in C#. Xenko’s technology has incredible potential in today’s gaming market. Through this partnership we can provide direct support to Xenko indie developers,” said Vince McMullin, TurboPlay President and CEO.

Launching in 2019, TurboPlay is developing a full-fledged marketplace ecosystem by maximizing exposure for unique indie content. TurboPlay is the world’s first ultra-modern, fully-scalable, fault-tolerant, peer-to-peer, videogames marketplace.

“I’m super excited to work with TurboPlay! We’ll be able to achieve great things together. I believe that both organizations are philosophically aligned, embracing the ideas of permissive open-source, decentralized and distributed architectures to disrupt the status quo in the games industry,” explains Virgile Bello, Lead Engine Developer.

TurboPlay plans to support Xenko in future endeavors, including their Indie Community, with developer grants supporting game development using both Xenko & TurboPlay technologies.

For further inquiries regarding this topic, please contact our CMO, Lisa Weeks, by email, lisaw@turboplay.com. Thank you.

https://www.linkedin.com/company/turboplay https://www.linkedin.com/company/xenko

Twitter

https://twitter.com/trbplay https://twitter.com/xenko3d

Facebook

https://www.facebook.com/TRBPlay https://www.facebook.com/xenko3d

Link to the official press-release: https://www.newswire.com/news/turboplay-announces-videogame-engine-support-with-xenko-20801982

Stride Game Engine

Stride 4.1 is now live!

Stride On .NET Live

Improvements Summary

Improvement Details

Dithered shadows for semi-transparent materials

Physics constraints

Physics optimizations

Improved editor gizmos

Intermediate tutorials

Known Issues

Integrated C# Editor

A little help

Contributors

Financial contributors

Community meeting February 2022

Summary community meeting 2022

Current funding

Funding for bug bounties

Funding for features

Release 4.1

Additional task for Xen2

Work in progress

Epic grant

Community meeting November 2021

Sponsors

A month of Open collective

Preparing request Epic grant

Other Action items

Ongoing development

Open collective

Open (Source) collective

Payments and Expenses

Projects

What’s next?

Community meeting October 2021

Access rights

Roadmap

Funding

Stride 4.1

Remaining topics

Stride 4.0 is now live!

Highlights

Xenko is now Stride!

Voxel Cone Tracing GI

.NET 5

Flexible GPU Instancing

Graphics API: different selection mechanism + Vulkan improvements

Documentation & Tutorials

New Developers are Welcome!

vvvv releases VL.Stride

NODE20

Community Meeting May 2020

Summary

VVVV and VL.Stride

Sponsoring and gold members

Links

Xenko has been renamed to Stride

Why the name change?

New Stride Logo

What does this mean for you?

What’s next?

Final notes

January 2020 recap

A new logo for Stride

3.2 release

Community picks

Project draco

Rollerghoaster

December 2019 recap

What is being worked on

Community meeting 3

Stride logo

Community picks

MentalArray

Fog of war

Community Meeting #3

Xenko 3.1 released!

Highlights

Xenko 3.1 loves NuGet!