White screen in GLquake

[spooker]

I'm trying to help a good buddy of mine get back Quaking again. I only chatted with him briefly about the problem, and here is what I have so far (I will find out more later):
He bought a new computer, and when he tries to run GLQuake, the screen goes white. Its not a gamma problem, its not that kind of white. He tried Winquake and he gets an error. He thinks its a problem with his onboard video.

I'm sorry, but thats all the information I have for now. I will post more when I get it, specifically what versions of quake he is trying, what OS, what onboard video, etc. But, going on just this, can anybody help?

[Baker]

Have him download the ProQuake Launcher (http://www.quakeone.com/proquake) and in 30 seconds either he'll be able to fix it or not. It has a brightness setting, can start both hardware and software modes (GL or non-GL).

Plus, the ProQuake Launcher has diagnostics in "More Options" that displays all information on processor/OS/video card that can be cut and pasted if need be the case.

But the truth is, within 30 seconds flat either it will work or won't work.

/The ProQuake Launcher is sort of a do-all problem solver for stuff like this and is a lot quicker than taking 1 hour to explain things or have someone try different things. The ProQuake Launcher requires only Quake, it includes ProQuake and everything else (security.dll, etc.)

Btw ... the diagnostics looks like this ...

[Diagnostic Report: Wednesday, March 14, 2007]

App Version: ProQuake Launcher (1.1.1)

[Network]

// 1) Someone on the Internet would connect to this
// 2) Someone on your LAN would connect to this
// 3) If you have a router, typically this is what to type in
// your browser to access it (FireFox, Internet Explorer, ..)

1) Internet IP 67.149.220.91
2) Local IP Address 192.168.1.102
3) Default Gateway 192.168.1.1

[Video Mode]

Current Mode In Pixels 1152x864x32 bpp
Primary Display Adapter Intel(R) 82845G/GL/GE/PE/GV Graphics Controller (1)
Resolution Width X 1152
Resolution Height Y 864
Color Setting (True Color)
Vertical Refresh 60 Hz

[System]

Windows XP 5.1 build 2600 (Service Pack 1)

CPU Clock Speed 2.0 GHz (Gigahertz)
Memory Usage % 71 % used
Total Physical RAM 522,736 Kbytes
Total Available RAM 147,304 Kbytes
Processes Running: 25
.
.
.

[spooker]

thanks baker! will get him to try it!!

[Mindf!3ldzX]

It's his onboard video card. I had this problem trying to run GLQuake on my PC's onboard video (before I bought my 128mb Radeon 9200), just have him either run WinProQuake or DirectX Quake (WinProQuake > DirectX Quake) , or find him a cheap 32mb video card with OpenGL support. His onboard video might not even support WinQuake or DirectX Quake,and if it does he will have to toy with a good resolution,starting from 320x200 and working his way up.

ps : Baker,sorry,im old school I cant bring myself to use a Launcher ;O hehehehehe

[Baker]

Baker,sorry,im old school I cant bring myself to use a Launcher ;O hehehehehe

Au contraire!

You do not understand, Mindz!

