3.3.11 x64. Temp is circumvented by torrents larger than temp, adding content later on.

[fusk-l]

If you're downloading a torrent that's larger than your temp, and you want to split it in two or more. After having transferred to destination the first portion of the torrent, when you add more downloads through the content of that torrent. Those downloads will circumvent the temp drive and download straight to the destination drive.

Expected behavior. When adding more downloads from the content of a torrent, those files will go to temp first before being transferred to the destination.
qBit 3.3.11 x64, win8.1 x64.

[fbriere]

If I understand correctly, instead of torrents being moved into or out of the "incomplete" directory as a whole, you would like this to be done on individual files instead.

This is not easily possible at the moment, since qBittorrent expects the entire contents of a torrent to be located under the same directory. See #4071 for a request to lift this restriction; I suppose that if/when that issue is solved, this one shouldn't be too hard. I don't know if it should be considered a requirement, though; what you're asking for might be a bit simpler, since it doesn't involve remembering (and creating a GUI for editing) individual pathnames, but rather a single toggle switch for a whole torrent.

[fusk-l]

IE. temp is 10gb, torrent is 20gb, set qbit to download the first 10gb to avoid errors, after qbit is done with the first 10gb and has transferred it to destination, the temp drive is now free to download another 10gb. You select the torrent and mark the next 10gb for download. The next 10gb does not go through the temp drive, but goes straight to destination. What i'm suggesting is that the second half of the torrent also go through temp drive like the first half did.
Hope that helps.

[sledgehammer999]

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.