Bosenator

Okay, was just informing you that the error persists for our community, and that not everyone gets the error, just a substantial number - an issue that started to occur with the last update. The issue doesn't occur with .PBOs, only .bisign files. It is not a partial file transfer issue for us, as doing what you mention to the .bisign files is perfectly fine - they update no problem. The fix is to delete them, to which sync will then download the file just fine. I will run ArmA3-Sync Debug by default now, so if the issue does happen again, I can screen shot it for you. Edit: Just found out, the guys who don't have the issue are the ones on 1.6.92, and the ones with are 1.6.97.

This issue just happened again for 20 people.

Sure, no problem. http://db.thewreckingcrew.eu/public/.a3s/autoconfig

Roger, will give it a try the next time it happens. It is HTTP.

Hello, Since the last update, many of our community members are getting the occasional signature file that fails to update. The download will state 0b, and continue to inform them the file is out of date. To fix it, they have to delete the file off their system, and recheck. Once doing this, ArmA3Sync will correctly download the signature file, and everything is fine. We did not have this issue prior to the last couple of updates. Is this a known new issue, or unique to us?