XEMU v0.7.58

XEMU v0.7.58 is released. xemu is an open-source, cross-platform application that emulates the hardware of the original Xbox game console, allowing users to play their Xbox games on Windows, macOS, and Linux systems. This project is focused on making significant forward progress in terms of features, performance, stability, and user experience in Xbox emulation. This project is an active fork of the XQEMU project, which is based on the very popular and highly actively maintained QEMU full system emulator project.

XEMU v0.7.57 changelog:
nv2a: Do not force oFog to 1.0
This code was added ~7 years ago in
[this commit](https://github.com/xqemu/xqemu/commit/97be3f598683721bc43e354d7804221152e21f02)
From what I can see from the [HW test results](https://github.com/abaire/nxdk_pgraph_tests_golden_results/wiki/Results-Fog_coord_vec4)
the behavior on nv2a is more subtle than the cited `NV_vertex_program`
documentation.
In practice the register more or less retains its value until it is explicitly
modified.[The test](https://github.com/abaire/nxdk_pgraph_tests/blob/4cff2b2ebe49c29eb24caea9c058b3d6ddaa3a16/src/tests/fog_tests.cpp#L432)
renders something with an explicitly set oFog.x, then renders again with a
shader that does not modify oFog.x but references it in the pixel shader. The
value carries over rather than being forced to 1.0.
Interestingly, this test is apparently not hermetic; running the other
vec4_coord test (that explictly set various components of oFog) lead to unusual
behavior where the fogging effect is not uniform across all vertices, despite
never being set. Even more interestingly, re-running the test once it's in this
state will often produce variations as to which vertices are apparently using
a stale/incorrect fog value.

Download: XEMU v0.7.58
Source: Here