Please fix. The error makes it impossible to continue a Download.

Happens mostly on updated torrents.
For example a torrent with a large book collection that you have already downaloaded gets updated (new books + changed books versions).
You download the new torrent version and let the filecheck run, which results in "File Too Large" error.

I have gotten that error before, and have determined the cause:

When I download a torrent with a single file, I have it set to not create a subfolder for it.  Say the file downloading is named 01.mp4.  If I then download another torrent that is only a single file and that file is too named 01.mp4, while not creating a subfolder for the torrent, it will conflict with the other 01.mp4 file in the download folder.  And hence, tixati reports the "file too large" error.

The problem is when for some reason the file size don't match what it supposedly should be. Using Utorrent, it cab automatically fix the file size when you do a "Force Re-check". Now I've encountered a case where doing this didn't fix the problem at all.

It's fixable by doing it manually with a hex-editor in order to save the downloaded data. You can determine the file expected size by recreating the torrent else where. But that's not really a solution to the software problem.

So I suggest adding a specific feature. When right clicking on the file there should be an option to fix the file size and a sub-option to keep a backup of the file. In order to save the downloaded data, the file should be copied to proper length: If the file was too long then truncate it. If the file was too short then expand it with nulls.

I made the same suggestion a few days ago:
> I'd certainly appreciate better handling where an incorrectly-sized file is detected.
> A YES/NO option to automatically resize (extend or truncate it) rather than forcing the user
> to manually delete it outside Tixati and manually recheck the torrent, forcing a complete
> empty file rewite, would be a far saner method, especially with large files. And even if the
> file is a different size than expected, it might still contain valid data if checked as normal

It certainly shouldn't be default behaviour to offer to save a copy of the old data. That's potentially a lot of additional copying, or if it renames and creates a new version of the offending file(s) we know how slow Tixati is creating empty files... :/

What is the benefit anyway? If you are verifying from a torrent you have downloaded, and have specifically provided a set of existing downloaded files with the same torrent name and structure for it to check, you are obviously trusting that to provide proper verification. If file names are exactly the same but the file size is different then the most likely scenario is a repack torrent, so you specifically wanted the newer version and don't need the old. Alternatively there was some allocation error originally, perhaps if there was a problem in the middle of creating the empty fileset and you have reloaded the original torrent, so again you just want that fixed with a simple resize to allow the torrent to work.

There's hardly any situation where you'd want to keep a copy of the old data when you are verifying from either a new or original torrent with exactly same-named files. That's why it's strange that Tixati has never provided an option to automatically resize files, just stopping clunkily with an error to force manual handling. :/

Stop playing fantasy and just read the instructions.
"File Too Large" in this case appears when the disk already contains a file that has changed in the updated *.torrent for some reason. The existing file must be deleted by hand or let Tixati do it. All necessary settings are in Settings-Transfers-Files

Cannot see any option Settings-Transfers-Files to solve the issue... After years with this behaviour I'm still deleting by hand the problematic files. The major issue is with torrents with libraries of hundreds of files, so much time consuming fixing them.
And BTW, really don't understand why is so hard setting an options that delete the file in case of size mismatch...

Settings/Transfers/Files -> Error on missing downloaded files
Settings/Transfers/Files -> Allow deletion of created seed local files

You can set the necessary behavior on your own.

Tried every combination possibile, including the experimental option skip start-up file scan. None of them works, still file too large occur. And delete one-by-one hundreds of files is frustrating....