CUT2:PR3.0 Bug Report Thread
Can anyone that gets a GPF or other type of hard crash on start up please send me both their ut2004.log, ut2004.ini, chaosut.log and chaosut2.ini so we can not get to the bottem of this? Enough of you have this problem so its something, just you folks are in the minority and we can not reproduce this issue at all. Thanks and sorry:
jb@planetunreal.com
jb@planetunreal.com
Jb
Thanks a lot for your help!jeditobe1 wrote:do NOT do this. You should NEVER rename or alter a game file.TKATK wrote:rename ut2004intro.u2 or sumthin to NoIntro.U2
If the ChaosNoIntro.ut2 file is giving you problems, go into ChaosUT2.ini and change the LocalMap= to NvidiaLogo.ut2 or NoIntro.ut2. It should be right near the top of the file.
Now I can start the ChaosUT link and the game starts as usual in UT2004.
Do you think I should reinstall it?
I was making a chaos map and I spawned a turrent, and decided to be mean to it and shot a napalm nade at it and got this error after it died:
UT2004 Build UT2004_Patch_[2004-05-10_17.18]
OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 2134 MHz with 511MB RAM
Video: RADEON 9800 PRO (6436)
General protection fault!
History: UShadowBitmapMaterial::Get <- FD3DRenderInterface::SetProjectorMaterial <- FD3DRenderInterface::SetMaterial <- RenderStaticMesh <- FDynamicActor::Render <- RenderLevel <- DM-ChaoticValley.myLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level Chaotic Valley <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 676F4C57 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free
Can someone tell me what this means.
UT2004 Build UT2004_Patch_[2004-05-10_17.18]
OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 2134 MHz with 511MB RAM
Video: RADEON 9800 PRO (6436)
General protection fault!
History: UShadowBitmapMaterial::Get <- FD3DRenderInterface::SetProjectorMaterial <- FD3DRenderInterface::SetMaterial <- RenderStaticMesh <- FDynamicActor::Render <- RenderLevel <- DM-ChaoticValley.myLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level Chaotic Valley <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 676F4C57 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free
Can someone tell me what this means.

Last edited by Brandon on Wed Jun 09, 2004 8:42 pm, edited 1 time in total.

This bug happened to make the game crash.
Description of what happened:
I was in the map, Oilrig and had CUT running. I had the Claw2 and was laying mines on the 4 prongs surrounding the Gravity Vortex. I picked up the vortex and launched it so that it was on the other side of the map. I then reset to Claw2 and launched a fire mine onto the nearest corner of the walkway. I also had a Large Turret sitting at the entrance to the pathway to the Vortex. After launching the mine, and hearing it beep, turn on, the game crashed. Here's the message.
UT2004 Build UT2004_Patch_[2004-05-10_17.18]
OS: Windows 2000 5.0 (Build: 2195)
CPU: GenuineIntel PentiumPro-class processor @ 1000 MHz with 383MB RAM
Video: NVIDIA GeForce4 MX 440 (5672)
General protection fault!
History: APawn::processHitWall <- APawn::physFalling <- APawn::performPhysics <- AActor::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=0) <- TickLevel <- UGameEngine::Tick <- Level CE Oilrig <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 676F4C57 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free
Description of what happened:
I was in the map, Oilrig and had CUT running. I had the Claw2 and was laying mines on the 4 prongs surrounding the Gravity Vortex. I picked up the vortex and launched it so that it was on the other side of the map. I then reset to Claw2 and launched a fire mine onto the nearest corner of the walkway. I also had a Large Turret sitting at the entrance to the pathway to the Vortex. After launching the mine, and hearing it beep, turn on, the game crashed. Here's the message.
UT2004 Build UT2004_Patch_[2004-05-10_17.18]
OS: Windows 2000 5.0 (Build: 2195)
CPU: GenuineIntel PentiumPro-class processor @ 1000 MHz with 383MB RAM
Video: NVIDIA GeForce4 MX 440 (5672)
General protection fault!
History: APawn::processHitWall <- APawn::physFalling <- APawn::performPhysics <- AActor::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=0) <- TickLevel <- UGameEngine::Tick <- Level CE Oilrig <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 676F4C57 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free
Weard bug
Advanced Weapon Option Button not availible online (it does work offline)
Here is a link to zoefff's (Darkmatter) post in the official atari forum.
Here is zoefff's post that he coudn't register:
- n00blike
Here is a link to zoefff's (Darkmatter) post in the official atari forum.
Here is zoefff's post that he coudn't register:
Originally posted by zoefff
yes, i know that this is a very unknown issue but when it got released and found the bug i thought someone els would post the bug and get an awnser but it apears i am the only one with this bug
and no, i can't register there because it won't give me a confirmation email to activate my acount
but thnx anyway for youre time
-zoefff
- n00blike
online name: n00blike
teh funnay to pwn
teh funnay to pwn
Originally posted by nublar
Plz ban epic
Flamethrower bug
There is no texture on the flamethrower under the pink highlighting of double damage...
-
- Posts: 5
- Joined: Sun Jun 06, 2004 11:08 pm
Maybe Mac Only Bug but not sure...
Whether I play online, host a game, or just play a botmatch. UTChaos with crash out, upon loading a new Map, after a round has been played.
For example, I could join or host, one round and play fine. But as soon as that match is over and the next map is loaded, when I get the "Press Fire to Begin" Message, that is when UT will crash out.
If I host a game or play a botmatch, it will happen after the first game. If I play online, as a client, to another machine, I can play about 2-3 matches before it will happen.
Bug reported...
S
For example, I could join or host, one round and play fine. But as soon as that match is over and the next map is loaded, when I get the "Press Fire to Begin" Message, that is when UT will crash out.
If I host a game or play a botmatch, it will happen after the first game. If I play online, as a client, to another machine, I can play about 2-3 matches before it will happen.
Bug reported...
S