Tag: .net

Flax Facts

Flax Facts #16 – Scripts Hot-Reload

Flax Editor and C# Scripts reloading Welcome to the newest Flax Facts! It’s time for another not/a little/very interesting blog post. You choose how interesting it is. But before, let’s dive into one of the coolest Flax Editor features which is C# scripts hot-reloading! Assemblies reload Flax Engine developers write game scripts in C# language.
Flax Facts 13

Flax Facts #13 – Profiler

Feature Preview: Profiler Welcome to the first Flax Facts in 2018! I’m very excited to show you our the latest engine feature: profiling tools set. Although Flax is running pretty good and has a great performance it’s important to keep eye on draw/update time charts and deliver games that run stable and smooth. So that’s

Flax Facts #10 – Scripts debugging

Feature Preview: Tool for Visual Studio Welcome back to the Flax Facts! Recently I’ve finished our brand new extension for Visual Studio (VS) that enables game scripts debugging. It’s definitely must have for every game programmer. It allows to debug and track code execution live. The plugin comes up with features like: breakpoints, threads stack

Flax Facts #2 – Moving Editor to C#

Open Source Editor Welcome to fresh Flax Facts post! Today I want to talk a little about our current task which is: Moving Editor to C#. Yeah, kind of dramatic change, especially because 3 years ago whole engine was running on C# 🙂 But we don’t move everything… Plug in baby The question is why

News Corner #3: Mono vs CoreCRL

Hi! Welcome to the News Corner! Today is my first blog post, I hope you will like it, like all previous posts 🙂 Today I will talk about .NET integration in the current project and possible outcome of coreclr integration as main CLR in Flax. Walking on spikes in the darkness. Mono CLR Every project
open source api

Open source scripting API

Open source API I’m proud to announce that Celelej Game Engine scripting API is now open source and available here! As I mentioned in the previous post I’m currently improving engine scripting service. This means breaking changes may occur but some basic parts are ready to go. What should you expect from new API? Designed