Notpron Forums

My UT2003.log file grows out of control. This file is located in a filder located installdrive:\UT2003\system. How big is your file?
I have to delete mine after every game. the errors from the dbhud cause this file to range 2 megs to as high as 524 megs after a game. Game playability goes to hell when it gets over 400k.

In version 1.8 the logs always reset after restarting UT and were typically 300k or so and a couple times reached 2 meg size. This growth of this file never occurred every game and never OMG 524 megs....

In version 1.7 the logs never grew past 300k and never higher than 300k.

When I play UT, CTF, this file never is above 100k after several maps.

The errors are as shown:

Log: No ScoreBoardType specified in GameInfo

Warning: DB_SingleReplay DB-Old-SmallCube.DB_SingleReplay (Function Deathball.DB_SingleReplay.PostBeginPlay:0181) Accessed None

Warning: DB_RadarObjectPlayer DB-Old-SmallCube.DB_RadarObjectPlayer (Function Deathball.DB_RadarObject.PreBeginPlay:0055) Accessed None

Warning: DB_RadarObjectPlayer DB-Old-SmallCube.DB_RadarObjectPlayer (Function Deathball.DB_RadarObjectPlayer.RenderObjectVicinity:026C) Accessed None

Warning: DB_DeathBallHUD DB-Old-SmallCube.DB_DeathBallHUD (Function Deathball.DB_DeathBallHUD.DrawTime:0042) Accessed None

ScriptLog: !!!ERROR!!! DB_DeathballHUD.PostRender - GRI == NONE

Warning: DB_RadarObjectPlayer DB-Old-SmallCube.DB_RadarObjectPlayer (Function Deathball.DB_RadarObjectPlayer.RenderBeacon:0036) Accessed None

Warning: DB_KeeperMessage None (Function Deathball.DB_KeeperMessage.ClientReceive:0046) Accessed None

Explain why I have these and how to fix them. Someone has to have this problem, if not everyone. My install of 1.9 is new, as is UT2003 and DE Bonus and Epic Bonus and BrightSkins were fresh installs just before 1.9. The game plays like shit, and I can't volley (never could I guess), and euro servers ping like shit just like US servers and ever since 1.9.

Accessed None
is not much fun

That's all I know about your problem.

I made it read only after i deleted it.

Since 1.9, the log file size explode.

Only one thing to that:
gg davidm

DavidM says: Blame it on the French and Dutch!

yeah the dutch are to blame here o/

i just read my logfile and in it stands startup time 3mins 54 secs O.o when was that ?

mine is 24'...i mean 4 megs

0o
mae, who sthat fat person ont avatar

its one of the artists of fatboy slim ?

Ars3h wrote: mae, who sthat fat person ont avatar

He's off the front of "You've come a long way baby" by Fatboy Slim.

------------ ON TOPIC -------------

I've heard a problem like this before. It was in UT though and the guy had to delete his log file after every map. Perhaps something in one of your *.ini files has gone. Or maybe you do get shit loads of errors.

Re-install or ask some nice person to send you they're *.ini's and compare them.

0o

Share the .ini files.... O_o

The last two versions of Deathball are causing the log size explosion. Not so much in 1.8 as is the case with 1.9, but in 1.8 the errors didn't always happen repeatedly like in 1.9.

I can play CTF map after map and not have the same issues, my user.ini and utuser.ini files almost mimic my DB.ini files except for the key binds which say something slightly different. Most certainly has something to do with the deathball files. Unless someone would like to show instances in their ini files that look like fixes to my errors, I will have to continue with the fix, Volley Whore Croaker, posted earlier...marking the log file as read only.

Atleast I don't have to worry about any more half gig log files.

one accessed none spammed all over it

shouldn't be a big deal to fix I think

I know theres a DBUser.ini but isn't there a DB.ini too? You know, the one that lists all the locations of texture files and sound files and has things like:

[Engine.Gametype]
Blah blah = blah/??/something
Etc etc/#: fgdsagfd

That sorta stuff.

DavidM wrote: one accessed none spammed all over it

shouldn't be a big deal to fix I think

is that a first?

heh.. jk :p

anywho, i've been having this as well, after 2 maps earlier, my log file was 3.4 mb