Dear Valve,
What on earth is going on with the automation process to patching, please As a user with a PC with multiple types of drives attached to my PC, I want to control where the Patch downloads and what drive it use's to patch, as an example Space Marine 170GB on my C drive 2TB NVME drive. This drive has 450GB free, the current patch is 11GB, I know you'll need room to uncompress and patch, but I have a decent amount of space free, Steam for what ever reason has decided to download the patch to another drive a mechanical drive that actually has less room on it than the C drive. and the patching process is now going to take 3 hours to complete.
so I ran health check on the NVME drive, checked the Firmware, and the drive is perfectly fine, I have now had to find the manifest file for Space Marine 2 and change the drive number from 2 > 1 this I'm told should make it use the 'C', I restart steam, and this forced the the redownload of the patch, everything fine for first 20mins of the patch C drive is being used, I have 1GBps up and down fibre, so the actual patch download took a few minutes, I have now just checked and its now using another drive an SSD drive as well, I still have 450GB on C (NVME drive, Steam has decided to use is a SATA 1TB SSD, and it has 193GB free to use, quite frankly this nonsense, and this has to stop, you need to start working with DEvs and work out a better patching process, I can download 170GB quicker than current patch process, give me control of this patching process as well, this process is killing my SDD/NVMe drive far faster. You (Valve/Developers that use your platform) are effectively ruining my hardware. This current practice needs to get better.