[Fjellsveis]

Hmm. Use CPU-Z (link in my signature) to check the model name of your chipset. That might help in searching for the drivers, particularly since the MSI page lists two possible chipset candidates.

That's a lovely program! I'm using Nvidia nForce 570 SLI chipset. Downloading now.

[Fjellsveis]

Brand new graphics' drivers, new chipset drivers, and no go. This really just does not want to work.

Same error message, Unable to get proper pixel format for OpenGL W32!.

[captain-custard]

i had a problem a little like this .......


go here http://www.realtech-vr.com/glview/

and download and run it to check that your opengl settings to see if anything is missing...........

heres the link to my problem http://www.hard-light.net/forums/index.php/topic,57370.msg1157682.html#msg1157682

[Fjellsveis]

i had a problem a little like this .......


go here http://www.realtech-vr.com/glview/

and download and run it to check that your opengl settings to see if anything is missing...........

heres the link to my problem http://www.hard-light.net/forums/index.php/topic,57370.msg1157682.html#msg1157682

Yeah, no, that didn't help.

[captain-custard]

its not a fix , its just to see if your missing open gl extensions , which i was ...

[Fjellsveis]

its not a fix , its just to see if your missing open gl extensions , which i was ...

No extensions missing from what I can tell.

[General Battuta]

Does retail work? Try running Freespace 2 without FSOpen.

[Fjellsveis]

Does retail work? Try running Freespace 2 without FSOpen.

