Weird looping bug...

Phage · Post by **Phage** » Mon Jun 07, 2004 5:19 pm

What happened:
While playing on 62.93.201.62:30000 someone had the presence of mind to shoot me in the back with the mugg firing that ice stuff. Everything was normal as I turned around to shoot back, but as my screen blacked out and I say his name <ol>orgy or <lo>something-like-that my comp went into what I can only assume was an infintie loop of somekind. The sound kept playing some sort of dieing gasp and everything else froze. I had to reboot to get out of it. My comp usually runs the game fine although it is possible it was something due to harware I really doubt it. Things like msn and eMule were running in the background.

Can anyone tell me what may have happened?

Oh and this has probably come up somewhere else already but the mouse wheel cannot scroll through all the waepons it gets stuck on the shield gun/whatever sword you have and is really annoying.

TKATK · Post by **TKATK** » Mon Jun 07, 2004 9:23 pm

maybe hes using the loopingg name?the one which crashes the game by colour changing

What gametype?Muts?

Reptrix · Post by **Reptrix** » Mon Jun 07, 2004 9:38 pm

I also got a crash today this one:

UT2004 Build UT2004_Patch_[2004-05-10_17.18]

OS: Windows XP 5.1 (Build: 2600)
CPU: GenuineIntel Unknown processor @ 3070 MHz with 511MB RAM
Video: NVIDIA GeForce FX 5600 (5664)

General protection fault!

History: UCanvas::WrappedPrint <- (Welcome to the à@@UT2004 @@àF@à`u@àànàààsàà@eà¤@rà@@vÀ àe@@àr àà@:-)) <- UCanvas::execDrawText <- (ChaosxDeathMatchHUD DM-FST-SpaceNoxx.ChaosxDeathMatchHUD @ Function Engine.HUD.DisplayProgressMessages : 03E9) <- UObject::ProcessEvent <- (ChaosxDeathMatchHUD DM-FST-SpaceNoxx.ChaosxDeathMatchHUD, Function Engine.HUD.PostRender) <- FPlayerSceneNode::Render <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level SpaceNoxx <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 676F4C57 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

maybe this helps ya.

i think i just might have been outta memory or something.

Phage · Post by **Phage** » Mon Jun 07, 2004 10:52 pm

A strange color name glitch is possible as there were several people with colored names, but I can't remember if he was one of them. As to your other questions.
Gametype: DM
Map: DM-CBP2-Reconstruct
Muts: Chaos, and no others

Given this it's most likely that name, which diplayed like it should when your aimer crosses someone at close range, was the problem but I can't be sure as can't remember.

Thanks

pinki · Post by **pinki** » Thu Jun 10, 2004 1:07 pm

Hi,

unfortunately I also have experienced 2 freezes, both with the freezing weapon. Its definitely not the hardware, because my computer runs very stable, also in ut2k4. I'm looking for a fix for this problem...

greets

TKATK · Post by **TKATK** » Thu Jun 10, 2004 2:42 pm

put world details to low,they added a last second effect for the mug,so its better to be safe and low

i know if you make a name with 25 char name+script it will crash anyone who aims at you

pinki · Post by **pinki** » Thu Jun 10, 2004 3:22 pm

only one question: is it a problem of ut or the chaos mod? i've never experienced crashes with ut2k4 (without mod)...

TKATK · Post by **TKATK** » Thu Jun 10, 2004 3:29 pm

i have had the opposite

wait,freezing is temp or permanent,if its permanent then you should post youre log here

pinki · Post by **pinki** » Thu Jun 10, 2004 4:00 pm

It's a permanent. But in the Ut2004.log there is no more entry about that game. I've played some matches after the freezing...

TKATK · Post by **TKATK** » Thu Jun 10, 2004 6:47 pm

yeeah,try to reproduce the bug and psot the log here,if it doesnt reproduce then its okay

Post by **R.Flagg** » Thu Jun 10, 2004 7:25 pm

pinki wrote:only one question: is it a problem of ut or the chaos mod? i've never experienced crashes with ut2k4 (without mod)...

Fairly sure it's us. Sorry about that. We had something similar during testing, but we thought we had it squashed (ie: we didn't see it again after repeated attempts)

Anyway, can't say for sure until we figure out the cause, but we'll be looking.

Thanks for posting guys, sorry you had a problem.