Skip to content

Releases

BattleTech: Unofficial Community Update (UCU) 2.1.5-2B

Choose a tag to compare

@InternetDadCo InternetDadCo released this 16 Nov 13:43

You need two things: the BattleTech UCU launcher (download BattleTechUCUSetup.exe below) and BATTLETECH itself, installed through Steam or GOG. The launcher finds your copy, installs UCU to a new folder beside it and starts the game; your own BATTLETECH isn't changed. To update, run the launcher again: it keeps a copy of itself in your install folder as BattleTech UCU Launcher.exe.

2.1.5-2B (BT-UCU Beta 2.5)

  • GOG support. UCU now runs on both the GOG and Steam editions of BATTLETECH. On a GOG install,
    the installer finds your GOG install, then copies the GOG files UCU needs from your
    GOG folder, including the markers for the DLC you own there. In the game, Flashpoint, Urban Warfare and Heavy Metal
    follow your GOG ownership, saves go to GOG Galaxy (synced to the cloud when Galaxy is signed in) and achievements go
    to your GOG account; Steam isn't needed. GOG's own BATTLETECH lists the saves UCU makes there. If you buy a DLC on
    GOG after installing UCU, run the installer again to repair your UCU folder and it picks the DLC up.
  • Co-op join stuck on "Receiving the campaign..." with big careers (issue #9). A joining player asked the host for the
    campaign again every five seconds and threw away what had already arrived, so a career too big to arrive in five
    seconds (a BattleTech Advanced career is about 12 MB) never finished loading, and the host stalled each time it
    rebuilt it. The joining player now keeps the download while it is still arriving. If the campaign arrives but
    can't be loaded, the joining player now sees a message and returns to the main menu instead of waiting forever.
  • The installer is now a launcher. The same window has five tabs: Home shows your installed version against the
    newest release and starts the game; Install / Update is the installer; Mods turns mod support on or off and links
    or copies a mod pack you installed for retail BATTLETECH (BattleTech Advanced, RogueTech, or another ModTek pack), so
    Link BTA.cmd is no longer needed; Settings picks DirectX 11 or 12 (12 has no benefit yet) and extra launch
    options; Tools verifies the install, opens the log and save-backup folders, and makes a desktop or Start menu
    shortcut. After installing, the launcher keeps a copy of itself in the install folder as BattleTech UCU Launcher.exe, so you no longer need the download to update. RogueTech has not been tested on UCU yet.
  • Mod packs on Linux and Steam Deck (issue #13). Under Proton, BattleTech Advanced 20.3 and other packs on ModTek 4.4.x no
    longer get stuck repeating an error while they load ("ModTek died"). The MonoMod library that ships with ModTek 4.4.x could write
    broken jumps in the game's code when the memory next to that code was full, which happens with UCU's newer Unity
    under Proton. UCU's mod loader now applies MonoMod's own fix for this (MonoMod pull request 308, credit to the
    MonoMod team). With ModTek 4.5.1 or later, which already includes the fix, or without ModTek, it does nothing.
    Tested under Proton: BattleTech Advanced 20.3 loads and plays a skirmish. On Windows it plays as before. Not yet
    tested under Proton: a BattleTech Advanced career or loading saves.
  • Mods that look for the game's popup layer (issue #16). UCU gave the layer that holds pop-ups a
    different name from the original game, so a mod that finds it by name got nothing. In LootMagnet's shift-click sale
    on the salvage screen, that left the item in place after paying its value. The layer now has the original game's
    name, PopupRoot. The LootMagnet sale itself hasn't been re-tested with the fix yet. In BattleTech Advanced, shift-click
    selling is off by default and you sell by clicking the item's icon, which already worked on UCU.
  • Mech Bay tile outlines (issue #15). In the Mech Bay, the outline around each unit's
    tile and the frame around the selected tile didn't draw, because the two frame shapes pointed at the wrong data and
    came out empty. Both are drawn again.

Public manifest: ucu-manifest.tsv, SHA-256 f7aef26990ec5863b9524e5c466aff931787ae3b645f598277a3a4902880390e. It lists every file this release installs, with SHA-512 and origin; check an install with verify.ps1 or the installer's Verify install. GOG installs: ucu-manifest-gog.tsv, SHA-256 c2e8d8589b7bb03a6e6a78ca9430e8cb916152a0a48f11441f95ebd849d02da5.

BattleTech: Unofficial Community Update (UCU) 2.1.4-2B

Choose a tag to compare

@InternetDadCo InternetDadCo released this 15 Nov 23:20

Needs your own copy of BATTLETECH on Steam, installed and unmodified, and Steam running and signed in when you install and play.

  1. Download BattleTechUCUSetup.exe below and run it. It will download about 9 GB.
  2. The installer finds BATTLETECH, confirms with Steam that you own it, downloads the game and installs it to a new folder beside BATTLETECH. Your copy of BATTLETECH isn't changed, and no profile settings need changing. You must have an unmodified retail install or the installer will not proceed.
  3. Press Start game, or run BattleTech.exe in the install folder.

To update, run BattleTechUCUSetup.exe again and install to the same folder: it downloads only what changed. Windows SmartScreen may warn because the installer isn't signed yet.

What's new in 2.1.4-2B

  • Skirmish launch. Pressing Play on the skirmish setup screen right after the lances fill in could freeze the load: the game kept repeating the same error and the mission never started. The lance crests no longer try to draw on a screen that has already closed. This is a retail bug.
  • Co-op game data check. The check that both players have the same game data no longer depends on the order in which the files are listed on disk (with mods, that order came from the mod loader) or on line endings: a mod file with Windows line endings now counts the same as one with Unix line endings. Two BattleTech Advanced installs were refused because one PC's copies of the CAB mech packs had Windows line endings and the other's Unix ones, with the same content. This is a retail bug. The game also writes mp-defhash.tsv next to Player.log (in AppData\LocalLow\BTUCU\BattleTechUCU) when it starts, hosts or joins: one line per file in the check. If a join is refused with "Game data mismatch (def hash)", the two players can compare their copies to see which files differ. With BattleTech Advanced, first make sure both players have the same BTA version: the join compares mod names, not versions.
  • Blank rows on the salvage screen (issue #8, also seen in issue #7). After a few contracts in one session, some salvage rows took up space but showed nothing: the item could still be picked or was handed out at random, but you could not see it. The same blank rows could turn up in other item lists that reuse them, such as the Mech Lab inventory, until a restart. When the salvage screen closed, the game threw the old screen away in the same moment it moved the rows out to be reused, and the rows came back switched off. The game now throws those screens away at the end of the frame, after the rows are out.
  • Loading a mid-battle save with mods. The game's file loader could get stuck for good on one file while it loaded a saved battle: the mission's load screen came up, but BEGIN did nothing. It happened when a faction's logo was still loading for one part of the game while the faction itself loaded for another. This showed on every mid-battle save loaded with BattleTech Advanced. This is a retail bug. BattleTech Advanced keeps mid-battle saves off by default, and other faults remain before those saves play on.
  • Smaller installs on the same drive as BATTLETECH. About 11 GiB of UCU's files are identical to files in your own BATTLETECH install. When UCU is installed on the same NTFS drive, the installer now links the large ones (asset bundles, map data, videos and sound banks, 10.8 GiB) to BATTLETECH's instead of copying them, so they take no extra space; it checks each one first, as before. Code and every text or data file you might edit, such as the JSON files, are still copied, so editing them in UCU's folder never changes BATTLETECH. On another drive the installer copies everything and says so. An existing install on the same drive switches the next time you run the installer. Uninstalling or moving BATTLETECH doesn't break UCU: a link is the file itself.
  • Link BTA with more than one UCU install. Run from an install's ModSupport folder, Link BTA.cmd and link-bta.sh now link that install, instead of listing every UCU install in your Steam libraries and asking.
  • Ghosting and smeared ground with anti-aliasing and motion blur. On High settings, trees and foliage left ghost trails and the ground flickered and smeared, even with the camera still. Unity 6 drew the game's trees into the motion pass that the anti-aliasing and motion blur read, with false movement of hundreds of pixels; retail draws none there. Trees and foliage now give only the camera's own movement, as on retail.
  • Data folder renamed. The game's saves, profiles, settings and Player.log now live in AppData\LocalLow\BTUCU\BattleTechUCU, not AppData\LocalLow\DefaultCompany\BattleTechU6. On the first start the game moves your saves, profiles and settings from the old folder, and on Windows (and under Proton) also copies the game's settings from the registry, such as whether mods are on; then it deletes the old folder and registry key. During that first start the window opens at the default size, then changes once to your old window size and mode; later starts open that way. If your old size is missing or no longer fits the screen, the game keeps the default window. Which monitor the window was on is not restored. If something stops the move, the old folder is kept and the next start tries again, so nothing is lost.
  • Unit picks with large mod packs. With big mod packs such as BattleTech Advanced, a lance or contract that picks its units by tags could match more than 999 groups of tags. The game's SQLite 3.16.2 refuses a query that size ("too many SQL variables"), so that unit pick failed with an error instead of choosing a unit. UCU now ships SQLite 3.54.1, whose limit is 32,766: in our tests with BattleTech Advanced loaded it answers all 132 such queries that 3.16.2 refused, as the SQLite 3.38.2 that BattleTech Advanced installs for the original game does. Without mods the game never comes near the limit.
  • Known issue: memory in long sessions. Memory use grows during a long session, about 1.5 GB above the original game after three missions and then about 200 MB per mission (around 9 GB after twelve). The original game also grows as you play. Restarting the game returns the memory. We are still working on it.

Public manifest: ucu-manifest.tsv, SHA-256 bfb7cdaf4ae99a2ba251cd3873af8329fe3c147bc943113b1669c7e282682a63. It lists every file this release installs, with SHA-512 and origin; check an install with verify.ps1 or the installer's Verify install.

BattleTech: Unofficial Community Update (UCU) 2.1.3-2B

Choose a tag to compare

@InternetDadCo InternetDadCo released this 15 Nov 03:10

Needs your own copy of BATTLETECH on Steam, installed and unmodified, and Steam running and signed in when you install and play.

  1. Download BattleTechUCUSetup.exe below and run it. It will download about 9 GB.
  2. The installer finds BATTLETECH, confirms with Steam that you own it, downloads the game and installs it to a new folder beside BATTLETECH. Your copy of BATTLETECH isn't changed, and no profile settings need changing. You must have an unmodified retail install or the installer will not proceed.
  3. Press Start game, or run BattleTech.exe in the install folder.

To update, run BattleTechUCUSetup.exe again and install to the same folder: it downloads only what changed. Windows SmartScreen may warn because the installer isn't signed yet.

What's new in 2.1.3-2B

  • Memory after loading a save. Every career you loaded in one session (Continue, Load, or a new career after going back to the main menu) left the previous career in memory, star map and all, because two of the game's own listeners never let go of it. Loading a save now releases the career you left. This is a retail bug.
  • Link BTA without the copy. Link BTA.cmd now links BTA's mod folders into UCU instead of copying about 20 GB, and BTA updates reach UCU without a re-run. Both games then share those folders: UCU writes mod logs and settings into the BTA install, and a mod turned off in one is off in the other. Link BTA (copy).cmd copies as before, and re-running either switches an install. Contributed by gkirkpatrick.
  • Link BTA on Linux and Steam Deck. link-bta.sh in ModSupport does the same under Proton: it links BTA's mod folders with symbolic links (or copies them with --copy) and tells you the Steam launch option the mod loader needs. It has been tested only on Windows' built-in Linux with a stand-in BTA folder, not yet under Proton or on a Steam Deck.
  • BattleTech Advanced: fast preloading (issue #4). With CustomPrewarm's caching turned on, the first start failed to write the cache and turned caching off again. The mod needs a small piece of .NET that the new engine does not ship. The mod loader now supplies it, so the cache is written once and later starts read it. In our test with BTA (Core 20.3), a save loaded in about 25 seconds with the cache, against 62.5 seconds without. Reported, with the fix, by gkirkpatrick.
  • BattleTech Advanced: fast preloading with BTA's backgrounds (issue #5). CustomPrewarm's cache build also stopped on BTA's career backgrounds, on retail as well, and turned caching off. The mod loader now works around that mod bug, so BTA can use the cache. Caching stays off unless you or BTA turn it on; if it already turned itself off, set UseFastPreloading back to true. Reported, with the fix, by gkirkpatrick.

Public manifest: ucu-manifest.tsv, SHA-256 dbdb381781a328cf781aa9dba8a40fc54f21dd8220033694316607bc860c8245. It lists every file this release installs, with SHA-512 and origin; check an install with verify.ps1 or the installer's Verify install.

BattleTech: Unofficial Community Update (UCU) 2.1.1-2B

Choose a tag to compare

@InternetDadCo InternetDadCo released this 14 Nov 21:09

Change the default 'notes' on the ReleaseManager to the following:

Needs your own copy of BATTLETECH on Steam, installed and unmodified, and Steam running and signed in when you install and play.

  1. Download BattleTechUCUSetup.exe below and run it. It will download about 9 GB.
  2. The installer finds BATTLETECH, confirms with Steam that you own it, downloads the game and installs it to a new folder beside BATTLETECH. Your copy of BATTLETECH isn't changed, and no profile settings need changing. You must have an unmodified retail install or the installer will not proceed.
  3. Press Start game, or run BattleTech.exe in the install folder.

To update, run BattleTechUCUSetup.exe again and install to the same folder: it downloads only what changed. Windows SmartScreen may warn because the installer isn't signed yet.

Public manifest: ucu-manifest.tsv, SHA-256 fb5483938b808e3efc496d3613931be5e0e0bcdf8fd6afcc5641c3ef3a61663d. It lists every file this release installs, with SHA-512 and origin; check an install with verify.ps1 or the installer's Verify install.

BattleTech: Unofficial Community Update (UCU) 2.1.0-2B

Choose a tag to compare

@InternetDadCo InternetDadCo released this 14 Nov 16:16

Needs your own copy of BATTLETECH on Steam, installed and unmodified, and Steam running and signed in when you install and play.

  1. Download BattleTechUCUSetup.exe below and run it. That's the only file you need: it downloads the game itself.

  2. The installer finds BATTLETECH, confirms with Steam that you own it, downloads the game and installs it to a new folder beside BATTLETECH. Your copy of BATTLETECH isn't changed, and no profile settings need changing.

  3. Press Start game, or run BattleTech.exe in the install folder.

To update, run BattleTechUCUSetup.exe again and install to the same folder: it downloads only what changed. Windows SmartScreen may warn because the installer isn't signed yet.

Public manifest: ucu-manifest.tsv, SHA-256 e170be6236980de1bc62b087529edbc6a2cc6a916b34d309f30f95e0ec291402. It lists every file this release installs, with SHA-512 and origin; check an install with verify.ps1 or the installer's Verify install.

BattleTech: Unofficial Community Update (UCU) 2.0.0-1B

Choose a tag to compare

@InternetDadCo InternetDadCo released this 13 Nov 19:01

Needs your own copy of BATTLETECH on Steam, installed and unmodified, and Steam running and signed in when you install and play.

  1. Download BattleTechUCUSetup.exe below and run it. That's the only file you need: it downloads the game itself.
  2. The installer finds BATTLETECH, confirms with Steam that you own it, downloads the game and installs it to a new folder beside BATTLETECH. Your copy of BATTLETECH isn't changed, and no profile settings need changing.
  3. Press Start game, or run BattleTech.exe in the install folder.

To update, run BattleTechUCUSetup.exe again and install to the same folder: it downloads only what changed. Windows SmartScreen may warn because the installer isn't signed yet.