•     Please make sure you check the Support FAQ and relevant Guides before you create a new thread in this section!

[SOLVED] Guide to install MB II on MAC / Macintosh

Status
Not open for further replies.
Posts
1
Likes
0
Hello guys, been a few years since i have been here playing. But i decided to install this wonderful mod on Mac and it took me a while to get it working.

Anyway heres a guide to make it easy for you all Mac guys :)

Download the game on Steam.

Download the Modification
Star Wars: Movie Battles II v1.3.1 download

Open Steam Folder.
> Right click on game Jedi Knight: Jedi Academy
> Properties
> Local Files
> Browse Local Files

You will find the folder " Star Wars Jedi Knight: Jedi Academy "
> Right click
> Show package contents

You will see folder
" Contents " and " installscript_osx.vdf "
> click and open Contents
> Move ALL FILES from the newly downloaded Modification folder ( mb2-v1-3 ) into " Contents " ( Equivalent of Game Data in MAC )

Go to folder " MB II "
Copy " z_MB_BaseAssets.pk3 " from MB II folder and paste into Base folder ( This will remove any bugs with models )
Remove the remaining " z_MB_BaseAssets.pk3 " in folder MB II

Download Jedi Academy MP Launcher
http://jkhub.org/files/file/1019-jedi-academy-mp-launcher-for-os-x/
> Open folder
> Move "JKJALaunch.app" into Jedi Academy folder ( Will appear beside " Star Wars Jedi Knight: Jedi Academy " )
> Double click " JKJALaunch.app "

Choose Multiplayer.
> Go to SETUP
> Load MB II Mod

And finally
> Go to SETUP
> Game Options
> Turn " Allow Downloads " to OFF

You are done! Happy gaming :) See you on the servers.

( Instructions are still the same if .app is not shown after your files, it just depends on your settings )

* If you for some reason need to use the console the command is " SHIFT " + " < " for Mac
 
Last edited:
Posts
108
Likes
10
can you provide the full stack trace ?
I tried several launchers. The JKJA launcher got me up to the point of joining a server form the actual in game server list, but would crash to the desktop after a couple of seconds. The second launcher, simply named MBII launcher, (Spaghetti provided the link) crashed upon double clicking it. I tried to open it a different way by going into its contents and using terminal to watch what happened as it started to launch. However, I don't know any C++ so it didn't help... What is a full stack trace?
 
Posts
108
Likes
10
I tried several launchers. The JKJA launcher got me up to the point of joining a server form the actual in game server list, but would crash to the desktop after a couple of seconds. The second launcher, simply named MBII launcher, (Spaghetti provided the link) crashed upon double clicking it. I tried to open it a different way by going into its contents and using terminal to watch what happened as it started to launch. However, I don't know any C++ so it didn't help... What is a full stack trace?
Maybe this could be a problem, idk for sure though just brainstorming. When I launch the version given from this post, which is 1.3.1, in the bottom right of the moviebattles start screen, it says 1.3.0.... Could that be the problem? Because the 1.3.2 halloween update is supposed to just be an upgrade right, not an entire file???? Any ideas?
 

kikili

Movie Battles II Team
Posts
151
Likes
46
I was meaning when you tried to execute the "launcher" through terminal, you just provide a screenshot.
Can do it again and provide a copy/paste of the entire text inside the terminal starting from your command
 
Posts
108
Likes
10
I was meaning when you tried to execute the "launcher" through terminal, you just provide a screenshot.
Can do it again and provide a copy/paste of the entire text inside the terminal starting from your command
Last login: Sat Nov 21 23:03:06 on ttys000

Ps-MacBook:~ Parker$ /Users/Parker/Library/Application\ Support/Steam/SteamApps/common/Jedi\ Academy/SWJKJA.app/Contents/MBII\ Launcher.app/Contents/MacOS/MBIILauncher ; exit;

