linux-vr-player-or-something VS Bullet

Using an Oculus Rift CV1 with nvidia - I've set up the udev rules and enabled extended mode, and got audio working via vr player. However in both the player and the simple example I can't get anything to appear on the display. I do get some effect though as after running either my computer thinks it sees a new display which shows up as a profile in xrandr (and it flickers like a new monitor was plugged in): HDMI-0 connected 2160x1200+2560+0 (normal left inverted right x axis y axis) 119mm x 66mm 2160x1200 90.00*+ as well as in displays on KDE - but nothing shows up on the headset and the light doesn't change from orange.

At one point, VLC implemented OpenHMD support but I'm not sure if they ship it in the compiled versions. There is also https://github.com/sandsmark/linux-vr-player-or-something

does anyone know something about it? https://github.com/sandsmark/linux-vr-player-or-something

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.