Author Topic: 3_6_10 freezing  (Read 10582 times)

0 Members and 1 Guest are viewing this topic.

Offline Zacam

  • Magnificent Bastard
  • Administrator
  • 211
  • I go Sledge-O-Matic on Spammers
    • Minecraft
    • Steam
    • Twitter
    • ModDB Feature
ATI x1xxx card owners will have to try various ATi OpenGL file versions to find the one that is right for them if they want Shaders and Normal Maps. Hopefully there is a Vista variant (possible pre-7.1) that will work there or a prior linux kernel driver package.

Why? Because they didn't bother making their **** to spec. These shaders are fully SM3.0 qualified _even by ATi's own Render Monkey_. Because they decided to shortcut things by special extensions and call it "Fully Capable" instead of "Marginally Compatible", it does not process SM3 like it should. x3xx/x6xx cards are in an even worse boat, then only have HDR capabililty, and even _that_ is broken.

"But I have other SM 3.0 games, and they run FINE!" Yeah. And how many of them are running in OpenGL and how many of them are running in DX? So far as I can determine, FSO is _the_ only game that is OpenGL First and Foremost _and_ is using SM 3.0. Every other game that _could_ have OpenGL in it (Far Cry, broken especially with HDR on, Serious Sam 2, ugly in anything BUT DX Mode), does it at second best if it even bothers to do it at all.

Having stressed through the hardware (I obtained several ATi cards for free from a PC recycle center from a friend of mine) I can tell you that very little is going to change in the shaders from here on out for those cards, unless some sort of compatible code branch can be written in to the engine (which is a headache and a half times ten from what I gather). And given how much work would have to go in to making ATi specific copies of the shaders that at best won't do much for the performance on these cards because of a total lack of support for Vertex Texture Fetch, -no_glsl seems the better option all the way around.

And for the idea of SM 2. Potentially, a lot of the shader stuff could be SM2 and the higher end stuff could be SM 3. But you would still be in the same boat, because guess which of the two controls the normals and the ability to have the env acting on them? SM 3. And what could be converted to run SM 2 would see no benefit to it on SM3 capable systems and in fact could even slow it down.

I am still keeping the idea and options open. Because, by and large, I hate being defeated. But if you can't find an ATi opengl file to work things for you, then -no_glsl is the only other option.
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!
Talk with the community on Discord
"If you can keep a level head in all this confusion, you just don't understand the situation"

¤[D+¬>

[08/01 16:53:11] <sigtau> EveningTea: I have decided that I am a 32-bit registerkin.  Pronouns are eax, ebx, ecx, edx.
[08/01 16:53:31] <EveningTea> dhauidahh
[08/01 16:53:32] <EveningTea> sak
[08/01 16:53:40] * EveningTea froths at the mouth
[08/01 16:53:40] <sigtau> i broke him, boys

 

Offline Member!

  • 22
Hello everyone. I’m new here and I would like to thank everyone for your awesome support and dedication.
I also had experienced freezing problem with my X1950XT and x1950Pro Video cards. Here is what I have discovered.
In December 07 ATI removed 22 extensions from OpenGL, thus causing the problems. All ATI drivers starting with 7.12 will cause many GL games not to function properly. Also I would like to say that latest ATI 8.12 drivers have completely broke OpneGL on all Radeon X1K series.
One solution is to simply use older 7.11 drivers. Other, is to upgrade to latest Catalyst then put a copy of atioglxx.dll from Cat 7.11 into main folder of game that stopped working. Example: Copy atioglxx.dll to c:\games\freespace2.
What I did is this:
Installed Catalyst 8.10 and replaced atioglxx.dll in C:\Windows\system32 folder with atioglxx.dll from Cat 7.11 thus fixing this GL problem globally. 
Here is the good info on how to extract atioglxx.dll from Cat 7.11
http://www.game-warden.com/forum/showthread.php?t=6270.
 
So, now I can play Freespace without any problems, naturally this will make intro movie play in the left corner, but oh well. I can live with that for now. ;)
« Last Edit: December 21, 2008, 12:46:22 pm by Member! »

 

Offline Zacam

  • Magnificent Bastard
  • Administrator
  • 211
  • I go Sledge-O-Matic on Spammers
    • Minecraft
    • Steam
    • Twitter
    • ModDB Feature
Thank you. We already managed to determine as much in the Freespace Upgrade thread (read: HERE), though in some cases an even older Catalyst OpenGL driver is needed. (7.1).

We also know why it breaks on the older hardware (Lack of Vertex Texture Fetch and the fact that the newer drivers support it on the HD series cards, but you cannot have both VTF and Render To Vertex Buffer in the same driver).

This issue however does not seem to address usability under Vista, which will be the next thing that I test.

I am also a little leary of suggesting to people to global replace the system catalyst driver for OpenGL, even if it does make it more compatible with the hardware. I would either recommend running the driver package in it's entirety or use the OpenGL file locally in any game that needs it.
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!
Talk with the community on Discord
"If you can keep a level head in all this confusion, you just don't understand the situation"

¤[D+¬>

[08/01 16:53:11] <sigtau> EveningTea: I have decided that I am a 32-bit registerkin.  Pronouns are eax, ebx, ecx, edx.
[08/01 16:53:31] <EveningTea> dhauidahh
[08/01 16:53:32] <EveningTea> sak
[08/01 16:53:40] * EveningTea froths at the mouth
[08/01 16:53:40] <sigtau> i broke him, boys

 

Offline ShivanSpS

  • 210
What i dont know, if the X1K cards lacks the VFT hardware capability, why DX games can run using SM3?

Maybe they still do the VFT via software under DX???