* Assertion at class.c:5078, condition `class' not met



Native stacktrace:


0 libmonoboehm-2.0.dylib 0x00776be6 mono_handle_native_sigsegv + 342

1 libmonoboehm-2.0.dylib 0x007c72f1 sigabrt_signal_handler + 129

2 libsystem_platform.dylib 0x97b1179b _sigtramp + 43

3 ??? 0xffffffff 0x0 + 4294967295

4 libsystem_c.dylib 0x9c8a58c8 abort + 156

5 libmonoboehm-2.0.dylib 0x008e9ec1 monoeg_log_default_handler + 129

6 libmonoboehm-2.0.dylib 0x008e9fbb monoeg_assertion_message + 107

7 libmonoboehm-2.0.dylib 0x007d529a mono_class_init + 1450

8 libmonoboehm-2.0.dylib 0x007e094e mono_class_get_method_from_name_flags + 46

9 libmonoboehm-2.0.dylib 0x007e2c37 mono_class_get_method_from_name + 39

10 libmonoboehm-2.0.dylib 0x0088628c mono_init_internal + 4268

11 libmonoboehm-2.0.dylib 0x00886c78 mono_init_from_assembly + 24

12 libmonoboehm-2.0.dylib 0x006c568f mini_init + 2063

13 libmonoboehm-2.0.dylib 0x00741200 mono_main + 4912

14 MBIILauncher 0x0002ead8 main + 424

15 libdyld.dylib 0x9622f6ad start + 1


Debug info from gdb:


(lldb) command source -s 0 '/tmp/mono-gdb-commands.o85uZU'

Executing commands in '/tmp/mono-gdb-commands.o85uZU'.

(lldb) process attach --pid 3972

Process 3972 stopped

* thread #1: tid = 0x30162, 0x94d34da6 libsystem_kernel.dylib`__wait4 + 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP

frame #0: 0x94d34da6 libsystem_kernel.dylib`__wait4 + 10

libsystem_kernel.dylib`__wait4:

-> 0x94d34da6 <+10>: jae 0x94d34db6 ; <+26>

0x94d34da8 <+12>: calll 0x94d34dad ; <+17>

0x94d34dad <+17>: popl %edx

0x94d34dae <+18>: movl 0xe3c3277(%edx), %edx


Executable module set to "/Users/Parker/Library/Application Support/Steam/SteamApps/common/Jedi Academy/SWJKJA.app/Contents/MBII Launcher.app/Contents/MacOS/MBIILauncher".

Architecture set to: i386-apple-macosx.

(lldb) thread list

Process 3972 stopped

* thread #1: tid = 0x30162, 0x94d34da6 libsystem_kernel.dylib`__wait4 + 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP

(lldb) thread backtrace all

* thread #1: tid = 0x30162, 0x94d34da6 libsystem_kernel.dylib`__wait4 + 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP

* frame #0: 0x94d34da6 libsystem_kernel.dylib`__wait4 + 10

frame #1: 0x9c8c5541 libsystem_c.dylib`waitpid$UNIX2003 + 48

frame #2: 0x00776cad libmonoboehm-2.0.dylib`mono_handle_native_sigsegv(signal=6, ctx=0xbffd352c, info=0xbffd34ec) + 541 at mini-exceptions.c:2193 [opt]

frame #3: 0x007c72f1 libmonoboehm-2.0.dylib`sigabrt_signal_handler(_dummy=<unavailable>, _info=<unavailable>, context=<unavailable>) + 129 at mini-posix.c:208 [opt]

frame #4: 0x97b1179b libsystem_platform.dylib`_sigtramp + 43

frame #5: 0x94d3462b libsystem_kernel.dylib`__pthread_kill + 11

frame #6: 0x97b1c664 libsystem_pthread.dylib`pthread_kill + 101

frame #7: 0x9c8a58c8 libsystem_c.dylib`abort + 156

frame #8: 0x008e9ec1 libmonoboehm-2.0.dylib`monoeg_log_default_handler(log_domain=<unavailable>, log_level=<unavailable>, message=<unavailable>, unused_data=<unavailable>) + 129 at goutput.c:233 [opt]

