Stride Game Engine VS WPF-Samples

In general it took me less time to rewrite the code-base then implementing some of the workarounds for missing features in Unity (e.g. HTTP2) in the first place.

[0] https://github.com/stride3d/stride/issues/2069

I don't know where you have all these GC problems. There must be a problem with your design. I run real time automation stuff in C#, GC doesn't caused any problem yet. Stride3D docs says, that's if you put a lot of big objects in the heap without reusing them, you will hit big GC pause: https://github.com/stride3d/stride/wiki/On-Garbage-Collection But most of the time it's trivial to reuses those.

This could be set as a prominent link somewhere, it is the official stride forums: https://github.com/stride3d/stride/discussions

If you like to develop in C#, the free and open-source game engine Stride is a good alternative. But it really depends on your needs and skill level: https://github.com/stride3d/stride

> ...you are requested to delete The Machinery source code and binaries.

This is pretty weird.

Then again, in regards to the engine itself dying, I feel like this is inevitable for many of the projects out there. For example, there was the Xenko engine which was later renamed to Stride: https://www.stride3d.net/

It's actually a nice project, has lots of great features and feels like it should be a more open alternative to Unity, whilst being similarly easy to use. However, compare the attention it is getting in comparison to something like Godot:

  - https://github.com/stride3d/stride

I leave this little thing: https://stride3d.net

In just a few minutes I was able to adapt Microsoft's "Custom UI" sample such that it included two extra buttons (the MS sample only does close and resize so I added minimize and maximize).

Look here for examples.

A few starting point in the documentation, though: * FrameworkElement.SizeChanged event * Window.DpiChanged event * PerMonitor DPI * Visual class: one of the root class of all visual elements. It has a few interesting methods such as void OnDpiChanged(DpiScale oldDpi, DpiScale newDpi) and GeneralTransform TransformToVisual(Visual visual).

There are a few sample apps here: Microsoft/WPF-Samples and there are plenty of tutorials/information available about MVVM and WPF in general on sites like stackoverflow and others.

Is it a per-monitor high DPI issue?