OpenGl Quake 3 engine Fix for ATI Cards..SoFII ...Jedi Knight Outcast ..Etc,

[Trimble Bracegirdle]

There is a known problem with Quake 3 engine games
which use the OpenGl method in that ATI Catalyst drivers
will not work particular since Cat 10.5 .

The most suggested fix found on the Net is to replace the file
atioglxx.dll with a version from Cat 10.4 or earlier.
This atioglxx.dll is in XP & VISTA in ' Windows\System32 '
In Windows 7 its in 'Windows\SysWOW64'
Its the same for 32 & 64 bit versions.
Or to install a pre 10.5 version of the Cat Drivers....(hardly satisfactory)

I've been using this method OK until recently when I found the
latest Catalyst 10.12 still wouldn't work in XP with an older
atioglxx.dll & not well in Win 7.

Much further Net searching yielded the following fix:
The problem occurs at the start up of these games which can not cope
with modern complexities in the ATI OpenGl driver.
By going into the games Folder & making a copy of the main EXE file
then renaming that to QUAKE3.EXE that should now run OK.
The quake3.exe name fools the drivers into using a configuration the engine
can work with.
The using old 'atioglxx.dll' tactic is now not needed. Indeed the lastest
version
will give better results.

Games affected:
GLQuake
Quake II
Heretic II
Sin 1
Kingpin: Life of Crime
Soldier of Fortune 1
Soldier of Fortune 2
Anachronox
Call of Duty 1 & UO
Return to Castle Wolfenstein Single Player
Star Wars Jedi Knight II: Jedi Outcast
Star Wars Jedi Knight: Jedi Academy
Medal of Honor Allied Assault & the two expansions
KOTOR (sometimes)
Star Trek Voyager Elite Force
Star Trek Voyager Elite Force 2
Heavy Metal FAKK2
Daikatana
(\__/)
(='.'=)
(")_(") mouse (sooo ! Old)

[John Lewis]

Huh. What "modern complexities" ?

How inconvenient, when a comprehensive OpenGL driver fix on ATi's
part would probably have been a 15 minute exercise by one of their
driver team.. ATi's GL support seems to be always late and
half-baked...

Nvidia latest driver 260.99 with a GTX460 on XP32 SP3 has no problem
at all with the DOS/DOSBox/ GL games in my collection that I have had
an opportunity to run with this newer nV hardware and driver (Star
Wars JK 1/II/Outcast, Kingpin, SOF1, Sin Episodes:Emergence, etc,
etc..).

I have stayed with nV hardware due to the generally excellent
Dx/OpenGL HW and SW backward compatibility in their graphics drivers.
I have a large collection of "classic" PC games that I like to revisit
from time to time and play on my current gaming machine. Russian
Roulette with graphics driver changes, or having to find manual hacks
just to play an older game are not my kind of fun.

John Lewis

[Shawk]

Le 05/01/2011 09:14, John Lewis a �crit :

> On Wed, 5 Jan 2011 01:20:06 -0000, "Trimble Bracegirdle"
> <no-...@never.spam> wrote:
>
>> There is a known problem with Quake 3 engine games
>> which use the OpenGl method in that ATI Catalyst drivers
>> will not work particular since Cat 10.5 .
>>
>> The most suggested fix found on the Net is to replace the file
>> atioglxx.dll with a version from Cat 10.4 or earlier.

>> This atioglxx.dll is in XP& VISTA in ' Windows\System32 '

>> In Windows 7 its in 'Windows\SysWOW64'

>> Its the same for 32& 64 bit versions.

>> Or to install a pre 10.5 version of the Cat Drivers....(hardly satisfactory)
>>
>> I've been using this method OK until recently when I found the
>> latest Catalyst 10.12 still wouldn't work in XP with an older

>> atioglxx.dll& not well in Win 7.

>>
>> Much further Net searching yielded the following fix:
>> The problem occurs at the start up of these games which can not cope
>> with modern complexities in the ATI OpenGl driver.

>> By going into the games Folder& making a copy of the main EXE file

>> then renaming that to QUAKE3.EXE that should now run OK.
>> The quake3.exe name fools the drivers into using a configuration the engine
>> can work with.
>> The using old 'atioglxx.dll' tactic is now not needed. Indeed the lastest
>> version
>> will give better results.
>>
>> Games affected:
>> GLQuake
>> Quake II
>> Heretic II
>> Sin 1
>> Kingpin: Life of Crime
>> Soldier of Fortune 1
>> Soldier of Fortune 2
>> Anachronox

>> Call of Duty 1& UO

>> Return to Castle Wolfenstein Single Player
>> Star Wars Jedi Knight II: Jedi Outcast
>> Star Wars Jedi Knight: Jedi Academy

>> Medal of Honor Allied Assault& the two expansions

>> KOTOR (sometimes)
>> Star Trek Voyager Elite Force
>> Star Trek Voyager Elite Force 2
>> Heavy Metal FAKK2
>> Daikatana
>> (\__/)
>> (='.'=)
>> (")_(") mouse (sooo ! Old)
>>
>>
>
>
>> The problem occurs at the start up of these games which can not cope
>> with modern complexities in the ATI OpenGl driver.
>
> Huh. What "modern complexities" ?
>
> How inconvenient, when a comprehensive OpenGL driver fix on ATi's