frame #9: 0x008e9fbb libmonoboehm-2.0.dylib`monoeg_assertion_message [inlined] monoeg_g_logv(log_level=G_LOG_LEVEL_ERROR, format=<unavailable>) + 85 at goutput.c:113 [opt]

frame #10: 0x008e9f66 libmonoboehm-2.0.dylib`monoeg_assertion_message(format=<unavailable>) + 22 at goutput.c:133 [opt]

frame #11: 0x007d529a libmonoboehm-2.0.dylib`mono_class_init(class=<unavailable>) + 1450 at class.c:5078 [opt]

frame #12: 0x007e094e libmonoboehm-2.0.dylib`mono_class_get_method_from_name_flags(klass=0x00000000, name=<unavailable>, param_count=<unavailable>, flags=2050270320) + 46 at class.c:9676 [opt]

frame #13: 0x007e2c37 libmonoboehm-2.0.dylib`mono_class_get_method_from_name(klass=0x00000000, name="PerformWaitCallback", param_count=0) + 39 at class.c:9616 [opt]

frame #14: 0x0088628c libmonoboehm-2.0.dylib`mono_init_internal(filename=<unavailable>, exe_filename=<unavailable>, runtime_version=<unavailable>) + 4268 at domain.c:848 [opt]

frame #15: 0x00886c78 libmonoboehm-2.0.dylib`mono_init_from_assembly(domain_name="MBIILauncher.exe", filename="MBIILauncher.exe") + 24 at domain.c:893 [opt]

frame #16: 0x006c568f libmonoboehm-2.0.dylib`mini_init(filename=<unavailable>, runtime_version=<unavailable>) + 2063 at mini-runtime.c:3069 [opt]

frame #17: 0x00741200 libmonoboehm-2.0.dylib`mono_main(argc=2, argv=0x79f07220) + 4912 at driver.c:1907 [opt]

frame #18: 0x0002ead8 MBIILauncher`main(argc=1, argv=0xbffd3b44) + 424 at temp.c:244

frame #19: 0x9622f6ad libdyld.dylib`start + 1

(lldb) detach


=================================================================

Got a SIGABRT while executing native code. This usually indicates

a fatal error in the mono runtime or one of the native libraries

used by your application.

=================================================================


Process 3972 detached

(lldb) quit

Abort trap: 6

logout

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.


[Process completed]
 
Posts
108
Likes
10
I was meaning when you tried to execute the "launcher" through terminal, you just provide a screenshot.
Can do it again and provide a copy/paste of the entire text inside the terminal starting from your command
Ok wait. For some reason everyone switched servers from last night, they arent on the first open type one. But now I can join that server because no one is in it.... What does this mean? Btw, I just tried this with the JKJA launcher
 
Posts
108
Likes
10
Update: Only has worked on the Hoth map.... The AOD 24/7 Stopming Grounds is now on republic cruser and I cant join. Maybe I'm missing maps???? However, this doesnt get rid of the fact that when someone was joining the hoth map i could play, I would get kicked out.... Hope to play this soon
 
Posts
108
Likes
10
Update: I've been trying to just get windows on a partition of my hard drive to make things easier, which hasn't been easy at all... But.. as I've researched how to do this, I've found that I'm on the most recent OS X el Capitan, a public beta software. I'll attempt to downgrade and then see if I can get this mod working. If not, the downgrade to a fully functional OS might help in the process of getting windows on a partitioned drive.
 

redsaurus

Movie Battles II Team Retired
Posts
115
Likes
114
It's probably not worth downgrading or installing windows just for MBII.

When you were doing the manual install, did you download the 1.3.1 full and install that before doing the 1.3.2 update? You'd just want to copy the files from the MBII folder in the 1.3.2 update into the MBII folder from 1.3.1.
 
Status
Not open for further replies.
Top