New recruit here. Having some very strange issues with ArmA3Sync.
First, I cannot connect to the repository, specifically the primary member repository system. When attempting to connect, I receive one of two error messages.
The first: "Failded [sic] to read file /.a3s/sync. IOException caught while copying."
The second: "Failed to connect to repository 506th Infantry Regiment - Member repository system on url
ftp://62.210.167.47. Connect timed out."
I'm sure the first is some sort of Java error. The second is strange, because I'm able to ping the IP, and I've disabled all of my router's security filtering as a test to make sure it wasn't being blocked or made inaccessible by my local equipment. There does not appear to be any rhyme or reason to the alternating error messages; it's almost like ArmA3Sync is just picking one and throwing it at me.
My second issue is with configuring the TFAR installer menu. When I select my TS3 location, C:\Program Files\TeamSpeak 3 Client, and click Proceed, I receive an error message stating that "TFAR plugin task_force_radio_win64.dll is missing." I have copied the relevant plugins to the TeamSpeak 3 Client\plugins folder, and have enabled the TFAR plugins in TeamSpeak. Google is of no help on this issue.
I followed the ArmA3Sync and 506th repository guides to the letter on first setup. What am I doing wrong?
Edit: I've solved my problem with the missing .dll. The repository instructions imply that the .dll and sound plugin files are only to be copied to the plugins folder in the TeamSpeak 3 Client folder. You must also create a plugins folder in the @task_force_radio mod folder and drop the plugins there.
This is taken care of automatically when installing mods via the repository, however, the repository is extremely slow to the point of being useless, at least for me. I'm not sure if people are hammering the servers due to the large mod updates released earlier, but there is definitely a performance issue on the repository. This is likely causing the error messages listed above. Guess I'll just have to hit the repository off peak hours.