FINALLY! Texture unwrapping on original Radeons SOLVED!

Ever since the catalyst drivers came out (in June I believe) and they offered tremendously better Tribes 2 FPS but with the horrible texture unwrapping problem, I've been doing everything I could think of to try to get unwrapping to go away on my Radeon 64 VIVO.

I tried older pre-catalyst drivers, but they gave me choppy FPS. I tried getting Direct3D working at more than 1/4 the FPS of OpenGL, but couldn't. I tried downloading every friggin registry tweak interface I came across and checking the dozens of API and processing settings on and off in every combination I could think of with the catalyst drivers -- and I still got the texture unwrapping.

Yes, it was possible to turn on interior texture fog to fix the unwrapping problem, but not with an intolerable overall performance hit that got really bad in some situations.

I tried editing some settings in my clientprefs.cs file (Gamedata/base/prefs) in the latest official T2 release, and no dice.

Well, I FINALLY had some luck opening up the clientprefs.cs file in the T2 beta build and disabling some OpenGL paramaters.

Being the layman that I am, I figured texture unwrapping might relate to something "external" -- so I changed the lines that said "disableEXT blah blah blah" from "0" (no) to "1" (yes). In the end, it fixed my texture unwrapping, and did not cause any FPS reduction.

Here are my OpenGL lines in my clientprefs.cs file -- if you are a Radeon user getting the texture unwrapping problem I suggest you change yours to look like this:

_______________________

$pref::openGL::allowCompression = "1";
$pref::openGL::allowTexGen = "1";
$pref::openGL::anisotropy = "0";
$pref::openGL::DisableARBMultitexture = "0";
$pref::openGL::DisableARBTextureCompression = "0";
$pref::openGL::DisableEXTCompiledVertexArray = "1";
$pref::openGL::DisableEXTFogCoord = "1";
$pref::openGL::DisableEXTPalettedTexture = "0";
$pref::openGL::DisableEXTTexEnvCombine = "0";
$pref::openGL::DisableSubImage = "0";
$pref::openGL::force16BitTexture = "1";
$pref::openGL::forcePalettedTexture = "0";
$pref::openGL::gammaCorrection = "0.921053";
$pref::openGL::interiorMipReduction = "1";
$pref::openGL::maxHardwareLights = "3";
$pref::openGL::mipReduction = "0";
$pref::openGL::noDrawArraysAlpha = "0";
$pref::openGL::noEnvColor = "0";
$pref::openGL::skyMipReduction = "0";

(Neo Edit: There's always a way around. )
_________________________

Now I can happily play T2 at decent FPS without being blinded by textures that have jumped off their polygons. Hope this helps anybody else having this problem.

(PREVIOUS EDITS DELETED DUE TO INVALIDATING DISCOVERIES)

EDIT 3 9/3

OK -- I've been editing this post too much. Whew! Anyway--

RIGHT NOW -- and I'm still experimenting -- I've found that setting all four lines with EXT in them to disabled is best.

I know that disabling the EXT Fog Coordinates fixes the texture unwrapping -- one of the other 3 lines affects performance issues inside specific situations with lots of light sources (like the Tombstone base). I am going to find out which line that is and edit this again.

EDIT 4 9/3

Ok, I've narrowed it down to two lines, that should look like this:

$pref::openGL::DisableEXTCompiledVertexArray = "1";
$pref::openGL::DisableEXTFogCoord = "1";

Setting both of these to disabled will:

1) Fix the texture unwrapping
2) Fix the performance issues associated with being in very particular lighting situations.

I THINK that these are the only two changes that would need to be inserted to address this issue in the patch.
Post edited by Sparkplug at 9/3/2002 6:15:16 PM

Bah. The forum is parsing some of the characters as emoticons. I tried putting it in "pre" tags and it still parsed them. Y'all get the point tho *sighs*

LOL WTF how'd that get there three times? *Edits and fixes it* -- these forums are whacko.
Post edited by Sparkplug at 9/2/2002 9:12:20 PM

Thanks, I know some people who really need this, heh.

And nice ownage by smilies

Seriously, if there is any time or future patching of the product, Marweas should make it so that these are the default settings for original Radeon cards. I realize that this is ATI's fault, but these are simple changes Sierra can make to nullify the ATI bug.

Being a texture unwrapping victim and not knowing what to do really makes you lose your mind.

This is a pre-emptive sex0r...
/me sex0r.
If I find that this doesn't work for me.. i'll have to take my sex0r back for giving me false hope. =P

Oh my fucking god.. i love you. I tested recalesence and beggar's run.. ran around for a bit looking different ways. NO UNWRAPPING. I'll need some help to give this guy the right amount of sex.

Edit: Thank you for stickying this, satoshi. =D
Post edited by Cyrus- at 9/2/2002 9:41:18 PM

OMFG>.....U SIR ARE MY ANGEL..>SAVIOR>>>...MYGOD....GIMMIE UR ADDRESS AND ILL SEND THE COKC WASHER OVER ASAP!!111 ALL ON MY EXPENSISES1111

I fixed your smiley invasion. The <x> html tag is powerful..
Post edited by NeoPhoenixTE at 9/3/2002 1:22:10 AM

---

RTFFAQ|NeoPhoenixTE
TeamWarfare|Site Support

have you tried leaving any of the 3 lines you changed as 0?

There are cfg files in the Gamedata dir for various video boards. For example, "DRI-Radeon.cs".

Talk to marweas about getting your tweaks included.

Side question, ....
Anyone compare the gf4-4600 to the radeon 9700 in t2?

Originally posted by: GreenBeret

have you tried leaving any of the 3 lines you changed as 0?

Yes, I narrowed it down to a single offending line and edited the post to reflect that.

EDIT:

I realized after changing only one line that when I only used that line it did not fix all performance issues. I am currently trying to identify what other line needs to be changed.
Post edited by Sparkplug at 9/3/2002 1:56:03 PM

Originally posted by: z0dd

There are cfg files in the Gamedata dir for various video boards. For example, "DRI-Radeon.cs".

Talk to marweas about getting your tweaks included.

The bizarre thing is that my DRI-Radeon.cs file already has the line

$pref::openGL::DisableEXTCompiledVertexArray = "1";

in it.

For some reason it "obeys" the line in ClientPrefs.cs over the line in DRI-Radeon.cs --- maybe ClientPrefs.cs gets loaded afterwards.
Post edited by Sparkplug at 9/3/2002 2:10:17 PM

thx sparkplug. It works for me. Though I've already ordered myself a new video card nice to see someone found the solution.

poor dm, ordered a card when the solution was3 days away
-
wifey

I was about to buy a new video card (9700) but I may put it off for a little while now (wait for price to drop a bit).

Is Marweas ever gonna reply to this?

I can't believe somebody finally figure this out. I've been stuck with sucky performance from my video card since I bought the thing because I could only use the oldest possible driver with T2 and still be able to play. You rock Sparkplug.

Has anyone tested the 9700 vs a gf4 4600 in t2?

Originally posted by: z0dd

Has anyone tested the 9700 vs a gf4 4600 in t2?

If you send 'em both, I'll test 'em both.
=)

Can someone give a link to d/l the recommended catalyst drivers for this?

SParkPlug=Genious