Xenko 1.6 Beta Released

Silicon Studio Corporation

Xenko 1.6.0-beta is now available, just in time for GDC 2016.

This release is a great step forward towards making the engine better to build awesome games.

Prefabs allow you to reuse assets and build game more efficiently. Particles are a critical requirement for many immersive games, and are now part of the engine with full editor support.

Lastly, we have done a full rewrite of our graphics engine, paving the road for better performance and scalability. We canโ€™t wait to add many new rendering features on top of it! As a bonus, we included our experimental Direct3D 12 renderer.

This release consists of 2425 commits, with 135208 lines changed!

New Features Highlights ๐Ÿ”—

Prefabs ๐Ÿ”—

Prefabs allow you to assemble entities into building blocks and easily reuse them in any of your scenes. Changes to your prefabs will be reflected on all instances (as long as properties are not overridden).

We even took the concept one step further to empower our users, by having prefabs within prefabs, as well as the possibility to use only part of a prefab when you instantiate it. And of course, removing or rearranging a few entities wonโ€™t break your prefab synchronization!


Archetypes ๐Ÿ”—

You can now use any asset as an archetype for another asset. When you change a property of the archetype, the new value will be automatically propagated to all the derived assets, unless you specifically override them. Archetypes can be used with most asset types.


Particles ๐Ÿ”—

You can now create and edit particle systems directly in the Xenko Game Studio. Particles are deeply integrated in the game engine and leverage the powerful effect system and its high level of customization.

While there are still several features on the roadmap, the current implementation is sufficient for most games. The ability to customize almost all aspects of the particle engine allows you to add features tailored to your gameโ€™s specific needs.


Feel free to visit our particle documentation.

Features ๐Ÿ”—

The particle engine supports many features out of the box:

  • Render particles as different shapes like billboards, 3D oriented quads or your own custom implementation
  • Powerful force fields which offer more control than simple attractors and repulsors
  • Collisions
  • Animated attributes such as size, color, rotation
  • Flipbooks, UV animation and support for the Xenko Shading Language

Modular system ๐Ÿ”—

All aspects of particle systems are broken down into individuals modules like spawners, initializers and updaters, and each of these modules is easily tweakable and customizable. Check out the samples and the Xenko documentation for a detailed walkthrough.

Curve Editor ๐Ÿ”—

The Game Studio now also comes with a built-in curve editor. For now only the particle engine uses curve animation. In the future, it will also power our property animation system and our storyboard system.

Curve Editor

New Graphics Engine ๐Ÿ”—

Most of our graphics pipeline, both low-, medium- and high-level, has been almost completely rewritten, and should be ready for the future.

The low-level API has been changed to more closely resemble DirectX 12 and Vulkan. For a list of breaking changes, please see below.

The high-level pipeline has been completely reworked, to achieve the following goals, most of which we will tackle in the upcoming releases:

  • Introduce a clean and extensible architecture to easily build new graphics features on (hoping to soon add a Forward+ renderer, IBL lightprobes, RLR, etc.)
  • New medium-level layer: lightweight RenderFeature, RenderStage, RenderObject, etc.
  • Easy for users to write small customizations (by implementing RenderFeatures)
  • Allow multi-threading of all parts of the pipeline
  • Make optimal use of next-gen graphics APIs
  • Reduce the amount of "magic" done by the effect system to increase performance
  • Minimize work by taking better advantage of different update frequencies (PerView, PerMaterial, PerLighting, etc.)
  • Take advantage of new API (first class support for Pipeline State Objects, Descriptor Sets, etc.)

Stay tuned for technical details and performance evaluation in the near future!

Direct3D 12 ๐Ÿ”—

Direct3D 12 has been added as a new build target. While still experimental, it already supports all parts of our rendering pipeline.

You can try it by changing the โ€˜Preferred Graphics Platformโ€™ in the โ€˜Rendering Settingsโ€™ of your โ€˜Game Settingsโ€™ asset.

Better OpenGL support ๐Ÿ”—

Our OpenGL renderer has been improved and should behave much better (shadows, PBR, etc.). Also, we now deliver OpenGL and OpenGL ES on Windows as build targets.

You can also try them by changing the โ€˜Preferred Graphics Platformโ€™ in the โ€˜Rendering Settingsโ€™ of your โ€˜Game Settingsโ€™ asset.

Scripts are now components ๐Ÿ”—

So far, there could only be one component per type on an Entity. This was quite cumbersome, especially for scripts, which had to be stored inside the ScriptComponent.Scripts list. It also resulted in many special cases to make them work in the editor (i.e. references between scripts, assembly reloading, etc.).

Now multiple components of a type are allowed. This affects scripts and physics components, and can be used for custom components for which more than one instance is sensible.

We hope this makes your life easier!

Event system ๐Ÿ”—

We added a simple event system that will allow your script to easily communicate with each other.
Check out the EventKey<> and EventReceiver<> classes.
You can create an EventKey from your sender scripts and consume events using EventReceiver from other scripts.

Game Settings overrides ๐Ÿ”—

The Game Settings asset has been improved: You can now have different settings depending on the platform or GPU.

For example, you might want to set different off-screen resolutions for your game on Android depending on the GPU model. Or you could use one of our new Direct3D12, OpenGL or OpenGL ES renderers on Windows.

