I have just started using Tixati (1.96) portable on Windows moving from uTorrent.
Every torrent I try starts ok and begins to download but then goes in to a constant loop "Checking" the files.
After scouring the forum I have tried forcing a check, changing peer read caching, changing file locations to local disk instead of USB, and enabling permissive checks but nothing has helped.

Event log keeps showing
"file last modified time mismatch"

Does anyone have any ideas how to stop this?

I have found the download does eventually complete but is very slow, I assume due to the constant checking.

Still no idea why it keeps looping on checking the files.

Is there a chance you have Utorrent running? maybe in the back ground? check with task manager.

Hello,

Apologies for the long delay in replying.

No, uTorrent is not running.

I have updated to 1.97 today and this has improved.  It still checks frequently but it is no longer constant and seems to have much less impact on the download.

The release notes do say they have relaxed this for NAS isues and so I assume this has helped even though I am not using a NAS and it seems they are changing how the checking is done in future as well so it is probably not worth worrying over this any further.

Thanks

There is something in the settings, at Transfers > Local Files, it says "Permissive last-write time checks".

Try that if you still get checking issues.

We're eventually going to eliminate the use of last-modified times and give Tixati a fine-grained hashing system instead.

Hello everyone,

I do suffer from the same phenomena, too.
Enabling permissive last-write does nothing (maybe helps something, but seems to have no real effect).
I tried to turn off individual files in the download by setting priority off.
Still, those files were opened for write( (w)) temporarily, although they already were in Off state.

Very disturbing that even some files are already completed, checking is initiated on them sometimes... why???
Also noticed that a file that have finished checking started checking right again.
My assumption is that some threads in Tixati do not know about what the others do, or should do.

A special setting which turns the checking off completely and/or logging the found and the expected value of the last write time could be very useful for debugging.

At the moment a ~10GB 12 file download with 1M pieces cannot complete, stuck at around 90%, because of the constant checking (target is a Ubuntu NAS).
I have stopped the download and watched the files last mod time, but it seem neither Windows nor Ubuntu seems to misbehave.
Something must be wrong within Tixati, it seems that is the only thing that accesses those files.

I have noticed that stopping the download, forcing a full recheck while in stopped state might help a bit, because the download can go on for a couple of minutes before starting the merry-go-round of checking again.
So the bug might be around reading/storing/comparing the last modifed data internally.

Any ideas?

send the torrent to devs with small explanation.

support@tixati.com

Before you assume it's an issue with Tixati, verify you are not running a "realtime scanner". This may be AV or Security or Malware or media player --whatever it is called... if you do not add an exception for the Tixati download folder this may happen.

Tixati does what it does very well but as stated it cannot control other programs. If the file are media and your player likes to mess with tags or append data.... If the files are disk images and you mount them in Windows.... If the files include thumbnails or shortcuts Windows will mess with them.
As of current version 2.47 this happens less but the options mentioned are still there for a reason. There is no universal implementation for non-local storage and as such you can try the two workarounds KH and the dev team have provided.

P.S. @KH is the fine-grained hashing any higher on the to-do?

EX: This is the procedure I follow for each version of Tixati with Windows Defender (included on all versions of windows post 7)
Windows -> Defender -> Open -> Settings ->
"Excluded files and locations" -- make sure main Tixati download folder is listed. Completed may be listed as well but by that time you should be able to get by with a full scan once you switch to seeding. (Be sure to save changes)
"Excluded file types" -- Add the 'incomplete' extension if you use it in Tixati, or add any extensions you don't want impacted. (Be sure to save changes)
"Excluded processes" -- Yes I check/add each version of Tixati here. I usually rename old versions to -2.43-x32 etc. So my Tixati.exe is still the same name but whatever Windows does i add the rule. It's much easier to be sure than try and troubleshoot later. (Be sure to save changes)
"Advanced" -- If I have "scan archives" checked i make sure the types I don't want to are listed above "iso; 7z; rar" etc.
"scan removable drives" applies to FULL, but when I have scheduler run this I make sure Tixati is not trying to fight the disk usage, scheduler is set to OFF for that hour.

2023 and I am getting the same repetitive checking.  Over and over on a very large file.  It is just killing throughput.  When the checking stops for a few minutes, the throughput goes up to 10MB/s.  When it starts up again, it dips down in the hundred MB/s.  That's huge.  I want this to finish but it is quoting many days due to the constant checking.  Files are on a USB drive on a Raspberry Pi running their take on Linux.  Tixati is running on Windows 11.  Is there a time of day issue?  A file updated time issue?  What's going on.  I need the revolving door of CHECKING to stop so this download will finish this year!

Exactly the same here. Keep on "checking" files in a neverending loop. Busy downloading 4x 60-70 Gb archives, and keep on checking in a neverneding loop
10/aug/2023 - tixati version v2.89

Have you tried upgrading to the newest version, 3.19?

This is also occurring for me, latest version v3.19. I am downloading from a windows 10 device to a 8TB SMB Share on my Synology NAS.

File Allocation - Sparse (default)
Peer Read Caching - Predictive

Skipping last-write check times is doing nothing (and is advised as not recommended!), but tested with this setting on and it's still a problem.

something is almost certainly touching your files, possibly even other transfers in the same client, maybe antivirus, who knows.

either way other clients are rather bone-headed and don't really care as long as the files are "there"... they will even let you "seed" a bunch of garbage data without even erroring out!!! realistically Tixati alerting you to an underlying problem designed to stop you from seeding/leeching garbage is not it's fault I would say

the tickbox as I understand it is only applies to the initial scanning phase when starting a transfer, not when downloading.