Instead of answering questions like "How do I make it brighter?", "How do I set the resolution", "How do I play a demo?", "How do I make a Quake name?", "How do I add +mlook to my config", "How do I set my FOV?" (you know FOV doesn't save in your config, right?), "How do I make a quick grenade bind?", "What settings should I use" (pq_moveup 1, +mlook, cl_forwardspeed 999, etc.) and the billion other questions ... the ProQuake Launcher does it all.

The ProQuake Launcher is a way to avoid all of the pain. It is a self-help cheat! It is a magic bullet for new players so they can have an easy time and a magic bullet to avoid answering questions.

But my point is that Quake is such a hassle that it is ridiculous and it takes a ton of work to get it setup right out of the box.

It doesn't matter to me whether or not someone uses it. Although I do care about how easily new players can get setup, I mostly made the ProQuake Launcher because it is insanely dumb how much setup it requires to get Quake setup properly and it is a hell of a lot easier to just say "Get the ProQuake Launcher" than it is to answer the same questions over and over for eternity.

/I wish *all* of the things the ProQuake Launcher does were built into every engine *ALL* of the things the ProQuake Launcher does should be built into every engine in an Options menu.

[spooker]

I got him to try the launcher that you recommended Baker. He said it worked, he could launch GLPro, but it felt weird and unplayable, not at all like normal GLPro (which he used to play); he said it felt similar to Qrack. Idunno!

Oh, by the way, he said his OS is Windows 98!

[Mindf!3ldzX]

Get a new video card!

32mb Nvidia GF will do just fine, pick one up in the used bin at a local pc shop...


Baker , in all actuallity , your right...but Quake "out of the box" to me only needs a couple things.

Command line's ,which isnt that big of a deal to explain to people.
Sensitivity tweaking is 2.

And thats it, for ProQuake anyways...

All these "newer engines" not only came with a bunch of eyecandy,but a bunch of damn hogwash for configing.

[Baker]

I got him to try the launcher that you recommended Baker. He said it worked, he could launch GLPro, but it felt weird and unplayable, not at all like normal GLPro (which he used to play); he said it felt similar to Qrack. Idunno!

Oh, by the way, he said his OS is Windows 98!

Well, then it works!

Tell him to start Quake with ...

c:\quake\glpro.exe -width 640 -height 480 -bpp 16 -dinput -gamma 0.65

And he's all set and he can try it without the launcher. I consider the launcher training wheels.

[Baker]

Command line's ,which isnt that big of a deal to explain to people.

Yeah, but it shouldn't take Mindzfield to setup your Quake

I know what you mean and I'm old skool too.

But let's not forget that I am perfectly aware QuadRaptor always had to type +mlook in his console when starting Quake because he didn't know how to add it to his config and that Catgirl never ever got a custom Quake name to work, yet both knew you

And your one IHOC bud who was pissed that XQuake couldn't connect to Bomber and didn't want to add -gamma 0.5 to his command line so he wouldn't play with ProQuake.

[night1727]

I have an error with GLpro!!!

with glpro when I launch it every thing is white but you can see players and models you just cant see textures

ps: the models are toally white apart from shadows

[Canadian*Sniper]

with glpro when I launch it every thing is white but you can see players and models you just cant see textures

ps: the models are toally white apart from shadows

Sounds like your graphics card can't handle opengl. I had the same problem in the past. Try using winpro

[Baker]

Try adding -no8bit or -nomtex to the command line and see if it solves the problem.

According to past experience, that seems to fix it for most people if you mean the textures are all white.

[=peg=]

also make sure r_lightmap is set to "0"

[MH]

In my experience even an Intel 915 is capable of running Quake respectable enough. Unless it's a really old Intel or ATI, integrated graphics should be fine. I did see something similar on an old ATI integrated once (about 7/8 years ago), so the first thing you need to find out is can you run a baseline GLQuake setup.

My tips.

1) Start with a clean installation. This means your GLQuake.exe and an ID1 folder containing pak0.pak and pak1.pak - nothing else. No autoexec, no config, we want a totally clean slate with no unknown variables in it.

2) Preferably use an ID GLQuake.exe, and preferably one of the older ones before they hacked in multitexture. I think 0.95 is good.

3) Turn on view hidden files and make sure that there is no opengl32.dll in your Quake directory.

4) Run it with no command-line options. See what happens.

[BizarroEvade]

Try adding -no8bit or -nomtex to the command line and see if it solves the problem.

According to past experience, that seems to fix it for most people if you mean the textures are all white.

ROOK, I LOVE YOU!! I just put together a new comp and bought a modern video card. I had been on an ATI x700 until today. Soon as I popped in this geforce, my glpro (version 3.5) went to crap (white background, no textures). Regular glquake worked. Tried newer proquake. Didn't like the feel of it, but display worked. Just tried your command line option, glpro 3.5 works great now. Thanks!!!