I keep getting crashes...

Discuss the BW-Invasion server here.
Post Reply
Faralex
Member
Posts: 1
Joined: Fri 17 Jan , 2014 9:44 pm
Contact:

I keep getting crashes...

Post by Faralex » Fri 17 Jan , 2014 10:24 pm

Hello,

I am playing on the invasion ballistic server and i keep getting crashes the last few days (several times per game)

I tried deleting the cache directory and reinstalled the game. But both methods didnt fix the problem.

I get this message:

UT2004 Build UT2004_Build_[2005-11-23_16.22]

OS: Windows XP 5.1 (Build: 2600)
CPU: GenuineIntel PentiumPro-class processor @ 3093 MHz with 1023MB RAM
Video: AMD Radeon HD 6800 Series (1230)

BallisticPlayer DM-Bygone.BallisticPlayer (Function BallisticProV55.BallisticPlayer.ListItems:01CE) Runaway loop detected (over 10000000 iterations)

Histoire: FFrame::Serialize <- UObject::ProcessEvent <- (BallisticPlayer DM-Bygone.BallisticPlayer, Function BallisticProV55.BallisticPlayer.PrevWeapon) <- UObject::ScriptConsoleExec <- (BallisticPlayer DM-Bygone.BallisticPlayer) <- UPlayer::Exec <- UViewport::Exec <- UWindowsViewport::Exec <- UInput::ExecInputCommands <- UInput::Process <- UEngine::InputEvent <- UWindowsViewport::CauseInputEvent <- UWindowsViewport::UpdateInput <- UViewport::ReadInput <- APlayerController::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=3) <- TickLevel <- UGameEngine::Tick <- Level DM-Bygone <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 10910191 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

Also in the UT2004.log, I see this:

Warning: XInvHUD DM-Bygone.XInvHUD (Function InvasionX_LDG.XInvHUD.ShowTeamScorePassC:0127) Accessed None 'ThePawn'
Warning: XInvHUD DM-Bygone.XInvHUD (Function InvasionX_LDG.XInvHUD.ShowTeamScorePassC:0127) Accessed None 'ThePawn'
Warning: XInvHUD DM-Bygone.XInvHUD (Function InvasionX_LDG.XInvHUD.ShowTeamScorePassC:0127) Accessed None 'ThePawn'
Critical: BallisticPlayer DM-Bygone.BallisticPlayer (Function BallisticProV55.BallisticPlayer.ListItems:01CE) Runaway loop detected (over 10000000 iterations)
Critical: Windows GetLastError: Une opération non bloquante sur un socket na pas pu être achevée immédiatement. (10035)
Exit: Executing UObject::StaticShutdownAfterError
Exit: Executing UWindowsClient::ShutdownAfterError
Log: Waiting for file streaming thread to finish...
Exit: OpenAL Audio subsystem shut down.
Critical: FFrame::Serialize
Critical: UObject::ProcessEvent
Critical: (BallisticPlayer DM-Bygone.BallisticPlayer, Function BallisticProV55.BallisticPlayer.PrevWeapon)
Critical: UObject::ScriptConsoleExec
Critical: (BallisticPlayer DM-Bygone.BallisticPlayer)
Critical: UPlayer::Exec
Critical: UViewport::Exec
Critical: UWindowsViewport::Exec
Critical: UInput::ExecInputCommands
Critical: UInput::Process
Critical: UEngine::InputEvent
Critical: UWindowsViewport::CauseInputEvent
Critical: UWindowsViewport::UpdateInput
Critical: UViewport::ReadInput
Critical: APlayerController::Tick
Critical: TickAllActors
Critical: ULevel::Tick
Critical: (NetMode=3)
Critical: TickLevel
Critical: UGameEngine::Tick
Critical: Level DM-Bygone
Critical: UpdateWorld
Critical: MainLoop
Critical: FMallocWindows::Free
Critical: FMallocWindows::Realloc
Critical: 10910191 0 FArray
Critical: FArray::Realloc
Critical: 0*2
Critical: FMallocWindows::Free
Exit: Exiting.

It crashes randomly but only when I try to change weapons with mousewheel with previous/next weapon. When I start i can switch weapon without problem but it crashes after a while without any reason.

help is welcome. It has become unplayable :-( (several crashes in a game sometimes)

User avatar
Butcher
V.I.P. Member
Posts: 893
Joined: Sat 15 Sep , 2012 1:31 pm
Location: Germany
Contact:

Re: I keep getting crashes...

Post by Butcher » Mon 20 Jan , 2014 11:32 am

I had some similar problem, but in my case none of the keybinds were working. I noticed that there was a conflict between the UT initial configuration (key binds) and the invasion keybinds.
what I did to solve it was:
1) Erase cache
2) Delete User.ini (have a backup)
3) Make new keybind configuration making sure none of the original keybinds from the UT matches the invasion Keybinds.
4) My keybinds for invasion were set and are different than for the Freon server.

it worked like that... maybe for you too.
"An BW match is a test of your skill against your opponents' luck." :)

Post Reply

Who is online

Users browsing this forum: No registered users and 26 guests