Problem with Clients

[Mr.Goodbar]

EDIT: I just now realized this is in the wrong section. Sorry bout that.

If this is already in the forum, I'll just apologize now. I searched and couldn't find anything that solves my problem.

I'm having a huge problem with pretty much all Quake clients other than Winquake and WQPro. Nothing gl will work.

I recently had to replace my old video card, a geforce 9800GT and picked up a Geforce GTX 460 for cheap. Before the new card, everything worked fine, so I'm not sure if it's the problem or not.

I've tried deleting qsecurity.dll, opengl.dll and everything else that could cause the problems. I've tried running as administrator and messing with all the settings beforehand.

I've also tried disabling "DEP" after it said it was closing the client. That didn't help either.

I get this error on everything I try to open. I get this error for glpro, darkplaces, telejano and even glpro451. I've tried every client that I can possibly download. Still, this is what I get:



Has anybody ever had this happen?

Core system specs if you think it matters:

AMD Phenom II BE 955
NVidia Geforce GTX 460
6GB Ram
Gigabyte MA785GM mboard
Windows VISTA 64

[Baker]

Try DirectQ

mhquake

Your OpenGL drivers might be foobared. DirectQ doesn't run OpenGL (and DirectQ gets super high FPS).




^^ I thought that was a feature of Tenebrae

/End joke

[Syluxguy28O3]

question

could the video card cause the message " win quake.exe has encountered a problem and needs to close"?

[Mr.Goodbar]

Is there any way to fix it? I've really been wanting to play with some of the more graphic enhanced stuff. DirectQ works good. I guess that will be my primary client until I resolve this problem.

Well, I guess if that's a regular known problem for Tenebrae, I'll skip that one.

[Baker]

Is there any way to fix it? I've really been wanting to play with some of the more graphic enhanced stuff.

Sounds like you have video card issues going on. All of the clients you listed run fine on 64-bit machines with working OpenGL drivers.

DirectQ works good. I guess that will be my primary client until I resolve this problem.

DirectQ is a great client. It has only existed a couple of years.

Well, I guess if that's a regular known problem for Tenebrae, I'll skip that one.

I was kidding around. There is nothing wrong with Tenebrae. It is known for the low frames per second and having non-standard everything, but it has its own flavor of rendering that is quite unique and plastic-like.

[Mr.Goodbar]

I know you were kidding. I really liked the lighting in Tenebrae and it has a certain charm to it that made me wanna play it more.

Not sure what's going on with the video card drivers. I installed the latest update and problem is still going on. It's a bummer, because I really liked some of those other clients. Any other suggestions are welcome.

[Spike]

if a large number of unmaintained quake engines crash upon startup, but the active ones don't, then its probably because those unmaintained versions of quake can't handle how many extensions your graphics drivers have.
nvidia have an 'extension limit' option in the drivers. set it to on. this should fix any issues - assuming you use nvidia. ATI likely have a similar setting somewhere.

[Baker]

I get this error for glpro, darkplaces, telejano and even glpro451. I've tried every client that I can possibly download. Still, this is what I get:

@Spike re:extensions

Yeah, but DarkPlaces and glpro451 don't print extensions to the console.

[@goodbar, Spike is referring to a big long of extensions that, say, GLQuake prints to the console that is too big for the Quake console buffer to hold ... which makes the .exe crash. But, for instance, DarkPlaces got rid of that issue maybe 10 years ago. Modern ProQuake that issue was fixed since version 3.70 or older.]

[Mr.Goodbar]

[@goodbar, Spike is referring to a big long of extensions that, say, GLQuake prints to the console that is too big for the Quake console buffer to hold ... which makes the .exe crash. But, for instance, DarkPlaces got rid of that issue maybe 10 years ago. Modern ProQuake that issue was fixed since version 3.70 or older.]

Gotcha. Gonna dig deeper into this extension stuff. I'll start poking around to see what I can do with it.

[Baker]

Wait! I was saying that does not have anything to do with your problems.

Spike suggested the old "too many extensions crash" ... but DarkPlaces and glpro451 can't crash from that.

And yet you have DarkPlaces and glpro451 crashing.

Whatever you problems are, it isn't that.

[Mr.Goodbar]

It's cool. I didn't change anything. I'll use one of the other clients for now. I've tried every search possible, but have come up with nothing. Kind of strange since every other nvidia card I've had (if that's the problem) worked fine, but this one wants to be a problem.

[MH]

Limiting the extension string might cause other problems too - if a required extension (or one that the engine has a faster or higher quality path for) gets chopped off, you won't be getting the best out of your hardware.

Tenebrae is an interesting case. It actually crashes under a modern OS even if the drivers (and other engines) are working right. Last year I recompiled a version of it that does work, which may be useful for helping to diagnose this problem.

http://www.quaketastic.com/upload/fi...ebrae_2010.zip

[Mr.Goodbar]

Limiting the extension string might cause other problems too - if a required extension (or one that the engine has a faster or higher quality path for) gets chopped off, you won't be getting the best out of your hardware.

Tenebrae is an interesting case. It actually crashes under a modern OS even if the drivers (and other engines) are working right. Last year I recompiled a version of it that does work, which may be useful for helping to diagnose this problem.

http://www.quaketastic.com/upload/fi...ebrae_2010.zip

Tried that one, too. It opens, starts to load then crashes.

[Baker]

Limiting the extension string might cause other problems too - if a required extension (or one that the engine has a faster or higher quality path for) gets chopped off, you won't be getting the best out of your hardware.

I'm not looking at source code right now, but I was thinking that the gl_extensions string is a const char* reference.

Like ...

const char * gl_extensions = glGetString (GL_EXTENSIONS);

I guess my question is ... can that can chopped off? I don't claim to know what the limitations are of glGetString or maybe there is something I am completely missing.

[bluntz]

May make sure Direct X is updated as well.I have been having similar issues since updating my Nvidia drivers.So far after Having even DQ fail me I tracked some of it down to D3D_49.dll missing.
After updating it seems ok but my GL clients keep crashing,even Qrack witch I have used for years with little issue is randomly crashing now.I am using a 9400GT and thought I just needed to upgrade to the GTX .
I hope you get this one sorted out Baker.