Hello,

Seems tixati doesn't recognize symbolic links, at least on my system
May anybody try it please, just to check it's not something affecting only me. Or perhaps torrent clients are unable to work with these type of links.

example:
download a torrent with multiple files
set torrent to offline status
move (outside tixati) some of the files to another location
create symbolic links pointing to those moved files
recheck the torrent

for me, only the files that, as expected, were NOT moved are recognised, all the sym links appear to be invisible to tixati.

tixati v2.57
windows 10 pro x64

thanks

An alternative would be changing your file's location by right-clicking in your torrent -> location -> move and then create a direct access for your desired file.

I have Tixati's data symlinked to an encrypted hard drive and it works properly. But I don't use Windows, so there might be something wrong going on there.

Symlinks work at the operating system level both on Windows and GNU/Linux so Tixati should have no problem with them. Try creating the symlinks before you move them to another directory.

I would like to switch to tixati but I cannot get it to work with symbolic links like I am doing on my current client. Every time I restart torrent or program tixati thinks all files with symbolic links are missing and tries to recheck all such files. It rechecks them all right but problem always reappears on next restart. Symbolic links are ok and every other torrent client and windows programs i use recognizes them.

Interesting enough I tried some older version of tixati 2.19 and 2.28 portable and it worked correctly, every symbolic links is recognized. Then I just replace exe file with version 2.58 or 2.59 and it is file missing for all symbolic links. I replace exe file again with 2.19 and again it is ok... Well I guess it is return to utorrent again.

Bump. Just tried with Tixati 2.59 on Windows, doesn't work with symbolic links.
You can create such a (file) link with "mklink <name> <point to path/name>" - Force Check doesn't work and starting the torrent instantly aborts with "error opening file for allocation: access denied, another program may have this file open (5)"

HOWEVER, the NTFS hardlinks work: "mklink /h <name> <target>" - unfortunately they only work within one partition.
Poor symlink support in programs is a pity.

I haven't tried file symbolic links. Folder symbolic links worked OK for me on Windows 8.1 using Tixati v2.58.

Problem still present in 2.61 every restart of tixati it rechecks every symbolic link to files.

Currently I rename all applicable files using Filebot, setting Filebot to crate a symbolic link, to the renamed file. So that Tixati can continue seeding torrent. As the original poster has said when you try to restarts or the Torrents or stop start Tixati the files are read as if they have a zero file length.

Folders work fine, Just not files.

Using hard links at this moment is not appropriate or viable for me.

Using Windows 10 64bit atm.

just ran into this issue myself. the modified date of the symlink itself (rather than the symlink target) seems to confuse tixati in the initial file scanning.

if you don't outright disable LM checking, it'll always recheck the symlinked file on torrent start, (eventual) seeding is unaffected however.

there is also another very minor bug in the ui, if you right click a symlinked file in Tixati, the open option is unavailable.

honestly hope this can get fixed eventually, as this seems like a very minor bug.
below is the log showing the confusion.

[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:08 PM but file is 2024/01/03 06:18:36 PM > 2.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:08 PM but file is 2024/01/03 06:18:36 PM > 7.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:09 PM but file is 2024/01/03 06:18:34 PM > 12.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:09 PM but file is 2024/01/03 06:18:34 PM > 19.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:09 PM but file is 2024/01/03 06:18:34 PM > 20.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:09 PM but file is 2024/01/03 06:18:34 PM > 23.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:09 PM but file is 2024/01/03 06:18:34 PM > 25.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:10 PM but file is 2024/01/03 06:18:34 PM > 26.jpg
[6:44:46 PM]  file LM time mismatch, expected 2021/07/05 06:10:10 PM but file is 2024/01/03 06:18:35 PM > 30.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:08 PM but file is 2024/01/03 06:18:33 PM > 60.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:08 PM but file is 2024/01/03 06:18:34 PM > 62.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:08 PM but file is 2024/01/03 06:18:34 PM > 63.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:11 PM but file is 2024/01/03 06:18:35 PM > 71.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:06 PM but file is 2024/01/03 06:18:35 PM > 88.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:09 PM but file is 2024/01/03 06:18:34 PM > 90.jpg
[6:44:47 PM]  file LM time mismatch, expected 2021/07/05 06:10:06 PM but file is 2024/01/03 06:18:35 PM > 91.jpg