Search results

Every time? Starting with admin rights? Tried jamp client? Make sure there are no several instances of mbii, openjk and jamp instances running at the same time in the task manager (Ctrl+Shift+Esc).

A suggestion: record a video stream or at least a demo for those who missed. O:

/serverstatus Private clients always start from 0 to sv_privateclients-1. If you have such a number - you took a private slot. As a test, try to connect to a public slot and check your client number.

Roger. Little tip: if it's the same machine then just do "connect localhost:29070".

There is some private information. I already downloaded it, so remove your post. Send it in PM next time. You sent the wrong log. I am interested in the qconsole.log. To have it you have to set logfive 2. And send it just after the fatal error.

On server side: seta sv_maxclients "32" //max seta sv_privateclients "2" seta sv_privatepassword "9U-64dsefA" //public slots 30 (32-2) On client side: Via the console if the server not passworded (g_password is ""): /connect address:port; password 9U-64dsefA Or via main menu when the password...

So your game doesn't crash, it goes into fatal error if no crash logs appear. Show the game log.

Implementing the in-game voice transmission is very hard.

And how are you sure it is the crash if there is no crash log? Maybe you mean fatal error? Add +set developer "1" on startup next time. And set it also now for the current session.

You did not answer my question. All you had to do is to put "jampgamei386.so" into MBII folder.

Put what? Show the crash_log_[date].log in GameData folder (or whereever linuxjampded is placed).

How did you install the patch?

Then the first link is yours: http://www.moviebattles.org/download/servers/MBII_1.3.2_Server_Hotfix.zip

Are you using linuxjampded executable?

Did you install Server Hotfix and Crash Logger | Movie Battles II Community ?

Which solution?

Try to run the launcher w/ admin rights. If it doesn't help, try to change game client to MBII in the launcher settings.

You can only save them manually. Just bind "saveDemo" command and do not forget to hit it. Or "saveDemoLast" if you forgot. The design of autorecord is to only save the needed demos.

"add"? Are you sure? Should be "btn_chrg".

It is based on like 3 weeks old ojk which prolly wasn't even named so. And first commits included only all those known common fixes. That's all we need. I also cherry-picked some important things afterward manually if there were something definitely useful.