Jules Blok

Normalize the path using replace().

2

On Windows `os.path.normpath()` will add backslashes and quotes to the path which git can't handle. The original commit 978314a4be4d51ceaca8bf8359b29289b16d2691 mentions that the intention for `os.path.normpath()` was to normalize paths with...

Use the Thread ID as the name for unknown thread

2

It isn't much, but this is slightly more useful than just using "Unknown".

We didn't account for the oversample factor yet. Since the overfill factor wasn't really used, I replaced it with the oversample factor.

Figure out the difference between BUFFER<T> and FBUFFER<T>

1

Seems to be exactly the same class...

Clarify that Content-Length is required in the HTTP header

5

Without it your message will be empty and the message will be replaced by "triggered". I initially missed this because normally this happens when using a GET request instead of...

TeamSpeak Push-To-Talk disables G-Key Voice Activation

5

It can be reproduced by enabling Voice Activation through a G-Key and then activating Push-To-Talk key through a normal TeamSpeak hotkey.

Useful to check for round-trip errors in the depth buffer. Purely an emulator test right now, since peeking poked values doesn't seem to work on console.

Useful for making depth more accurate, expected result on console is: 13884592.

VideoCommon: Add support for unrestricted depth range.

23

This PR uses the unrestricted depth range extension to achieve the following: - Remove the need for normalization of the `[0, 2^24)` depth value range using `VK_EXT_depth_range_unrestricted` and `GL_NV_depth_buffer_float`. -...

[DO NOT MERGE] Use a fixed-point depth buffer with an unrestricted depth range.

1

This is a test using `D24_UNORM` and `VK_EXT_unrestricted_depth_range`. In theory this allows us to natively support oversized depth ranges without the need for `VK_EXT_depth_clamp_control`, but unfortunately the `16777215.0` divisor causes...