Multi-Backup/AutoSave doesn't work with large tvpp size above 2.1gb, on Windows Topic is solved

[ini]

There might be a permission issue on your multi-backup files, that prevents TVPaint from overwriting them.

Can you see that the file modification dates are updated, when you save your project ? if you click on "file properties", are you the owner of the files ?

well, I think It's not...


Backeuped one is updated with new one only when the file size lower than that amount of size..
furthermore, i checked the file changed with new, by opening it.

if it's permission issue I think It's impossible even when the file size is lower than 2.1gb.

Defaultly I'm adminstor user.
I tried to test it by executing TVP with admin authority once.

Also,
i tried it when there is no backuped file with over than 2.1gb tvpp size,
If it's permmission issue, and if there is no backup before, It have to make backup file.
but it doesn't...

[ini]

I checked it from my friend using windows, and Tvpaint v11.

The same thing occurs to him too.
-asking location
-no update on backup

when I asked only about if backup worked well or not,
He refered about the asking location first, and said about backup.

He also said,
when he made graduation film, because of the save-alarm, he devided that to 3.

[Xavier]

I'll check that.

[Xavier]

but when the tvpp file hit large size above 2.1gb,
It ask me the location to save,
even if it already has saved location & even if I used "Save", not "Save as"

You're right, I was able to reproduce this. I created a bug in our bugtracker.

I tested using a 4 gig TVP project. On Linux and Mac it worked fine: I had a copy with the save datetime, but on Windows it is as you described.

[ini]

Thank you for the check!

Maybe can you fix this someday?

I think these are all caused by same reason....
I hope this is fixable.

[Xavier]

The idea with the multi-backup is that you don't lose your work so yes, we'll do our best to fix it !

[ini]

The idea with the multi-backup is that you don't lose your work so yes, we'll do our best to fix it !

Thank you....!

[Xavier]

Dammit, I think I got it ! Apparently it was caused by the Windows API, but I suspect you don't wan't the details

The fix will be available in the next beta and in the 11.5.1 release.