Works just fine, even if I have to enable compatibility for Win98.
And I'm walking a fine line here. I've spent two goddamn days trying to get this working, and noone has any idea what's wrong.
Seriously, what kind of magical hijjinks do you perform on your desktops that makes it accept this stuff? [Rambling profanity that's being censored.]

[captain-custard]

go into the launcher/video   in the graphics tab select direct3D8  and whatever else you think ok then try running and if it works i have a really ****ty solution....

[karajorma]

D3D would work (badly) with 3.6.9 builds but I'd recommend trying a 3.6.10 build from the nightly builds forum first.

[Fjellsveis]

D3D would work (badly) with 3.6.9 builds but I'd recommend trying a 3.6.10 build from the nightly builds forum first.

Doesn't work. Neither in D3D nor other modes.

[Jeff Vader]

With 3.6.9 and Direct3D it definitely shouldn't give the same OpenGL error.

[Herra Tohtori]

*The following is classified level Rho.*

This is an excerpt from a communications log from a "sekret mediavp talk channel" and might be relevant to your current plight.

DO NOT blindly add registry entries unless you know for sure you can fix whatever you do. I don't know if the entries referred in the log would help in your particular situation.

Code: [Select]

<Zacam> And I think I may have a solution (for nVidia users atleast) on the whol OpenGL w32 issue. Maybe.
<HerraTohtori> enlighten me
<Zacam> I noticed that Opengl Extensions viewer from vpTech was unable to parse the DLL version for OpenGL rendering that I was using. And it listed a key location in the registry.
<Zacam> Ironically, the INF for the video card deletes the key location it is trying to find information for/in.
<HerraTohtori> oh snap
<Zacam> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\
<Zacam> Add a key in there called RIVATNT
<HerraTohtori> rivatnt... as in the ancient history GPU?
<Zacam> In that, add: DLL (string) value: nvoglv32.dll
<Zacam> Yeah.
<Zacam> Other accepted values: (as DWORDs) "Flags:0x00000003 (3)" and "Version: 0x00001000 (4096)"
<Zacam> The (3) and (4096) are the decimal values.
<HerraTohtori> how trivial :/
<HerraTohtori> so... make it so that the Launcher constructs this registry entry in addition to others it does if they don't exist?
<Zacam> So far, it hasn't broken anything at all and OpenGL Extensions veiwer now knows what OpenGL and Driver version I am using.
<Zacam> Errr. No.
<HerraTohtori> wut
<Zacam> Heh.
<Zacam> Because there are coresponding ATI ones as well. And I don't have enough information regarding those yet to make it a good idea.
<HerraTohtori> who the hell had the bright idea of using operating system's registry for storing application data anyway -_-
<HerraTohtori> well... make it so that the Launcher reads what is in use and constructs the registry entry accordingly
<Zacam> It's not application data. It _is_ system data saying "Yo, here is your OpenGL" at an OS level without relying on having the driver intercept or the API pass off to.
<HerraTohtori> well, I was talking in general level
<HerraTohtori> using registry instead of config files
<Zacam> According to the openGL spec, the way to probe that is via the key I just mentioned. That the driver deletes during install.
<HerraTohtori> well that's just dumb.
<Zacam> Because that is where M$ stores the OS layer ICD information.
<Zacam> Er, GDI, sorry.
<HerraTohtori> those acronyms mean little to me so... :D
<Zacam> The GDI is _assumed_ to be over-ridden by the driver, but _especially in vista_ the default GDI acceleration on an OS level is DX, not OpenGL.
<Zacam> GDI controls the screen rendering elements relevant to the desktop.
<Zacam> And any desktop rendered applications.
<Zacam> With no listed GDI OpenGL key, any OpenGL to the desktop is now apprehended by the D3D and passed via the driver interaction to the OpenGL driver, instead of straight from API to OpenGL.
<Zacam> w32 being the API.
<Zacam> OpenGL being the function
* HerraTohtori blinks
<HerraTohtori> this is going over my head in details, but I think I got the gist
<Zacam> The erre  translates as: I cannot find a valid OpenGL GDI handler! Halp!
<HerraTohtori> so... why is that pointer to OpenGL GDI handler being removed?
<Zacam> I think they mean it to take place during init of the driver install to prevent conflicts that cause the issue. If you had both RIVATNT (or any other nVidia Product) and ati2dvag (or any other ATI Product) both at the same time AND a M$ GDI ICD, then *whammo* it's now playing ping-pong while you have either a frozen system or a BSOD.
<Zacam> I found the info through a search that lead me to the ReactOS pages on OpenGL that clued me in, especially with the extensions viewer saying my driver was out of date and/or not registered.
<Zacam> Which means it called to the OS GDI query and failed to get expected results because there was nothing where it was looking to tell it the file it needed to find.
<Zacam> Also, depending on the driver and hardware, instead of nvoglv32, it could be nvoglnt (depending what is in system32. And my bad, remove the .dll if you use that entry.

So... yeah. Might be related, but I'm not really able to directly tell you what you should do in this case.

[Fjellsveis]

With 3.6.9 and Direct3D it definitely shouldn't give the same OpenGL error.

Indeed, I stand corrected. It now works when running it in D3D. After a few test-runs, I am very impressed with the work you've done. Yet I feel a little cheated, because I know there's so much more, because damn, ships looks clunky.

[captain-custard]

ok in my experience , re-run the open gl test and check at the end if its missing any extensions or if it has them but isnt running them , this was my problem , and as i said i only found one ****ty solution......

[Jeff Vader]

With 3.6.9 and Direct3D it definitely shouldn't give the same OpenGL error.

Indeed, I stand corrected. It now works when running it in D3D. After a few test-runs, I am very impressed with the work you've done. Yet I feel a little cheated, because I know there's so much more, because damn, ships looks clunky.

Yet it makes my soul bleed to recommend you to play in Direct3D. Because Direct3D is no longer supported and 3.6.9 is the last build that allows you to use it. And even then there are some fantastic issues such as lower graphics quality compared to OpenGL, unexplainable performance drops and the inability to play cutscenes.

But please don't concider this to be normal. There are very few people who have severe problems with running FSO. Mostly it's about the basic little things, like forgetting to install OpenAL.

[chief1983]

I've run into problems with my setup where nothing short of a reformat seemed to fix the problems.  I've had both D3D and OpenGL stop working almost at all at different times.  Driver uninstalls and reinstalls wouldn't take care of it.  Not saying that I recommend you jump out and do that, but it has been the only solution for me in the past.

[captain-custard]

if you find there are missing extensions ,and as i have read you have reinstalled drivers etc ( hopefully having completely de-installed those drivers 1st) read the solution posted by Herra Tohtori and also have a look on the open gl site for other solutions..... if you cant fix it , i found that my problem was caused by a fault in my windows xp build so you could try repairing it ..... this sounds drastic but double check everything and post the open gl results here ( before you start fixing it) some one will be able to see anything thats amiss.... good luck

[Fjellsveis]

New error whilst playing the FSO-FS 1 campaign:
Error: Invalid ship class name.

In sexpression: ( when
   ( true )
   ( allow-ship "GTF Valkyrie" )
   ( tech-add-ships
      "GTF Valkyrie"
      "PVF Seth"
      "PVB Osiris"
      "PVF Horus"
   )
)
(Error appears to be: GTF Valkyrie)
File:J:\src\cvs\fs2_open_3_6_9.final\code\Mission\MissionParse.cpp
Line: 5798
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

I'll get back on trying to fix this tomorrow. But goddamnit, there's barely good news.

[Zacam]

The short summary of the excerpt Herra posted is try adding this in your registry:

Code: [Select]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\RIVATNT]
"Flags"=dword:00000003
"Dll"="nvoglv32.dll"
"Version"=dword:00001000

Paste the above into a file saved as riva.reg and merge via right-click menu.

Also, if you have any third party desktop enhancement tools that are running that are providing any window transparency effects, try temporarily turning them off before playing. I only occasionally ran into issues under XP whenever I was turning explorer windows semi-transparent and then launched a full screen OpenGL app. (I was doing the app window transparency through the nVidia Desktop tools. I no longer do so, but I am also running Vista now.)