Xamarin.Essentials VS Bullet

This one was one of the most annoying bugs in MAUI, and I solved it with this workaround taken from IeuanWalker on this thread.

This behavior is by design as it enables SSO with web identities but can be problematic in situations like this. Unfortunately, this kind of sign-out isn't a well-supported scenario, but you can read a good discussion on GitHub about it here: https://github.com/xamarin/Essentials/issues/1223.

I don't know where you're seeing "xamarin/Essentials", but that's a repo for code used in writing cross-platform mobile applications. That message refers to this issue: https://github.com/xamarin/Essentials/pull/1457. It's something that was fixed in the project 7 months ago.

First, add the Xamarin.Essentials NuGet Package to your projects. If you're using MVVM (Like we're doing in this example), you'll ideally want to install the Xamarin.Essentials.Interfaces NuGet Package

In the guide they have a link to a sample controller which does this, so I borrowed the code from it and ended up with this authentication controller method:

Xamarin.Essential >=1.5.3

Fortunately for us Xamarin developers, the Xamarin team and the community have created the Xamarin Essentials library and one of its utilities is the MediaPicker, which abstracts from you the logic for taking a picture with the camera or getting an image from the storage. You can read the documentation for the Media picker here.

For typical game physics engines... not that much. Math libraries like Eigen or Blaze use lots of template metaprogramming techniques under the hood that can help when you're doing large batched matrix multiplications (since it can remove temporary allocations at compile-time and can also fuse operations efficiently, as well as applying various SIMD optimizations), but it doesn't really help when you need lots of small operations (with mat3 / mat4 / vec3 / quat / etc.). Typical game physics engines tend to use iterative algorithms for their solvers (Gauss-Seidel, PBD, etc...) instead of batched "matrix"-oriented ones, so you'll get less benefits out of Eigen / Blaze compared to what you typically see in deep learning / scientific computing workloads.

The codebases I've seen in many game physics engines seem to all roll their own math libraries for these stuff, or even just use SIMD (SSE / AVX) intrinsics directly. Examples: PhysX (https://github.com/NVIDIA-Omniverse/PhysX), Box2D (https://github.com/erincatto/box2d), Bullet (https://github.com/bulletphysics/bullet3)...

I suspect most C++ physics libraries like Box2D (https://github.com/erincatto/box2d) or Bullet3 (https://github.com/bulletphysics/bullet3) could really benefit a lot from SIMD.

No, they replaced Bullet with Jolt. That is considerably more than "some adjustment", regardless of what you think of the result.

Vulkan graphics via Intel GVK, and physics via Bullet

The first two have a bunch of great examples, and I’m tying them together by refactoring some of the THREE examples to fit the ECS paradigm defined in AFrame. then upping the ante by adding physics using AMMO, which is more challenging since it’s only a partial implementation of Bullet, and already poorly documented (yet popular) physics engine.

Plus, SM uses a system called bullet physics, I imagine this would be rather complex to rework into a modern engine such as Unreal or Unity (after all, the majority of performance issues come from the physics engine rather than the graphics engine)

The physics in HDT-SMP are actually being calculated outside of Skyrim's engine with Bullet, an open-source physics engine. So this isn't some limitation of Skyrim's engine.