RUSE Mod Manager v1.1.10-beta

Added

• The Mod Manager now writes a startup.log next to itself every time it starts. If it ever
  fails to start, that file says how far it got and what went wrong, and the error message tells you
  where it is, so you can send it with a bug report. If the app's own folder cannot be written to -
  which is itself a common cause of a failed start - the log goes to your AppData folder instead.

Fixed

• The Mod Manager could get stuck running with no window. If something went wrong very early in
  startup - almost always because the folder the app lives in could not be written to - it tried to
  show you an error message, but that message could never actually appear on screen. The app then sat
  there forever: alive in Task Manager, no window, and closing it did nothing. Only End Task could
  stop it. While it was stuck it also blocked every new launch, so the app looked like it had stopped
  working for good, and installing a newer version did not help. Early messages now always show up,
  so you see what went wrong and the app carries on.
• Starting the Mod Manager while it is already running now does something you can see. Before,
  the second copy quietly closed itself after a few seconds and you saw nothing at all. Now it brings
  the window you already have to the front. If the copy that is running has no window, it tells you
  how to close it instead of leaving you guessing.
• Closed a leak that left invisible background processes behind. When the map editor was drawing
  terrain and the Mod Manager was killed or crashed, the 8 helper processes it uses to decode terrain
  kept running forever - each one showing up in Task Manager as another RUSE_ModManager, with no
  window, holding on to memory. They now shut down with the app.

Changed

Auto-updater asset: RUSE_ModManager_v1.1.10.exe
Full deploy bundle: RUSE_Mod_Manager_v1.1.10.zip (exe + mods/ + profile/)