Thomas Altenburger

3.8.0 is not compatible with ```net6-android``` targets, it requires the "Xamarin" style of projects (likely Xamarin.Android 11 with VS 2019). 3.8.1 supports ```net6-android``` only.

> `Mono.Android` and `Mono.iOS` implement a few of the `System.Drawing` features, such as basic types like `Point`. > > This proposed change is actually a breaking change because it is...

I may have mislead you into this, but it has nothing to do with XNA. This is about platform consistency. I only mentioned XNA to retrace why XAudio was used...

I believe that we should be fine dropping SM 2 and 3, we need to move forward at some point. People who need SM 2 or 3 could still use...

As far as I can tell, the Vsync code of the UWP implementation was done back in the days when UWP didn't have support for explicit VSync support. So there's...

You didn't pulled the git submodules. No other dependency should be needed to build MonoGame. Even though the teamcity nugets are outdated, the one you referenced to does include #7463

Could you share more context in regard to why you need to kill and restart instances of ```Game```? Monogame isn't designed for this and the mobile/UWP use cases intended aren't...

This really is very specific and not the intended use of MonoGame. I am not sure if we should support/encourage to instantiate a Game object per GUI view. The intended...

Closing this issue for the time being since it relates to an intended use case. Feel free to comment, we will re-evaluate the demand if need be.

This is a really open question: does anyone have a real world use case where using ```System.Numerics``` shows a noticeable difference? On full games, these operations are likely invisible in...