UT2003 problems

petecool · Jan 8, 2003, 06:06 AM

I have problems running Unreal Tournament 2003 with this driver set (the 2.3.55 omega's)... I get a black screen, then an error dialog pops up with this text:

OS: Windows 2000 5.0 (Build: 2195)
CPU: AuthenticAMD PentiumPro-class processor @ 1472 MHz with 511MB RAM
Video: No Video

General protection fault!

History: UWindowsViewport::ResizeViewport <- UOpenGLRenderDevice::SetRes <- UWindowsViewport::TryRenderDevice <- UWindowsViewport::OpenWindow <- UGameEngine::Init <- InitEngine

This happens both with OpenGL and D3D rendering, I edited the UT2003.ini to try out GL rendering...

Any ideas why this might happen?

Thanks

The_Neon_Cowboy · Jan 8, 2003, 06:49 AM

I got that same error when I tryed to apply a no cd patch... you have to uninstall and reinstall and repatch

petecool · Jan 8, 2003, 07:00 AM

The problem is, I just did that! - reinstall everything from scratch

Also, with th eunpatched exe, the mouse pointer becomes a spinning CD, the cd spins in its drive, and then... nothing at all! It doesn't even try to initialise the 3d!

Very weird

ToshiroOC · Jan 8, 2003, 08:35 AM

Did you uninstall before reinstalling?

UberLord · Jan 8, 2003, 12:03 PM

Could you retest using the official Cat 3's and see if it's an Omega driver problem?

ToshiroOC · Jan 8, 2003, 12:09 PM

Hmmm also, did you update UT2k3? And did the aforementioned no-cd patch match with the patch number? Did you clean the registry after uninstalling? So many questions, so few answers

sanosizo · Jan 8, 2003, 02:51 PM

i have the same problem before. i just reinstall UT back, install the 2136 patch then apply the nocd fix. should work for everyone i hope

petecool · Jan 8, 2003, 06:02 PM

I don't see anything related to UT in the registry after uninstalling (didn't look before uninstalling though)

Can I apply the no-cd patch before I ever started the game fully? Or do I need a normal startup before putting it in?

ToshiroOC · Jan 8, 2003, 11:34 PM

I would suggest starting it up and then doing the configuration for the video and all, then quitting then applying the no-cd patch - see if that helps.

MSX · Jan 8, 2003, 11:39 PM

I'm not sure why it happens... but it happens to me when I'm playing multiplayer and a lot of stuff is going on.

However this is a different problem.. same error message. Which probibly means your machine is trying to send too much stuff to video or the default resolutions/ refresh rate is wrong... So try playing around with that. Do you use a refresh rate locker?

MSX

damm · Jan 9, 2003, 08:57 PM

I'm shocked, and dismayed.

At any rate, i've been using the Omega 2.3.55 drivers since they came out with UT2K3 with D3D mode, i wish OpenGL mode worked... but hard crash

At any rate, D3D is fine, i get a few artifacts here and there, a few missing textures now and then. But i'm sure it's due to DX9 or ATI, god knows.

You would think, that ATI would be producing more quality, constantly.

I have a problem with one driver set working great, and another fscking up.

I would go elsewhere, but truthfully, that would drop me out of support on FreeBSD for DRI, unless i went NVidia which i would never do.

So my little lesson if anyone cares is simple, If you find a driverset that works great, stick with it. Stop touching it, stop modifying it, don't touch it unless you have to!

I'd run the Non Catalyst drivers if i could with UT2K3, because the last release of Non Catalyst's from Omega was supreme, great release, mipmap was working right, opengl was fine, etc etc.

Now for some reason, full screen opengl with Catalyst 3.0 crash's, omega or non omega.

GREAT JOB ATI!

BTW,

ATI Radeon VIVO (7200)
AMD 1.4Ghz TBird, 512Meg of SDRAM/CAS=2
Tyan Trinity S2390B (KT133A) with George's VIA PCI Latency Patch's .14
and alot of other stuff that's really irrelevent.

petecool · Jan 10, 2003, 05:53 AM

ToshiroOC, the game doesn't even start...

After applying the patch, I try to start the game. The loading screen appears, the resolution changes to 640x480, and an error window pops up with the previously mentioned text.

petecool · Jan 10, 2003, 06:13 AM

Even reverting to Omega 2.2.18 didn't fix the problem...

Weird, very &#*(%#*% weird

The_Neon_Cowboy · Jan 10, 2003, 10:58 AM

try the 3.0 drivers!!!

