If you are a registered Ares tester then you should have been given instructions on how to enable access to the other Ares branches - information can be found in the Ares developer forum.

Launch Base does not allow Ares' files to be changed manually.

I'm not sure what you mean by "without Verbose logging even the automated download doesn't worked". The logging should not have any impact on the operation of Launch Base. Can you replicate the problem (i.e. turn off Verbose logging and see if the problem returns)? I suspect you have changed another setting somewhere.

I reinstalled LaunchBase and started everything again. After I checked Advanced Mode, I did a Syringe-Ares update and I got constantly Ares update failure. I tried putting 0.1 P1 into the Resources folder manually, but I got verification failures. Then somehow I ended up with revision 666 binary.

The LaunchBase update screen shows that the stable is version 710 (Ares 0.1 P1, isn't it?), although I think the checksums the validation uses are still the 666 versions' one. I think this, because ares.mix passes the verifying, and in the SVN, it's revision is 544, while both the dll and inj has revision number 710.

Hmm... I can't replicate that.
Can you delete ares.* from your Resource folder as well as any subfolders and try again?
If that doesn't work, then can you replicate with a clean installation of Launch Base?

It still looks like it wants to use revision 666 instead of revision 710. I even checked by manually downloading Ares 0.1 P1 and both it's Ares.dll and Ares.dll.inj is bigger than what Launch Base has.

Quote:I'm more concerned about the fact that no one reported this before.

I don't use LaunchBase with Ares (at least, not yet), otherwise I'd probably have noticed something. As Graion Dilach says, maybe LaunchBase just isn't widely used with the stable builds yet. If it was affecting the unstable builds, surely some of the testers would have noticed by now.