Hard Light Productions Forums

Hosted Projects - Standalone => The Babylon Project => Topic started by: Fjellsveis on December 23, 2008, 12:06:27 pm

Title: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 23, 2008, 12:06:27 pm
Hullo again.

Once I had installed the TBP files and installed it, upon running the game from the launcher after adjusting the settings, I get the:
Unable to get proper pixel format for OpenGL W32! - error.
Which is annoying, because I've gotten the game to run using D3D, but that option doesn't work with the TBP.

So, I'm sorry if a fix has been posted, but seriously, I'm not going to rummage through 90+ pages, and I couldn't think of search queries to match the problem.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 23, 2008, 12:10:50 pm
This isn't the BP mod area.  If you meant TBP then you have a problem with your video card and/or drivers.  Check here for info:  http://www.hard-light.net/forums/index.php/topic,56279.msg1180356.html#msg1180356
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 23, 2008, 12:18:19 pm
Yes, well, I've tried both of the 'fixes' when I first got the FSO, which didn't work for no goddamn reason, that's why I'm running D3D in the first place.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Wanderer on December 23, 2008, 12:23:09 pm
Run debug build. Find 'freespace/data/fs2_open.log' as described here... http://www.hard-light.net/forums/index.php/topic,56279.msg1180359.html#msg1180359 - section marked Your fs2_open.log:

Post the log here using 'code' tags and lets have a look at it.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 23, 2008, 12:27:12 pm
What video card/chipset do you have.  I'm guessing Intel.   

You can try a 3.6.10 build and see if that helps.  If you still get the crash run the debug build and attach the fs2_open.log from the data folder.
The other option if you card wont' support OpenGL is a D3D exe.  There is one posted around here somewhere.

Note: 3.6.10 isn't officially supported for TBP unless it's multiplayer. 


@ Wanderer:  What the heck are we going to keep posting at the same time all day or what?
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 23, 2008, 12:37:37 pm
What video card/chipset do you have.  I'm guessing Intel.   

You can try a 3.6.10 build and see if that helps.  If you still get the crash run the debug build and attach the fs2_open.log from the data folder.
The other option if you card wont' support OpenGL is a D3D exe.  There is one posted around here somewhere.

Note: 3.6.10 isn't officially supported for TBP unless it's multiplayer. 


@ Wanderer:  What the heck are we going to keep posting at the same time all day or what?

I'm using Nvidia nForce 570 SLI chipset.

I'll run the debugging in a little.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 23, 2008, 01:04:30 pm
Code: [Select]
==========================================================================
DEBUG SPEW: No debug_filter.cfg found, so only general, error, and warning
categories can be shown and no debug_filter.cfg info will be saved.
==========================================================================
Passed cmdline options:
  -missile_lighting
  -dualscanlines
  -orbradar
  -targetinfo
  -mod cardinalspear,fsport,mediavps
Building file index...
Searching root 'C:\progra~1\gog.com\freesp~1\cardinalspear\'
Searching root pack 'C:\progra~1\gog.com\freesp~1\cardinalspear\fsport-cardinalspear-voice.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\cardinalspear\fsport-cardinalspear.vp'
Searching root 'C:\progra~1\gog.com\freesp~1\fsport\'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\FS1OGGcutscenepack.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\fsport-hi_res.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\fsport-missions.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\fsport3_0_4.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\sparky_hi_fs1.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\stu_fs1.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\tango_fs1.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport\warble_fs1.vp'
Searching root 'C:\progra~1\gog.com\freesp~1\mediavps\'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mp-710_adveffects.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mp-710_effects.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mp-710_models.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mv_adveffects.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mv_core.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mv_effects.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mv_models.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mv_music.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\mediavps\mv_textures.vp'
Searching root 'C:\progra~1\gog.com\freesp~1\'
Searching root pack 'C:\progra~1\gog.com\freesp~1\Crucible.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\FS2OGGcutscenepack.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport-cardinalspear-voice.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport-cardinalspear.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\Homesick.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\Root_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\smarty_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\sparky_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\sparky_hi_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\stu_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\tango1_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\tango2_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\tango3_fs2.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\warble_fs2.vp'
Found 37 roots and 15310 files.
Setting language to English
Initializing OpenAL...
  Using 'Generic Software' as OpenAL sound device...
  OpenAL Vendor     : Creative Labs Inc.
  OpenAL Renderer   : Software
  OpenAL Version    : 1.1

... OpenAL successfully initialized!
GR_CPU: Family 15, MMX=Yes
Initializing OpenGL graphics device at 1280x1024 with 32-bit color...
  Initializing WGL...

