Open extesy opened 1 year ago
Looks a lot like #18495 and #18297 that appeared only in 4.5.0. There was no problem with rehashing in older versions, especially with manual relocation there's no problem even in 4.5.0. Anyway this is fixed in next release. Make sure you have alternative path for unfinished jobs turned off.
there's no problem even in 4.5.0
I am using 4.5.0 and there is a problem, please see the repro steps. I will check the next version whenever it releases.
4. Do not start downloading. Instead, right click and chose "Set Location" to point to FILES_LOCATION.
Set location
is some kind of rudimentary. It does change "Save path" actually. And qBittorrent doesn't still look at "complete" save path when rechecking incomplete torrent and "incomplete" save path is configured to be used.
And qBittorrent doesn't still look at "complete" save path when rechecking incomplete torrent and "incomplete" save path is configured to be used.
And what is the correct workflow for when I want to seed existing files without redownloading them?
And what is the correct workflow for when I want to seed existing files without redownloading them?
Perform your steps 1-3 above and then change "incomplete" save path of torrent instead of "Set location" (assuming you use v4.5.1)
Otherwise you can initially point torrent to the location where existing files are placed (using Add new torrent dialog)
I am using 4.5.0 and there is a problem, please see the repro steps. I will check the next version whenever it releases.
4.5.1 resolves that. It works as it should, my favorite version now. Now it can rehash multiple torrents at once - that's so great.
qBittorrent & operating system versions
qBittorrent: 4.5.0 x64 Operating system: Windows 11 Pro 22H2 (10.0.22621)
What is the problem?
A torrent for pre-existing files was loaded into qTorrent. Before starting a download, I changed the save location to match the current location of those files. "Force recheck" didn't work so I had to copy files into the temporary download folder, then it worked. However now it still expects the files to be in the temporary location instead of a destination one.
Steps to reproduce
Additional context
There is a hacky workaround. Assume there is a new random folder we can use RANDOM_LOCATION.
Log(s) & preferences file(s)
data.zip