Updated MBII Client Testing (Windows)

Spaghetti

Floating in the void
R2D2
Movie Battles II Team Retired
Posts
1,637
Likes
1,633
A handful of improvements have built up on MBII's OpenJK fork and I would like to give the updated engine some broader testing before it goes out to everyone through the launcher. The most noteworthy changes:
  • Clicking inside the game window or other input while loading should no longer interfere or cause the game to permanently freeze.
  • Steam integration (everything needed is bundled in the download)
    • Also helps with Discord recognizing the game for status / overlay / streaming.
    • Can be disabled with com_steamIntegration 0 in startup arguments if not wanted.
  • Set the Large Address Aware flag which should reduce instances of "VM_CreateLegacy on cgame failed" occurring.
    • This is a memory issue that also impacts the original engine JAMP (there it shuts down with "VM_Create on UI failed").
    • Technical details: LAA mitigates the issue by allowing more addressable memory range. For some reason DLLs were failing to load well before addressable memory is exhausted. Fortunately MBII does not actually use or need more memory - even in the most extreme testing we could not manage to use more than 2GB after loading dozens of maps and their FAs and every open model (VRAM exhaustion is very possible though).
  • Reduced size of demo recording text option and moved to bottom left of screen.
To test the engine update, download the attached ZIP and extract the contents to your GameData folder, overwriting when prompted. Also make sure that "MBII Client" is set as the engine in the launcher's options (if you are changing from JAMP for the first time then your settings will reset - this is normal as each engine maintains those separately).

Please report any issues or leave other relevant feedback in this thread.
 
Last edited:
Top