Dev Diary - New Launcher and Open Beta - A Guide

iwCSA26.png

Developer Diary - New Launcher and Open Beta

For some time it has been our ambition as a team to be able to be more open with the whole community with in progress development and testing. Those of you who view and follow the Development Roadmap will have not only been able to see the first glimpses of that philosophy but also what is coming down the pipeline to aid that. The cornerstone of all this is the Launcher - so today I am glad to announce the Open Beta of the new launcher ... which will enable Open Betas for MBII!

Where we've come from

Today's launcher has been end of life for some time. Work was started on it more than 11 years ago and the landscape of computing has changed immensely in that period. The approach to a cross platform application that can be rapidly developed, maintained and with the full power of the platform on which it runs available is no longer possible. The Mono framework appears to have become less compatible across platforms to the point where without making any changes at all to the application, the framework would no longer run it cross platform. Additionally the person who did most of the original work on the current Launcher did it in such a way that expanding the UI to expose new features - like an Open Beta feature was not possible. The only workable part of the current Launcher is the Patcher which was rewritten a few years ago in a modern cross platform technology.

A New Hope Launcher

We have totally re-written Launcher from the ground up with an eye on the future. This means we are looking to keep this as piece of the mod which can be updated quickly and easily and not be a drag on peoples time. The new Launcher - which is still unfinished beta software - will when complete have total feature parity with the existing launcher - with the exception of cross platform support via the mono framework. Unfortunately this reflects the reality of the world today where the existing Launcher does not reliably work for many people on Linux and Mac. Linux and Mac users should switch to the cross platform command line updater which uses the same code as the Windows patcher but runs natively via the open source dotnet Core framework. Dropping cross platform support entirely means we have been able to switch to platform standard Windows Installer technology that every windows user is already familiar with. For us this means that we no longer have to maintain two patchers and can offload the physical patching of the launcher to well proven technology provided by the platform.

Getting Started

Installing the new launcher is as simple as downloading the Installer Package and running through the Wizard. Please note the requirement to be installed in the GameData directory is gone - but feel free to install it there if you wish.

setup.png

You all know what to do with this

Once the installer is finished, a Short Cut will be placed on your desktop and in your Start Menu as you would expect. Hopefully this will cut down on the amount of players needing support because they cant find Launcher or try and run it directly from the Zip.

Shortcut.png

StartMenu.png

So you fire up new launcher and first things first - you need to scroll down and accept the EULA. The accept button is well hidden at the moment and is something that will be improved before the new Launcher leaves Open Beta.
EULA.png

Having Accepted the EULA the Launcher will - just like the old one - look for your Jedi Academy installation. If you chose to point the installation to your GameData folder you will likely not see this step unless your Jedi Academy installation does not meet the minimum criteria to be valid. The search will follow the same priority as the current launcher does which can basically by summerised as the most recent of Retail Disc, GoG, Any other digital platform other than steam - followed by Steam. If the auto detect picks up the wrong directory you can reject the location picked by Launcher and chose your own or pick again at any time from the settings menu.

Once you have found your installation you can go straight ahead and hit the Install button (And ignore where it says 'Initialising Patcher'...). Launcher will then check that your system has all the pre-requisites for MBII Installed - at the moment this is just the Visual C++ runtime and then move onto validating your Moviebattles installation. If your MBII installation is up to date this should take no longer than starting the old launcher would have. If on the other hand you've just sat down to write a Dev Diary - Enjoy the new install animation.

Install.png

Here's one i didn't prepare earlier.

Once patching is complete you will want to head over to the settings menu. You should set everything to as it is in the current Launcher - this should ensure everything stays working. And of course, to opt into the Open Beta CTF also happening tonight (1st of August 2021), you will want to hit the Enable Open Beta checkbox.

Settings.png

If an Open Beta is currently running you will then be able to select the Open Beta build on the left hand side of the screen. Upon selecting this the Launcher will begin to install the Open Beta files. Any files that are unchanged from the current public build to the open beta build will be copied locally. Any updated files (Or files that have been modified on your local system) will be reacquired from the server. No configurations or Force Config files will be copied from the public game - You will have to set up your keys, binds and builds from scratch.

Copying.png

Once patching is complete, you can simply hit play to load up the beta.

Should you wish to switch back to the public build, you simply need to click on the Release build in the settings menu

Once the Open Beta period ends Launcher will inform you and automatically switch you back to the public build.

Known Issues
  • Closing the launcher while the game is minimized will leave the game running in the background and can only be stopped with task manager.
  • An empty folder will be created next to the GameData folder at initial setup or file validation.
  • Steam is a strange animal. We strongly recommend any steam players close down the game, new and old launcher and repair the installation from steam before beginning. - Fixed 4.015.0
  • Not all minimize key combinations that were accepted by the old Launcher will work with the new Launcher - This is a known bug which we hope to resolve shortly. - Fixed 4.015.0
  • The help menu doesn't work - This is coming shortly.
  • There are issues sorting columns in the server list. - Fixed 4.015.0
  • For OpenJK Users when switching between release and Open Beta the engine will get forgotten but the UI will be incorrect. To fix this switch the engine to JAMP, then enable Steam Integration (Even for non-steam users), and then switch back to Open JK - This is a known bug which will be fixed shortly. - Fixed 4.0.6.0

You can download the Open Beta Launcher Installer Here
 
Last edited by a moderator:
Posts
220
Likes
286
JA: v1.0.1.0 win-x86 Oct 24 2003
Initialising zone memory .....
----- FS_Startup -----
ERROR: filename length > MAX_QPATH ( strlen(models/players/pl_rockettrooper/base_rockettrooper_rocket_spec.jpg) = 66)


I get this error when trying to launch beta
 

MaceMadunusus

Level Designer
Donator
Movie Battles II Team Retired
Posts
1,798
Likes
2,390
This got me hella hyped for Tempest patch, then I see this.

Do you want us testing the new system to make sure it all works with the more important beta, or the one of less consequence? We can run CTF beta for a single night to get some testing in, fix some things, run it again. Sabering beta has to be run for a week or two straight kinda thing. Gotta walk before we can run.
 
Posts
97
Likes
131
Hello, is there a possiblity for hosting an EU beta server ? (Mostly concerned for when it comes to sabering, where ping is such an important value).
I can propose/provide something about the hosting part, if needed.

Thanks you for the work.

P.S: After installing the launcher, when double-clicking on the icon, nothing is happening. There is no crash logs or error displayed. Also as administrator.
 

MaceMadunusus

Level Designer
Donator
Movie Battles II Team Retired
Posts
1,798
Likes
2,390
Hello, is there a possiblity for hosting an EU beta server ?

For sabering there will probably be one. For CTF for now probably not, unless enough people join where we can fill the full US server. But so far we haven't been close. It would be really appreciated for EU people to deal with higher ping to get things tested, as sometimes we just need bodies of people playing, not everyone playing at their 100%.
 
Posts
8
Likes
21
JA: v1.0.1.0 win-x86 Oct 24 2003
Initialising zone memory .....
----- FS_Startup -----
ERROR: filename length > MAX_QPATH ( strlen(models/players/pl_rockettrooper/base_rockettrooper_rocket_spec.jpg) = 66)


I get this error when trying to launch beta
Hey I got that as well, couldn't figure out how to fix it so I've just been using the mb2 client
 
Top