Notpron Forums

I just noticed that I had forgotten a dot from ~/.ut2004/... in my instructions. :rolleyes: So XST1 you have to edit ~/.ut2004/deathball/System/Deathball.ini file (.ut2004 is a hidden directory under your home directory) and add line "Paths=../Maps/*.ut2" under [Core.System] section. Updated the ...

defaultlinux.ini is (still) borked. For Linux users: 1. Remove default.ini from ut2004/deathball/system directory and rename defaultlinux.ini to default.ini. 2. Try to start Deathball (it will fail). 3. Open ~/.ut2004/deathball/system/Deathball.ini and find [Core.System] section and add line "Paths ...

I just played the first league (league 3) in SP with hard difficulty... 1. defaultlinux.ini is borked - it removes the Paths=../Maps/*.ut2 line from the generated deathball.ini. Without it UT2k4 can't find the NoIntro.ut2 file -> Deathball won't start. 2. DB-Hole (and DB-Chill if it isn't already ...

I just did some testing under linux. First I moved away deathball directory from ut2004's directory as well as moved away ~/.ut2004/deathball (for you windows users: In linux different programs stores their config files to the user's home directory who runs the program, in other words every user ...

I didn't need to change anything else from in the deathball. ini than just do the three changes I've said. FireCell, try to rename your deathball folder to Deathball (or wise versa) and try to launch DB with -mod=deathball or -mod=Deathball (what ever is the way you do normally). I don't remember ...

Clean DB 2.1d install won't work under linux :rolleyes: For those linux users having trouble getting DB to work under linux see <A HREF="http://forums.gameservers.net/showthread.php?s=&threadid=16112">this thread</A> (scroll down to my post which subject is "It's working!!!"). Any change DB 2.1e ...

Icculus is the one who maintains ut2k4's linux version (32bit and 64bit) as well as 64bit windows version when it comes out (or so I heard), so when icculus releases a linux patch for ut2k4, it's as official as it gets. But then as you can play DB with 3236, there's no need for you to patch - after ...

FireCell, yes there is, read my 3rd reply's edit2.

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.

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 ...

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 ...

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 ...

UT2004-bin segfaults if I try to run it with -mod=deathball parameter like this: Signal: SIGSEGV [segmentation fault] Aborting. Crash information will be saved to your logfile. Deathball.log is like this: Log: Log file open, Mon Aug 30 18:26:56 2004 Init: Name subsystem initialized Init: Version ...