I deleted the deathball directory under ut2004 as well as ~/.ut2004/deathball directory and then extracted the deathball21.zip in to ut2004 directory so that there is deathball directory. My UT2k4 was first patched to 3236 version (latest official) but as DB 2.1 didn't work in it I installed the 3270 patch (which is still beta patch for linux). Error messages are same with both patches.
I have the same problem. My Deathball.log file looks the same. I really want to be able to play this mod too. It reminds me of Gridiron mod for quake3.
I reinstalled DB 2.0, launched it once, picked up the deathball.ini and then tried to launch DB 2.1c with that ini file. Here is deathball.log (interesting part is in bold):
Log: Log file open, Tue Aug 31 11:38:51 2004
Init: Name subsystem initialized
Init: Version: 3270 (127.29)
Init: Compiled: Jul 30 2004 06:54:16
Init: Command line: -mod=Deathball
Init: (This is Linux patch version 3270.0)
Init: Character set: Unicode
Init: Base directory: /home/sami/pelit/ut2004/System/
Init: Ini:../Deathball/System/Deathball.ini UserIni:../Deathball/System/DeathballUser.ini
Init: Build label: UT2004 Build UT2004_Patch_[2004-07-27_14.28]
Init: Object subsystem initialized
Warning: Missing Class Class Editor.TransBuffer
[B]Warning: Failed to load 'Class Deathball.DB_GameEngine': Failed to find object 'Class Deathball.DB_GameEngine'
Warning: Failed to find object 'Class Deathball.DB_GameEngine'
Critical: Failed to find object 'Class Deathball.DB_GameEngine'[/B]
Exit: Executing UObject::StaticShutdownAfterError
Exit: Exiting.
Log: FileManager: Reading 0 GByte 2 MByte 882 KByte 264 Bytes from HD took 0.007553 seconds (0.006578 reading, 0.000975 seeking).
Log: FileManager: 0.000000 seconds spent with misc. duties
Uninitialized: Name subsystem shut down
Uninitialized: Log file closed, Tue Aug 31 11:38:52 2004
I believe that those warnings happens because of some internal changes from DB 2.0 to 2.1 and the settings in the ini file are wrong due to those changes.
Just a thought but, should it display DB's own splash screen when starting DB or the UT2k4's default splash screen? For me it displays the UT2k4's splash screen till it crashes/quits.
From the old fix for a the 2.0 problem in linux i found this.
Originally posted by ivionojon
Open deathball.ini and find the GameEngine=Deathball.DB_GameEngine line. Change it to GameEngine=Engine.GameEngine and it will work.
mmm i can play 2.1c doing what i said above..
But i dont have anything custom to DB e.g cant change the players apperance, or have the options in controls for Curve left right.. just next weapon and so on.
It may be my deathball.ini
On that note.. can TV stick to using Deathball or deathball for files it does make a big difference.
FireCell,
That fix 'GameEngine=Engine.GameEngine' does not seem to be necessary with 2.1 because my Deathball.ini already has that set by default. I still can not launch the game without a seg fault. I have not tried any other Deathball.ini file besides the default.
First of all. Team Vortex, could you please keep the file names exactly the same in each version/update/whatever? I could have solved this yesterday if a certain file would have been named the sameway in DB 2.1c as it was in DB 2.1...
Anyways, here's how to get DB 2.1c to work under linux. Extract deathball21.zip and deathball21cudpate.zip to your ut2004 folder. Go to ut2004/deathball/System and delete Deathball.u (notice big D) and rename deathball.u to Deathball.u (thanks to this I kept having "package mismatch error"). Then edit ~/.ut2004/deathball/system/Deathball.ini like this:
mm thats weird cause i have it playable my way but not fully. Ill try this your way as well.
Tried it your way and seems the same, i cant edit my player at all. Also the controls in the configure screen are not Deathball specific (e.g ball curve left/right).
Last edited by FireCell on 01-09-2004 12:58, edited 1 time in total.
FireCell, you might have borked your deathball.ini or your Deathball installation somehow. Delete your ~/.ut2004/deathball/system/deathball.ini and then (try) to start Deathball (it will recreate deathball.ini) and then do those changes. If it still doesn't work, try to reinstall Deathball. For me it works 100% well with those changes.
[EDIT] If it still doesn't work after reinstalling, then you obviously need to have your ut2k4 pached to 3270 (it's still beta patch though). Direct link to ut2004 linux patch 3270 beta: http://0day.icculus.org/ut2004/ut2004-l ... TA.tar.bz2
[EDIT2] I just noticed that a 3270 (non-beta) patch has been released for linux yesterday. I just tried it briefly and you still need to edit deathball.ini like I told in my previous post. No idea how well it works, but I haven't had problems with 3270beta so I'd guess it should work fine. Get it from http://0day.icculus.org/ut2004/ut2004-l ... -1.tar.bz2
Last edited by teidon on 01-09-2004 14:48, edited 1 time in total.
FireCell, was it your deathball.ini or did you have to install 3270 patch? Just asking so that other linux users (as well as me) would know if it requires 3270 patch or not.