> part would probably.....

Translation ... I hate ATI

> Nvidia latest driver 260.99 with a GTX460 on XP32 SP3 has no problem

> at all with the.....

Translation... I love NVidia

Its nice when you've been away a long time to come back and find
nothings changed.... thanks John.

[Ross Ridge]

Trimble Bracegirdle <no-...@never.spam> wrote:
>Star Wars Jedi Knight II: Jedi Outcast

I don't know about any of the other games, but the problem with Jedi
Outcast is that it overruns a buffer when it tries to print out a list
of OpenGL extensions that video card supports. If you have a hex editor
you can fix the problem by changing the string "GL_EXTENSIONS: %s" to
"GL_EXTENSIONS: %p" in the executable.

Ross Ridge

--
l/ // Ross Ridge -- The Great HTMU
[oo][oo] rri...@csclub.uwaterloo.ca
-()-/()/ http://www.csclub.uwaterloo.ca/~rridge/
db //

[Andrew Rybenkov]

On Wed, 05 Jan 2011 04:20:06 +0300, Trimble Bracegirdle <no-...@never.spam> wrote:

> There is a known problem with Quake 3 engine games
> which use the OpenGl method in that ATI Catalyst drivers
> will not work particular since Cat 10.5

Is there any reason to update my 10.3 drivers (HD5770 here)?

--
Andrew Rybenkov

[Trimble Bracegirdle]

In the last few months ATI have been making a point about
how they are keeping up with the latest OPENGL features.
Also in Nov. I noticed a ATI Forum person declaring this Quake 3 Engine
games Bug as fixed.

I think they have fixed it for the actual Quake3 game
...so the renaming of other games Main.Exe's trick works...BUT they haven't
included fixes explicitly for the other games.

I find the rename to Quake3.exe tactic works well with in XP
but in Win 7 all the games start but the brightness levels in some are very
dark &
refuse to be changed.
Thanks to Ross Ridge here for that jk2 Hack ..I will try it.
@@@Mouse@@@

[John Lewis]

On Wed, 05 Jan 2011 21:40:43 +0100, Shawk <sh...@gmx.co.uk.3guesses>
wrote:

Got your knickers in a twist, I see.

I have genuine PRACTICAL reasons for staying with nVidia. How about
your own PRACTICAL reasons for ATi ?

John Lewis

[Shawk]

On 07/01/2011 03:42, John Lewis wrote:

>
>
> Got your knickers in a twist, I see.

Nope... just mildly amused that I can go away from the newsgroup for a
year or so and come back to see you saying exactly the same things as
you have said for several years previously. In an uncertain world
there's a little comfort to be had from knowing some things never change
(no matter what technological advances are made)...

> I have genuine PRACTICAL reasons for staying with nVidia. How about
> your own PRACTICAL reasons for ATi ?

Also nice to see some folk are still carrying on with that old
traditional craft of building straw men.

You may recall on 27th December in response to my question about gfx
cards you posted "I would highly suggest waiting to see the
specs/reviews on the upcoming nVidia GTX560, expected to release late
January, early -February" and my reply was "The GTX570 is calling to me
currently and I fancy a NVidia card this time - they seem to be doing a
lot of things right at last"

But thanks for playing...

[Shawk]

On 08/01/2011 22:57, Zaghadka wrote:

> On Fri, 07 Jan 2011 20:50:27 +0000, in comp.sys.ibm.pc.games.rpg, Shawk wrote:
>
>>> I have genuine PRACTICAL reasons for staying with nVidia. How about
>>> your own PRACTICAL reasons for ATi ?
>>
>>
>> Also nice to see some folk are still carrying on with that old
>> traditional craft of building straw men.
>>
>> You may recall on 27th December in response to my question about gfx
>> cards you posted "I would highly suggest waiting to see the
>> specs/reviews on the upcoming nVidia GTX560, expected to release late
>> January, early -February" and my reply was "The GTX570 is calling to me
>> currently and I fancy a NVidia card this time - they seem to be doing a
>> lot of things right at last"
>>
>> But thanks for playing...
>

> I'm simply in awe at your correct use of the term "straw man argument."
>
> Well done, sir. ;^)

Seems to be a dying art but thankyou. Nice to see you are still around
Zag.. hope things are good with you

[Ayatollah of rock 'n' roller]

On the plus side, none of us could play Daikatana for a while.

[Shawk]

Le 09/01/2011 18:42, Ayatollah of rock 'n' roller a écrit :
> On the plus side, none of us could play Daikatana for a while.
>
>

Nice... :)

[noman]

On 1/5/2011 12:14 AM, John Lewis wrote:
> On Wed, 5 Jan 2011 01:20:06 -0000, "Trimble Bracegirdle"
> <no-...@never.spam> wrote:
>
>
>> The problem occurs at the start up of these games which can not cope
>> with modern complexities in the ATI OpenGl driver.
>
> Huh. What "modern complexities" ?
>
> How inconvenient, when a comprehensive OpenGL driver fix on ATi's
> part would probably have been a 15 minute exercise by one of their
> driver team.. ATi's GL support seems to be always late and
> half-baked...