Jan 8, 2003, 06:06 AM	#1
petecool DriverHeaven Newbie Join Date: Nov 2002 Location: Laval, Canada Posts: 10 Rep Power: 0	UT2003 problems I have problems running Unreal Tournament 2003 with this driver set (the 2.3.55 omega's)... I get a black screen, then an error dialog pops up with this text: OS: Windows 2000 5.0 (Build: 2195) CPU: AuthenticAMD PentiumPro-class processor @ 1472 MHz with 511MB RAM Video: No Video General protection fault! History: UWindowsViewport::ResizeViewport <- UOpenGLRenderDevice::SetRes <- UWindowsViewport::TryRenderDevice <- UWindowsViewport::OpenWindow <- UGameEngine::Init <- InitEngine This happens both with OpenGL and D3D rendering, I edited the UT2003.ini to try out GL rendering... Any ideas why this might happen? Thanks

Jan 8, 2003, 06:49 AM	#2
The_Neon_Cowboy HardwareHeaven Extreme Member Join Date: Dec 2002 Location: U.S.A. Posts: 16,009 Rep Power: 92 System Specs	I got that same error when I tryed to apply a no cd patch... you have to uninstall and reinstall and repatch __________________

Jan 8, 2003, 08:35 AM	#4
ToshiroOC Unbiased. Join Date: Jun 2002 Posts: 4,812 Rep Power: 0	Did you uninstall before reinstalling? __________________ [img][/img] [color=White]Peace be with you, Joe.[/color] Driverheaven Staff Member (Supermoderator)

Jan 8, 2003, 12:03 PM	#5
UberLord A Legend in Underwear Join Date: May 2002 Location: Unknown Posts: 5,255 Rep Power: 0	Could you retest using the official Cat 3's and see if it's an Omega driver problem? __________________ Gentoo Linux - Developer (baselayout) Read my blog "I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours." Stephen Roberts

Jan 8, 2003, 12:09 PM	#6
ToshiroOC Unbiased. Join Date: Jun 2002 Posts: 4,812 Rep Power: 0	Hmmm also, did you update UT2k3? And did the aforementioned no-cd patch match with the patch number? Did you clean the registry after uninstalling? So many questions, so few answers __________________ [img][/img] [color=White]Peace be with you, Joe.[/color] Driverheaven Staff Member (Supermoderator)

Jan 8, 2003, 07:00 AM	Thread Starter #3
petecool DriverHeaven Newbie Join Date: Nov 2002 Location: Laval, Canada Posts: 10 Rep Power: 0	The problem is, I just did that! - reinstall everything from scratch Also, with th eunpatched exe, the mouse pointer becomes a spinning CD, the cd spins in its drive, and then... nothing at all! It doesn't even try to initialise the 3d! Very weird

Jan 8, 2003, 02:51 PM	#7
sanosizo DriverHeaven Junior Member Join Date: Jun 2002 Location: Malaysia Posts: 59 Rep Power: 0	i have the same problem before. i just reinstall UT back, install the 2136 patch then apply the nocd fix. should work for everyone i hope __________________ Athlon XP 1700+ Asus A7S333 512MB PC2700 Kingston DDR Yuan 9800SE softmodded (Omega Cat4.8) Windows XP Pro SP1 Logitech Wingman RumblePad Logitech Wingman Formula Force GP

Jan 8, 2003, 06:02 PM	Thread Starter #8
petecool DriverHeaven Newbie Join Date: Nov 2002 Location: Laval, Canada Posts: 10 Rep Power: 0	I don't see anything related to UT in the registry after uninstalling (didn't look before uninstalling though) Can I apply the no-cd patch before I ever started the game fully? Or do I need a normal startup before putting it in?

Jan 8, 2003, 11:34 PM	#9
ToshiroOC Unbiased. Join Date: Jun 2002 Posts: 4,812 Rep Power: 0	I would suggest starting it up and then doing the configuration for the video and all, then quitting then applying the no-cd patch - see if that helps. __________________ [img][/img] [color=White]Peace be with you, Joe.[/color] Driverheaven Staff Member (Supermoderator)

Jan 8, 2003, 11:39 PM	#10
MSX Burning the frozen... Join Date: Sep 2002 Posts: 1,201 Rep Power: 0	I'm not sure why it happens... but it happens to me when I'm playing multiplayer and a lot of stuff is going on. However this is a different problem.. same error message. Which probibly means your machine is trying to send too much stuff to video or the default resolutions/ refresh rate is wrong... So try playing around with that. Do you use a refresh rate locker? MSX

Jan 9, 2003, 08:57 PM	#11
damm DriverHeaven Junior Member Join Date: Jul 2002 Posts: 41 Rep Power: 0	I'm shocked, and dismayed. At any rate, i've been using the Omega 2.3.55 drivers since they came out with UT2K3 with D3D mode, i wish OpenGL mode worked... but hard crash At any rate, D3D is fine, i get a few artifacts here and there, a few missing textures now and then. But i'm sure it's due to DX9 or ATI, god knows. You would think, that ATI would be producing more quality, constantly. I have a problem with one driver set working great, and another fscking up. I would go elsewhere, but truthfully, that would drop me out of support on FreeBSD for DRI, unless i went NVidia which i would never do. So my little lesson if anyone cares is simple, If you find a driverset that works great, stick with it. Stop touching it, stop modifying it, don't touch it unless you have to! I'd run the Non Catalyst drivers if i could with UT2K3, because the last release of Non Catalyst's from Omega was supreme, great release, mipmap was working right, opengl was fine, etc etc. Now for some reason, full screen opengl with Catalyst 3.0 crash's, omega or non omega. GREAT JOB ATI! BTW, ATI Radeon VIVO (7200) AMD 1.4Ghz TBird, 512Meg of SDRAM/CAS=2 Tyan Trinity S2390B (KT133A) with George's VIA PCI Latency Patch's .14 and alot of other stuff that's really irrelevent.

Jan 10, 2003, 05:53 AM	Thread Starter #12
petecool DriverHeaven Newbie Join Date: Nov 2002 Location: Laval, Canada Posts: 10 Rep Power: 0	ToshiroOC, the game doesn't even start... After applying the patch, I try to start the game. The loading screen appears, the resolution changes to 640x480, and an error window pops up with the previously mentioned text.

Jan 10, 2003, 06:13 AM	Thread Starter #13
petecool DriverHeaven Newbie Join Date: Nov 2002 Location: Laval, Canada Posts: 10 Rep Power: 0	Even reverting to Omega 2.2.18 didn't fix the problem... Weird, very &#(%#% weird

Jan 10, 2003, 10:58 AM	#14
The_Neon_Cowboy HardwareHeaven Extreme Member Join Date: Dec 2002 Location: U.S.A. Posts: 16,009 Rep Power: 92 System Specs	try the 3.0 drivers!!! __________________