Version 1.6.0-beta ๐Ÿ”—

Release date: 2016/03/15

How to upgrade ๐Ÿ”—

Simply open your older projects with new version of GameStudio. It will probably fail to compile your assemblies since API changed little bit, but you can still continue.

Then, save back your project in GameStudio. You now can open your project with VIsual Studio and try to fix your game code with latest API changes.

Enhancements ๐Ÿ”—

Assets ๐Ÿ”—

Engine ๐Ÿ”—

  • The KeyedSortedList now implements ICollection instead of IList annd is more consistent with CollectionDescriptor.

Game Studio ๐Ÿ”—

  • Support for prefabs, add a prefab editor
  • Create derived assets and support property inheritance
  • Added a curve editor to edit animation curve
  • Layout is saved on a solution basis. When reloading a project, Game Studio will try to present the same layout and reopen all assets that were edited (this include scenes, prefabs and sprite sheets).
  • Add a confirmation dialog to enable saving newly created script automatically.
  • Add a confirmation dialog to enable reloading modified assemblies automatically. This is necessary for the script to appear in the list of components that can be added to an entity.
  • Physics gizmos are shown by default.
  • Preview of an asset can be displayed even if this asset is being edited.
  • Project folder can be opened in Windows explorer from the launcher with right-clicking.
  • Properties of derived asset are displayed in gray, unless they are overridden. In this case they are displayed in bold.
  • Rework scene initialization in the scene editor: the scene will be available almost immediately, and content (model, etc.) will be streamed in as soon as they are (asynchronously) loaded.
  • The entity fixup wizard has been removed. Now when an entity is deleted, all references to it or to one of its component is reset to null.
  • The gizmo and camera menus are now displayed in the top-right corner.
  • Entity hierarchy is synchronized (automatically expanded) with the selected entity in the scene.

Graphics ๐Ÿ”—

  • New D3D12 renderer (experimental)
  • New Windows OpenGL and OpenGL ES renderers (experimental)
  • Rewrote most of the low- and high-level graphics code to have better performance and better take advantage of new graphics APIs
  • Properly separated rendering in 4 phases: Collect (collect & cull), Extract (copy data from scene to renderers), Prepare (prepare cbuffer data & heavy computations), Draw (emit draw calls)
  • Introduced concepts of RenderFeature (entry point for extending rendering), RenderStage (effect selection), RenderView and RenderObject
  • Render sorting logic can now be customized (culling will be soon too)
  • Low-level API has been rewritten to match better new API: CommandList, DescriptorSet, DescriptorHeap, PipelineState, etc.
  • Introduced concept of RendererProcessor which are responsible for pushing component data to rendering
  • Many other changes, that will soon be covered in documentation

Input ๐Ÿ”—

  • Improved GamePad event management to resemble the keyboard API.

Issues fixed ๐Ÿ”—

Game Studio ๐Ÿ”—

  • Fix Scripts thumbnail generation during project launch.
  • Fix Settings window sharing columns layout with property grid (#341).
  • Fix default IDE settings incorrectly reset to null.
  • Fix a crash occurring when duplicating an object quickly after selecting it.
  • Fix an issue with the message box incorrectly resizing.
  • Tooltips are always visible even if the control (menu, buttonโ€ฆ) is disabled.
  • Fix several issues with undo/redo.
  • Fix drag and drop of components into properties
  • Sometimes the Game Studio was not asking to save when closed with some changes in a project.
  • Fix some issues related to folders in scene editor.
  • Redo does not re-open asset picker anymore.

Graphics ๐Ÿ”—

  • Tangents generation was invalid and might have resulted in various swaps

Physics ๐Ÿ”—

  • Improved collision detection reliability
  • Fixed collision filter groups
  • Fixed enable/disable component behavior

Breaking changes ๐Ÿ”—

Graphics ๐Ÿ”—

  • Extending rendering is quite different from before. Please check SpaceEscape and other samples to have a better idea while we prepare documentation.
  • Many methods of GraphicsDevice have been split off into a second class: CommandList
  • Added objects such as PipelineState, DescriptorSet and DescriptorHeap to better match new graphics API
  • Game now contains a GraphicsContext which gives access to the current CommandList
  • GraphicsDevice.BackBuffer and GraphicsDevice.DepthStencilBuffer are gone. Use GraphicsDevice.Presenter.BackBuffer to access the actual backbuffer.
  • In addition to RenderContext, there is now a RenderDrawContext. Some methods have been changed to expect the latter.
  • ParameterCollection has been rewritten to be much more memory and performance efficient (data is now stored directly in buffers).
  • Transferring values from application to shaders and computation of effect permutations used to be done through various inefficient ParameterCollection overrides. This should now be done using RenderFeatures.

Physics ๐Ÿ”—

  • PhysicsComponents are now split into 3 different types (Rigidbody, Character, StaticCollider) which can be added multiple times in an entity.
  • PhysicsElements are now removed, including the Collider, Rigidbody and Character classes. They now are merged into the new components.

Known Issues ๐Ÿ”—

  • iOS on ARM64 iPhones encounters crashes after a few second. We are currently investigating this.
  • Sometimes duplicate contacts are detected by the physics engine


Any comments? You can start ๐Ÿ—จ at GitHub Discussions or Discord.

Edit this page on .