Except that in this case, it is due to a bug in id software game
engines. One of the first things the software in Quake 3 (and also
Quake 2) engine do, is to ask for the openGl extensions supported
by the graphic driver. It also sets aside a memory buffer where
the reply from the driver (a list of extensions) are stored.
These early games didn't anticipate the number of extensions
that would be supported by subsequent versions of the API. So you
either get buffer overrun or seriously cut down list of extensions
(if the application writer at least checked for a max limit) which
either crash the game or affect regular functioning.

I downloaded Return to Castle Wolfenstein source code, to fix it
myself and the problem was obvious. Actually, the code even had
a comment about the buffer size not enough for future compatibility
and someone had arbitrarily increased the size about two or
three times as a quick workaround.

When nVidia released OpenGl 4.0 support, their customers ran into
exact same problem. Quake 3 games stopped working. To their credit
though, they fixed the issue quickly by detecting the application
and then only sending extensions supported by OpenGl 2.0. ATI's
10.10e (hotfix) drivers do the same and most Quake3/2 games work
(with Call of Duty as the only big exception)

Until ATI added fix for game engine's shortcoming, the workaround
was to copy atioglxx.dll (from Catalyst 10.4 and before) into the
game directory. I am not sure why that method stopped working
for Trimble. Currently I have three Quake 3 engine games installed.
Alice and Quake 3 (both original and Live) run fine without any
issues on 10.10e driver, and Call of Duty requires copying the dll file.

My 2¢
--
Noman

[trevi...@gmail.com]

I have the same problem with Alice. This is my favorite game. I have an AMD HD 4xxx series card and the newest driver from the AMD support site. What can I do to play with this great game again? :(

[HappyCowParty]

So I'm trying to run Quake 3 right now, and I keep getting an awful crash at the start. It only ran one time, but now it's been giving me this error:

http://i.imgur.com/n6qzGJx.jpg

I tried to install catalyst 10.4 but there is no atioglxx.dll. Only a atioglxx.dl_ I think. I guess that's a component file of the dll or something? I'm not sure how to actually get the dll and put it in the q3a folder. Help?

[Trimble Bracegirdle]

Which Windows are you using ?
I think you have some other problem.
That 2011 issue should be long gone & solved.
1st try right clicking the games exe & selecting compatibility - then set
to Windows XP.

(\__/)
(='.'=)

(")_(") mouse (sooo ! Totally Old)

[luddensj...@gmail.com]

Win 7 64 bit. It appears to be my catalyst drivers. I have to use this automatic detector thing from the catalyst website to download the drivers, but midway through the installation it crashes. Imam try older versions. : \

[Xocyll]

luddensj...@gmail.com looked up from reading the entrails of the
porn spammer to utter "The Augury is good, the signs say:

>Win 7 64 bit. It appears to be my catalyst drivers. I have to use this automatic detector thing from the catalyst website to download the drivers, but midway through the installation it crashes. Imam try older versions. : \

Wait, you're Muslim and you get your priest to try drivers for you?
Or you're a Muslim priest who talks about himself in the third person?

Xocyll

[CowParty]

Heh. Typo. I got it working by downloading and installing the 14.11 beta catalyst drivers. For whatever reason the .9 would always crash 60 something percent through install.

[Čeněk Šmiták]

Dne pondělí 10. ledna 2011 v 8:08:07 UTC+1 uživatel noman napsal:

Hello guys, year 2022 here, and im struggling with crazy fps drops. Particular in name Call of Duty 1.
I hope its not rude to ask you, how the hell did you fix it. Im not really a computer guy and i dont really understand your solution or what should i do :/ thank you very much.

[Spalls Hurgenson]

On Sun, 13 Feb 2022 03:37:41 -0800 (PST), ?en?k Šmiták
<csm...@gmail.com> wrote:

>Dne pond?lí 10. ledna 2011 v 8:08:07 UTC+1 uživatel noman napsal:

Hello year 2022, this is Dad.
(sorry, couldn't resist a bad Dad joke).

The explanation above was specific to an ATI video card, probably
running on Windows XP drivers. It required copying a file from a
patched version of the drivers into the game's directory. However,
unless you match that specific set of operating
system/hardware/drivers, their solution is unlikely to work for you.

At the very least, you should provide some basic info about your
computer (CPU, video card, operating system) and the software that
you're having problems with (for example, which version of "Call of
Duty 1"; the original CD-ROM version, or the version found on Steam?).
Without that basic information, it will be very difficult to
troubleshoot the issue.

And while it pains me to admit it, you're also better seeking help
elsewhere. This newsgroup is, if not dead, then only a breath or two
away from it. At the very least, you should check out the marginally
more active comp.sys.ibm.pc.games.action (which, anyway, is a better
fit for a game like "Call of Duty").

Good luck on your search.