This is what the debug turned up.
System specs are, the top portion of the DxDiag;
------------------
System Information
------------------
Time of this report: 12/12/2008, 16:27:36
       Machine name: POSTEITRYNET
   Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.080814-1233)
           Language: English (Regional Setting: Norwegian (BokmÃ¥l))
System Manufacturer: MSI
       System Model: MS-7250
               BIOS: Default System BIOS
          Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+,  MMX,  3DNow (2 CPUs), ~2.2GHz
             Memory: 3072MB RAM
          Page File: 568MB used, 3878MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.2180 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
          Music Tab: No problems found.
          Input Tab: No problems found.
        Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (n/a)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: NVIDIA GeForce 8800 GT
     Manufacturer: NVIDIA
        Chip type: GeForce 8800 GT
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0611&SUBSYS_23331682&REV_A2
   Display Memory: 512.0 MB
     Current Mode: 1280 x 1024 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.8048 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 11/12/2008 14:54:00, 6148864 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 11/12/2008 14:54:00, 6188320 bytes
Device Identifier: {D7B71E3E-4551-11CF-426A-380303C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0611
        SubSys ID: 0x23331682
      Revision ID: 0x00A2
      Revision ID: 0x00A2
      Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
 Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
         Registry: OK
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
DDraw Test Result: Not run
 D3D7 Test Result: Not run
 D3D8 Test Result: Not run
 D3D9 Test Result: Not run
___________________________
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 23, 2008, 01:29:50 pm
Thats not a log from The Babylon Project it's from FSPort Cardinal Spear. 
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Wanderer on December 23, 2008, 01:37:01 pm
Regardless where the log is from... Driver seems to be ok. Card itself certainly is. Hmmm... Make sure you have not enabled the extension limits (check from Nvidia control panel).. And as expected the game starts in OpenGL mode regardless (its better to choose that from the list in the first place).
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Jeff Vader on December 23, 2008, 01:52:22 pm
Not related to TBP or the issue at hand:

Code: [Select]
Searching root pack 'C:\progra~1\gog.com\freesp~1\Crucible.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport-cardinalspear-voice.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\fsport-cardinalspear.vp'
Searching root pack 'C:\progra~1\gog.com\freesp~1\Homesick.vp'
There shouldn't be any non-retail vp files in your root directory, apart from the cutscene pack and possibly the two multiplayer vps. And you already had Cardinal Spear in its own subfolder so I can't understand why you'd have it in the root directory as well.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 25, 2008, 12:23:04 pm
Thats not a log from The Babylon Project it's from FSPort Cardinal Spear. 

Ooh, bollocks. Is this the correct log, then? I've kind of lost track, with all these modification instructions the different campaigns come with.
And Lobo, I'm not sure what exactly to delete here. I mean, the files aren't exactly called 'Irrelevantfile.vp'.

Code: [Select]
==========================================================================
DEBUG SPEW: No debug_filter.cfg found, so only general, error, and warning
categories can be shown and no debug_filter.cfg info will be saved.
==========================================================================
Passed cmdline options:
  -ambient_factor 65
  -env
  -jpgtga
  -mipmap
  -missile_lighting
  -glow
  -nomotiondebris
  -spec
  -ballistic_gauge
  -dualscanlines
  -orbradar
  -rearm_timer
  -targetinfo
  -3dwarp
  -warp_flash
  -tbp
Building file index...
Searching root 'C:\program files\gog.com\freespace 2\babylon\'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\B5-C-sp-EMW-3_0.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\B5-C-sp-RW-3_0.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\B5-Core-3_4.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\B5-M-MultiPack-1_0.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\Root_fs2.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\sparky_fs2.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\sparky_hi_fs2.vp'
Searching root pack 'C:\program files\gog.com\freespace 2\babylon\stu_fs2.vp'
Searching root 'd:\'
Found 10 roots and 8579 files.
Setting language to English
Initializing OpenAL...
  Using 'Generic Software' as OpenAL sound device...
  OpenAL Vendor     : Creative Labs Inc.
  OpenAL Renderer   : Software
  OpenAL Version    : 1.1

... OpenAL successfully initialized!
GR_CPU: Family 15, MMX=Yes
Initializing OpenGL graphics device at 1280x1024 with 32-bit color...
  Initializing WGL...

Oh. Happy Christmas or whatever.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 26, 2008, 01:06:01 am
No idea why you have ballistic-gauge turned on but I don't think that is causing the problem. 

Do I understand you right that you are saying you can run FS2 in D3D mode but not OpenGL?  If so I think there is a D3D version of TBP.  Can't say it's 100% tested but I'll try to dig it up.

Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: karajorma on December 26, 2008, 03:42:57 am
http://www.freespacefaq.com/Misc-Downloads/Builds/BtRL_D3D_Exes.zip

and

http://www.freespacefaq.com/Misc-Downloads/Builds/BtRL_D3D_Inferno_Builds.zip
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 26, 2008, 12:00:42 pm
Thanks.  Spent about an hour hunting for those before I gave up. 
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 26, 2008, 12:46:42 pm
No idea why you have ballistic-gauge turned on but I don't think that is causing the problem. 

Do I understand you right that you are saying you can run FS2 in D3D mode but not OpenGL?  If so I think there is a D3D version of TBP.  Can't say it's 100% tested but I'll try to dig it up.



Yes, I cannot.

http://www.hard-light.net/forums/index.php/topic,58280.0.html

And thanks for the links, Karaj.

Update: I had some odd problems with the smoke/fires from hull-breaches on ships. The same thing when, for example, I blew up an asteroid. Basically, instead of fires and smokes, I get huge white blocks. In the case of the asteroids, my screen turns white from the hugeness of the block. So when I tweaked the features in the Launcher to see if I could fix it, I get this error when I try to start it up again;

Warning: Too many ship classes before 'Sinclair's Aurora'; maximum is 130, so only the first 130 will be used
File:D:\C++\Freespace\fs2_open 3.6.9 - BtRL\code\ship\Ship.cpp
Line: 2884
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    parse_shiptbl()    parse_modular_table()    ship_init()    game_init()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------



NEW UPDATE: Fixed the Launcher-error by running the game directly from the .exe instead of the Launcher. Tried different settings on the particle qualities, etc, only succeeded in slightly turning the horrible lag I get from watching the white blocks down.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 26, 2008, 01:06:11 pm
Those warning only appear in the debug builds.  Switch back to the regular one.  As for the boxes make sure you have the -jpgtga flag on.  Looks like you did but switching builds will sometimes disable it.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 26, 2008, 01:35:13 pm
Those warning only appear in the debug builds.  Switch back to the regular one.  As for the boxes make sure you have the -jpgtga flag on.  Looks like you did but switching builds will sometimes disable it.

Adding in the flag didn't fix it.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 26, 2008, 01:46:26 pm
Can't believe I didn't notice this before.  Why do you have TBP under your FS2 folder?  TBP is a standalone program and not a mod.  It should not be under your FS2 folder.  You are loading both TBP and FS2 stuff at the same time that is bound to cause problems.  I suggest a complete reinstall of TBP in the correct folder for starters. 
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 26, 2008, 01:51:02 pm
Can't believe I didn't notice this before.  Why do you have TBP under your FS2 folder?  TBP is a standalone program and not a mod.  It should not be under your FS2 folder.  You are loading both TBP and FS2 stuff at the same time that is bound to cause problems.  I suggest a complete reinstall of TBP in the correct folder for starters. 


[Words that describe rage and frustration well]
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 26, 2008, 03:05:26 pm
Reinstalled in an entirely different directory. The problem is still there. Smoke effects are still white blocks and lags me horribly.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Jeff Vader on December 26, 2008, 03:07:27 pm
As andicirk once said (pretty much): your Windows is probably dying. The simplest solution would be for you to reinstall Windows entirely.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 26, 2008, 03:22:08 pm
Do you have the latest drivers for you video card?  http://www.nvidia.com/object/winxp_180.48_whql.html
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: Fjellsveis on December 26, 2008, 05:41:58 pm
Do you have the latest drivers for you video card?  http://www.nvidia.com/object/winxp_180.48_whql.html

Yes.

And I'd rather dissect my own, still living dog, Lobo.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: FUBAR-BDHR on December 26, 2008, 06:27:52 pm
I think I've had it with your attitude.  We try to help and every idea is met with nothing but criticism.
Title: Re: Unable to get proper pixel format for OpenGL W32! -Using D3D. What.
Post by: karajorma on December 26, 2008, 06:45:32 pm
The white boxes are a side-effect of running in D3D. It's crap like that that made us abandon D3D support in the first place. D3D builds are basically provided as a last ditch solution. If they work, great. If not, then that's unfortunate for you but D3D won't be getting fixed any time soon (if ever) since pretty much everyone has moved over to OpenGL (which appears to be borked for you).