News • Armarize

Some of the changes from today's update are already known for those who upgraded to v1.4.1.1 but I have added some more improvements and bugfixes since then. Especially the dependency as well as compatibility handling for modifications has been greatly improved. This update is also the second one which drops a feature that was added with v1.3: The contact list. This is because it experienced too little usage in the last few months and I do not think that I will increase its set of features some day, so it's probably not a great loss anyway.

[FEATURE] It is now possible to filter gameservers based on their location.
[BUGFIX] Filtering based on "similar" versions works now for ArmA3.
[BUGFIX] Crash when less than four rsync mirrors are detected as available/reachable.
[BUGFIX] Crash when removing a modification directory after a package directory has just been added.
[BUGFIX] If ArmA2 or ArmA2OA is not installed Armarize requests the installation directory only once.
[BUGFIX] When switching between profiles in the serverbrowser the server list will not be filtered multiple times anymore.
[CHANGE] Disabled contact list.
[IMPROVEMENT] Improved compatibility and dependency handling.
[IMPROVEMENT] The serverbrowser considers now the reqBuild gameserver information.

If you have already installed Armarize, just start it. Otherwise:

The ArmA3 alpha is finally out and one third of the community curses BI for how we open our "g"ear by default, another third thinks the splash screen should state that its "madness" when they look at the bug tracker and the remaining third happily plays the game. While I am part of the remaining one I have adjusted Armarize besides so that it supports ArmA3 natively.

But there are also some bugfixes and improvements included in this update because not everything worked well after the update to v1.4. Especially the synchronisation should run much smoother as its a bit more obstinate in case a mirror does not answer right away.

[FEATURE] Added native support for ArmA3.
[BUGFIX] Crash when connecting to a server via manual mod selection where mods are running which are broken on the client side.
[BUGFIX] The Operation Arrowhead beta patch will not be marked as broken anymore after an update or repair.
[BUGFIX] Crash when starting a synchronisation while Armarize is running without administrator rights.
[BUGFIX] Crash when trying to delete a profile within the server browser while no profile exists.
[BUGFIX] Searching for a player aborted a running browser refresh.
[IMPROVEMENT] Added possibility to change the loadorder with drag and drop when connecting to a server via manual mod selection.
[IMPROVEMENT] When the network utilisation is set to "Next to nothing" it is now possible to abort a running browser refresh.
[IMPROVEMENT] The synchronisation is now a bit more tolerant in case the mirrors are overloaded where it tries to connect to.

If you have already installed Armarize, just start it. Otherwise:

Nearly five months passed since the last full update and its incremental successors. That is a long time, and definitely my personal record, but I suppose there was not any need for a new update as Armarize ran very stable. Though this stability might be a little bit affected with today's update as I changed much parts of the code and did a bunch of minor improvements. But I hope that I had enough time to ensure that everything is working well...

This update also introduces a new feature which was requested a few days after the first release of Armarize: Drag & Drop when changing the loadorder of mods. (Another record beaten!) I have also integrated the functionality for creating groups of modifications which gives finer grained control how modifications are loaded when launching the game. And to facilitate joining on a gameserver it is now possible to link a specific profile with one so that this profile is used when joining.

The next major update will also introduce a feature that was long awaited by some of you: Custom synchronisation repositories. Though rsync will be the only supported type of repository initially and zsync might follow some time later.

[FEATURE] Added possibility to create groups of modifications.
[FEATURE] It is now possible to link profiles with favorite/history gameservers.
[FEATURE] Changing the loadorder of modifications is now also possible with drag and drop.
[IMPROVEMENT] Decreased memory usage.
[IMPROVEMENT] Increased performance of the server browser.
[IMPROVEMENT] Removed some unnecessary confirmation dialogs.
[IMPROVEMENT] System language is now set automatically on the first run, if available.
[IMPROVEMENT] Some context sensitive as well as graphical parts of the UI were reworked.
[IMPROVEMENT] A dummy "addons"-directory is not necessary anymore to detect the OA beta patch.
[IMPROVEMENT] Auto update initialisation is now a bit more tolerant in case the downloaded installer is being scanned by anti virus software or the like.
[IMPROVEMENT] When status notification is enabled the icons wont be reset anymore when Armarize is not in the foreground and the status of a server has changed.
[BUGFIX] Rare crash when refreshing the browser.
[BUGFIX] Crash when the game could not be started.
[BUGFIX] Performance hits caused by redundant data aggregation.
[BUGFIX] Random crashes due to incorrect parallelisation logics.
[BUGFIX] Synchronisation with the modifications running on a gameserver is working again.
[BUGFIX] Fixed that modifications were sometimes installed at an incorrect location or listed multiple times.

If you have already installed Armarize, just start it. Otherwise:

As I released Armarize 1.3 I mentioned a few reasons why I started with its development. One reason was to get more experience in application development. This means that some parts of the source code are somewhat unstructured and I felt a bit like an "adventurer" as I implemented support for Take On Helicopters the last days... However, it is done now and Armarize got also a few other features:

[FEATURE] Added native support for ArmA2 Free and Take On Helicopters.
[FEATURE] It is now possible to define per profile which game will be started by default.
[FEATURE] It is now possible to disable the use of the custom executable defined within a profile.
[FEATURE] It is now possible to display a preview of the command-line that is used to start the game.
[BUGFIX] Crash when removing a favorite gameserver or adding a new one.
[BUGFIX] Crash when joining on a gameserver where a buddy is playing.
[BUGFIX] Crash when the favorites were refreshed automatically.

If you have already installed Armarize, just start it. Otherwise: