X1nput VS DirectStorage

TL;DR: Disable Steam input first (right-click Forza Horizon 5 > Properties > Controller > Disable steam input), then download the latest version of X1input here and place the 64bit .dll file it gives you in the directory of your FH5 game (should be like steamapps > common > ForzaHorizon5)

Go to https://github.com/araghon007/X1nput/releases

Link to download: Releases · araghon007/X1nput (github.com) Link to instructions: araghon007/X1nput: Xinput hook for Impulse Trigger emulation (github.com)

The API that allows for that is Windows.Gaming.Input. There is a re-writing of Xinput called X1nput that allows to use it https://github.com/araghon007/X1nput

Interesting, I hadn't heard of X1nput before. Did you try following the instructions on the X1nput repo?

Try this! It will make it so that if there's a vibration event, the triggers will also vibrate.

I don't think the GPU decompression optimizations is in this driver. I updated and using the Bulk Loader Demo test I'm actually seeing lower throughput than before. I used to hit around 24-25GB a sec, now I'm only hitting like 21GB a sec. Although it's possible but I doubt it, it could be related to the Windows 11 March update reducing SSD bandwidth. I haven't run the test in months so it might be related.

The data is compressed with GDeflate, not deflate. The single stream is designed to use the parallelism of a GPU. It is described here:

https://github.com/microsoft/DirectStorage/blob/main/GDeflat...

The GPU decompression benchmark I linked earlier allows you to specify a single file that it will compress with GDeflate (and zlib for comparison). The numbers presented in the docs that come with the benchmark and presented elsewhere are consistent with my own runs using a source file that is highly compressible.

Part of the trick of achieving this speedup is to read the data fast enough. I don't know of any NVMe drive that can reach full speed with a queue depth of 1. While running the benchmark in a windows VM with a GPU passed through, on the linux host I observed that the average read size was about 512k and the queue depth was sometimes over 30.

We already have GDeflate, with permissive sources available for both CPU compression/decompression and GPU decompression in the DirectStorage GitHub repo. I haven't personally played with it yet, but I'll be implementing it in a project I'm working on in the next few months and am pretty excited to do so.

Wrong: https://github.com/microsoft/DirectStorage/blob/main/Docs/diagrams.mmd

The github repo has some command line parameters.

Only the final test where the results of several SSDs are displayed in the graph is a synthetic one. The first two both support DirectStorage and are designed with Microsoft's recommendations for DirectStorage in mind. That is, random reads of 32k or greater block sizes with high queue depths. This is because you need a high queue depth to be able to saturate NVMe drives.

For most it'll be a background element they're not aware of, if you're running up to date win10 onwards you have DS capabilities, you can get the sample from microsoft build it and run it fine.

Direct Storage github Samples: https://github.com/microsoft/DirectStorage