Unofficial ProQuake 3.80 (Stable?)

[aguirRe]

You could try adding "-no8bit" or "-nomtex" to the ProQ cmd line.

[Phenom]

ok heres how it went down

D3DProQuake = loaded fine, crashed to desktop right when the first demo begins to play.

GLPRO380 + -no8bit -nomtex seemed to work fine!

*Update*

Added "-no8bit -nomtex -gamma .4" to my GLPro380 commandline and everything works so far thanks aguiRe!

[Baker]

*Update*

Added "-no8bit -nomtex -gamma .4" to my GLPro380 commandline and everything works so far thanks aguiRe!

Well, good. I'm glad to hear that.

[PapaSmurf]

So what does -no8bit and -nomtex do? Something to do with textures, i imagine.

[aguirRe]

Good that it works now. "-no8bit" will turn off a special OpenGL optimization that can cause problems with some cards, the usual symptom is all-white textures. This mode appeared first in the released engine code, so e.g. GLQ 0.97 doesn't have this issue. Some newer engines have disabled this mode altogether.

"-nomtex" just disables OpenGL multi-texture, which will typically make the engine slower as it possibly doesn't take full advantage of the gfx hardware. Running in this mode is probably not tested much, but at least it offers an alternative.

Btw, if you have issues with Q1 engines, you could check out my Q1 ToolTips document, section "Engine Problems": http://user.tninet.se/~xir870k/tooltips.txt

[Baker]

2 very small features added (see first post for revised download):

1. glpro380.exe terminates with a message if opengl32.dll is found in the Quake folder.
2. Added Rook's q_version code
3. Adding -nosoundkeys the command line will allow "old" operation of -/+ where you could use those keys however you choose (instead of them automatically be assigned as sound adjustment keys).

[R00k]

q_sysinfo is nice too, though i recommend it only to be used during intermisson

[Baker]

q_sysinfo is nice too, though i recommend it only to be used during intermisson

I thought about adding that. Maybe I will next time.

[Fuzznut]

Well, that sucks

The rendering code between GLQuake/ProQuake vs. Qrack are radically different. I don't believe there is really any way I could determine why GL ProQuake does this and Qrack does not.

This machine I use has a Intel Integrated Media chip and will not run any OpenGL Quake engine (I get a black screen; I have dual monitors with the other monitor using a GeForce.), but GL ProQuake works fine on some other Intel Integrated Media PCs I've used.

Does my Direct3D build work on your machine:

http://www.quakeone.com/proquake/uno...-d3dpro370.zip

If so, I will quickly re-add Direct3d support for 3.80 for you. (Direct3D versions do run on my Intel Integrated Media).

I have a 400mhz system with an ATI 3D RAGE II+DVD in it that from what I can tell only uses Direct3D. Give me a couple days to get situated and see if I can try this client out on that system.

Just put it in the Quake folder? Replace the Quake exe? What do I need to do here?

[Baker]

Just put it in the Quake folder? Replace the Quake exe? What do I need to do here?

Yeah, that's all you need to do.

I'm closing this thread because the current thread is this one:

http://www.quakeone.com/forums/showthread.php?p=36909

[Fuzznut]

Cute. What exactly is it that I say about Baker?

Hey, you're not suppose to be here when we're talking about you. Go on now.

[Canadian*Sniper]

Don't put any more words in my mouth fuzznut

[Fuzznut]

Don't put any more words in my mouth fuzznut

Snipes, you're cluttering up Bakers thread here.