major_shepard

LEA 1.4 Update 3 Build 1.4.75 --- Downloads --- => Check for Updates in the Help menu. => Use windows installer: ftp://www.sonsofexiled.fr/ArmA2/LEA/download/lea-installer-1-4-75.exe --- Changelog --- Fixed: Mission Editor: compatibility with ArmA 2 OA patch v1.63. Script error displayed in game when a slot is disabled.

Are you sure to run @CBA_A3?

Thanks ^^ How do you set ArmA3Sync to launch your ArmA3Server on the Linux machine?

Yeah make a mistake, the correct file structure is @LEA_A3/Addons/lea.pbo Re-uploading the shit :rolleyes:

Menu -> Help -> Install @LEA

LEA v2.0 Update 5 Download Use Check for Updates in the Help menu or use Windows automatic installer: ftp://www.sonsofexiled.fr/ArmA3/LEA/releases/lea-installer-2-0-20.exe Changelog - Updated: @LEA to v1.3 - Added: Virtual Arsenal integrated within @LEA. - Fixed: @LEA: Apply Loadout does not kept available upon 5 minutes even if the player stays in the 100 meters close to his spawning location. - Fixed: Right clicking on uniform/vest/backpack does not work sometimes. - Added: keep default helmet and glasses as options.

VA integration within LEA http://i191.photobucket.com/albums/z155/Bazooca1/lea_va_zps88549938.png (785 kB)

The thing is that there is no convention in the way people play. To sum up we have people who play on public servers and others who play on private servers along with a team. ArmA3Sync addresses foremost the second category. Team players tipically want to be able to host there own (private) addons, in specific version. They want control over the update process and ensure their player base will match the mission requirement at D day. So far as I understand, BIS Launcher intend to deserve the first category. For these guys, being able to grap the last available update of a given addon is the foremost priority.

Working successfully here, I expect you set the wrong url for the repository in ArmA3Sync, which may also have something to do with the upload.check your PM.

Check your PM.

Try to reupload the /.a3s folder

Are you sure to have set the transfer mode as Binary?

Use WINSCP or whatever to upload the repository. Be sure to set binary transfer mode before uploading.

survive... adapt... win... and stop bitching

Well I also try to upload on my FTP, I get the same result. So as a workaround for now, just create the repository folder on the FTP before uploading the files. Fixed for next update.

OK. So I have done 2 tests on your ftp: 1- I created a folder named TEST on your repository then uploaded successfully my local repo to the remote target ftp://..../TEST. Check for Addons and download worked fine. 2- I directly upload my local repo to the remote target without creating the TEST folder on the ftp => upload failed with wrong remote file structure.

Nope. I gonna try to upload on your FTP with a repo name TEST. Do not delete it, thanks.

Could you give me your server info by PM? ---------- Post added at 09:59 PM ---------- Previous post was at 09:24 PM ---------- The sync is corrupted. How do you upload the repository ? Do you use the upload feature of ArmA3Sync?

I am not speaking about the missions but the "spirit" of the game: - massive lake of content (compared to A2) - massive lake of credibility of the ArmA3 story (NATO, CSAT forces etc) - shitty new stuff (Virtual Reality), shitty DLC incoming - complete lake of badly needed features like weapon resting, fast roping... ArmA gathered mature players since OFP time. These guys want quality content and are ready to pay for it.

Looks like the lead design of the ArmA series is more and more influenced by DAYZ, Altis no life and all that casual stuff. We seriously considering moving to VBS 3 PE, hoping they push it out at last.

Woo what a fucking pile of crap @MacShit Not simple to workaround that shit mate. Will check on my Linux Ubuntu about the upload of the hidden .a3s file what happens. This could be more easily workarounded and fixed. ---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ---------- -enableHT will be added with the next update of ArmA3Sync. Now on the server, we tipically edit the config file and set the checkSignatures=0/1, it's not what you do ?

The first thing to solve is the renaming of the files when building the repository which is not normal behaviour. ArmA3Sync is not responsible for that. As far as the file tructure is not correct after the build finished, upload/sync will failed.

When you build the repository is the file structure of the repository correct? (i.e no modification of the files name)

I expect you have built the repository on your MacShit and you are trying to upload the files to a remote FTP server right? How do you transfer the files? Do you use A3S upload functionnality?

The author of the upload uses as nickname a well known french site about FPS -> http://www.nofrag.com/ The big mess is beginning :rolleyes: