Month: June 2017

Flax Facts

Flax Facts #7 – Universal API


Universal API Hidden behind decompiler Many modern game engines, actually all of them that I know of uses 4 different APIs for UI elements. Editor Internal API – for all elements that were not designed to be modified, or intermediate methods that hide “complicated” stuff Editor Public API – all methods that we get to

Flax Facts #6 – Persistent Data


Game saved. Another Friday Flax Facts! Today we have a bold topic. How many times were you in need of writing your own system for handling persistent data between restarts: game states, configurations, local runtime asset storage and everything that needs to be held for the user until next session? Flax has an answer for this,

Flax Facts #5 – DirectX 12


Next-Gen and DirectX 12 Did you hear about DirectX 12? It’s a next graphics API from Microsoft after DirectX 11 which is not a successor but kind of new low-level API. This gives a way more power and control over the GPU but does it? Writing own GPU driver First of all we’ve successfully implemented
Flax Facts

Flax Facts #4 – Shaders Parser


Shading Surfaces using Shaders Hello! It’s Friday again! As always we have some news for you and of course interesting post. This time I will talk a little about our shaders, especially parsing shaders. But first the news. In this week we added more support for Compute pipeline in DirectX 12 and exposed more Engine
flax facts

Flax Facts #3 – Let’s design Editor


From developers for developers. I would like to do a test 🙂 It is anonymous so brace with me. Pick your best, a beloved game engine that you are working on Today. Now imagine that in the middle of the project where your whole animation data is processed by default engine animator timeline tool, you had added