* July 25, 2014, 01:34:03 AM
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Come Chat with us live! Learn how HERE!
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: GLW_ChoosePFD failed ?  (Read 7431 times)
Nomad
Guest
« on: April 16, 2006, 04:00:27 AM »

Hi, I seem to have a problem running Tremulous.
It works fine on four out of five of my computers, but on this system here it doesn't work. I am using the exact same video card as another computer, on which it runs just fine (NVidia GeForce 2 MX/MX 400). Same operating system too (Win98).
I got the latest geforce drivers from nvidia's site, and am currently running the latest version of directx. This is what I get in the console:

tremulous 1.1.0 win_mingw-x86 Feb 28 2006
----- FS_Startup -----
Current search path:
C:\Program Files\Tremulous\base\vms-1.1.0.pk3 (4 files)
C:\Program Files\Tremulous\base\map-uncreation-1.1.0.pk3 (110 files)
C:\Program Files\Tremulous\base\map-tremor-1.1.0.pk3 (45 files)
C:\Program Files\Tremulous\base\map-transit-1.1.0.pk3 (135 files)
C:\Program Files\Tremulous\base\map-niveus-1.1.0.pk3 (134 files)
C:\Program Files\Tremulous\base\map-nexus6-1.1.0.pk3 (151 files)
C:\Program Files\Tremulous\base\map-karith-1.1.0.pk3 (118 files)
C:\Program Files\Tremulous\base\map-atcs-1.1.0.pk3 (87 files)
C:\Program Files\Tremulous\base\map-arachnid2-1.1.0.pk3 (67 files)
C:\Program Files\Tremulous\base\data-1.1.0.pk3 (1229 files)
C:\Program Files\Tremulous/base

----------------------
2080 files in pk3 files
execing default.cfg
couldn't exec autogen.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
...detecting CPU, found generic

------- Input Initialization -------
No window for DirectInput mouse init, delaying
Joystick is not active.
------------------------------------
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\WINDOWS\SYSTEM\opengl32.dll' ): succeeded
...setting mode 3: 640 480 FS
...using desktop display depth of 32
...calling CDS: ok
...registered window class
...created window@0,0 (640x480)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 32, 24, 8 )
...23 PFDs found
...GLW_ChoosePFD failed
...GLW_ChoosePFD( 32, 24, 0 )
...23 PFDs found
...GLW_ChoosePFD failed
...failed to find an appropriate PIXELFORMAT
...restoring display settings
...WARNING: could not set the given mode (3)
...setting mode 3: 640 480 FS
...using colorsbits of 16
...calling CDS: ok
...created window@0,0 (640x480)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 16, 16, 0 )
...23 PFDs found
...GLW_ChoosePFD failed
...GLW_ChoosePFD( 16, 16, 0 )
...23 PFDs found
...GLW_ChoosePFD failed
...failed to find an appropriate PIXELFORMAT
...restoring display settings
...WARNING: could not set the given mode (3)
...shutting down QGL
...unloading OpenGL DLL
...assuming '3dfxvgl' is a standalone driver
...initializing QGL
...WARNING: missing Glide installation, assuming no 3Dfx available
...shutting down QGL
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
GLW_StartOpenGL() - could not load OpenGL subsystem


It matches the console of the systems that are running it properly up until
...23 PFDs found [over 100 on my other computer]
...GLW_ChoosePFD failed [is this the problem?]
I've spent about an hour googling around trying to figure out how to resolve this... I must have missed the solution :\
Any help would be greatly appreciated, thank you!
Logged
[EVIL]Unknown


Turrets: +1/-1
Posts: 263


WWW
« Reply #1 on: April 16, 2006, 12:55:49 PM »

well im not an expert in this field but try rolling back the driver for ur vid card and c what happens... is there anything else diff from the other system u said that has the same vid card that works fine???
Logged

url=http://userbars.org][/url]

Royale


Turrets: +0/-0
Posts: 11


« Reply #2 on: April 30, 2006, 06:13:23 AM »

Well from what I remember of OpenGL coding a PFD is a pixel format descriptor errors stemming from an incorrect PFD usually has to do with bad resolution or color depth settings. As mentioned in the previous post you can try rolling back drivers and also try reinstalling opengl and or change color depth\resolution.
Logged
Teiman


Turrets: +0/-0
Posts: 286


« Reply #3 on: May 07, 2006, 01:01:30 PM »

Quote from: "Royale"
Well from what I remember of OpenGL coding a PFD is a pixel format descriptor errors stemming from an incorrect PFD usually has to do with bad resolution or color depth settings. As mentioned in the previous post you can try rolling back drivers and also try reinstalling opengl and or change color depth\resolution.


Maybe he can try to change the defalt setting for Tremulous, so the game try to use other config.  32bpp instead of 16bpp,  no stencil buffer (?), etc.

Something like this (I have no idea of what exact command sould be)
$ ./tremulous -bpp 32  

read the manual will be needed..
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC
TremPlus theme by Ingar, based on AF316 theme by Fedhog
Valid XHTML 1.0! Valid CSS!