Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Fjellsveis on December 11, 2008, 03:52:12 pm
-
So, I just got around to reinstall Freespace. And, well, to cut to the chase, it doesn't work.
The error message is:
Unable to get proper pixel format for OpenGL W32!
And taking from your Troubleshooting guide;
* Make sure that you have (the newest) graphics card drivers and chipset drivers installed.
* Make sure that you're using 32-bit colours for both your desktop and the game itself (can be changed from the Launcher's Video tab).
Being blunt, neither fix works. I followed the instructions for the Source step-by-step, and with the latest 5.5C Launcher version. Anyone have any explenation of sorts?
-
whats your graphics card?
-
Nvidia 8800 GT.
-
Latest launcher is 5.5d, not 5.5c. It's linked in the Nightly Build FAQ (http://www.hard-light.net/forums/index.php/topic,56458.0.html). I'd get it anyway, but I don't think it's going to solve your problem. What instructions did you follow? Did you use Turey's installer over an existing retail install, or just build the directory yourself by hand, or something else? Need MOAR info.
-
Latest launcher is 5.5d, not 5.5c. It's linked in the Nightly Build FAQ (http://www.hard-light.net/forums/index.php/topic,56458.0.html). I'd get it anyway, but I don't think it's going to solve your problem. What instructions did you follow? Did you use Turey's installer over an existing retail install, or just build the directory yourself by hand, or something else? Need MOAR info.
What I used is all in this thread; http://hard-light.net/wiki/index.php/Installing_fs2_open
As I understand it, the game itself is downloaded by the installer itself. No files were present prior to installation. I did nothing that the walkthrough didn't advise to do. And no, getting 5.5c didn't solve it. Keep asking, I'm here all night.
-
Crap I can't believe that wasn't updated yet. The FSO installer no longer includes retail files since you can now legally acquire FS2 for $6 from GOG.com, and it's not just some used copy like ebay, they're now an official distributor. I'll have to remember to update that later tonight unless someone beats me to it. In the mean time you need the FS2 retail data somehow.
-
Crap I can't believe that wasn't updated yet. The FSO installer no longer includes retail files since you can now legally acquire FS2 for $6 from GOG.com, and it's not just some used copy like ebay, they're now an official distributor. I'll have to remember to update that later tonight unless someone beats me to it. In the mean time you need the FS2 retail data somehow.
Grand, so it's a file of 2.88GB of nothing but mods?
Sweet. I didn't waste any time at all. Oh wait, it took up most of my day trying to figure this out.
-
Well all you need now is the retail data and you can play it. It wasn't a complete waste. You might be able to find the discs somewhere without having to pay for them, but no one here can help you out, as we want to see people owning legal copies. Is that such a bad thing?
-
Well all you need now is the retail data and you can play it. It wasn't a complete waste. You might be able to find the discs somewhere without having to pay for them, but no one here can help you out, as we want to see people owning legal copies. Is that such a bad thing?
Yes, for I like conformism, and you've just forced me to physically use my body in order to obtain stimulus.
-
I'm not sure if you're being sarcastic or really angry or what. I can't tell you to appreciate the work done here by volunteers, but I can say that if you really are upset at the change no one around here will miss you much if you leave, as we all appreciate the work done by :V: and Interplay to pay for their game, and then to spend countless hours making it prettier for those who have done the same. So if you're looking for sympathy look elsewhere.
-
I'm not sure if you're being sarcastic or really angry or what. I can't tell you to appreciate the work done here by volunteers, but I can say that if you really are upset at the change no one around here will miss you much if you leave, as we all appreciate the work done by :V: and Interplay to pay for their game, and then to spend countless hours making it prettier for those who have done the same. So if you're looking for sympathy look elsewhere.
I love people who cannot recognize sarcasm without the use of silly emoticons. I jest, I jest. But I cannot praise you without actually seeing your work. And as many others in this community, FreeSpace was a milestone in my childhood. I have very fond memories of me and my friends batteling for the rights of the joystick, getting out of control and crashing smack-down into the side of a capital ship. '**** was awesome.
-
It's hard to detect sarcasm without the associated vocal tones or facial expressions, that's kind of the point of emoticons. Not everyone reads what you write the same way it sounds in your head, no fault of theirs. Just something you have to account for. And if you read some of the threads around here, you'd understand why it was difficult to tell if that was sarcasm, because I guarantee you people have made similar statements and been dead serious. But yeah, I'm very fond of it too, I played the FS1 demo that came on the PC Gamer disc way back in the day. Instantly hooked.
-
http://www.hard-light.net/forums/index.php/topic,47640.0.html
http://www.hard-light.net/forums/index.php/topic,56279.0.html
Your OpenGL error means that your graphics card drivers are too old and/or you haven't installed proper chipset drivers.
-
http://www.hard-light.net/forums/index.php/topic,47640.0.html
http://www.hard-light.net/forums/index.php/topic,56279.0.html
Your OpenGL error means that your graphics card drivers are too old and/or you haven't installed proper chipset drivers.
Or it's because the game was not included by the installer.
-
No. Not having the game gives a "Web cursor bitmap not found" error. But obviously you are not getting long enough to experience it because of driver issues.
-
No. Not having the game gives a "Web cursor bitmap not found" error. But obviously you are not getting long enough to experience it because of driver issues.
Alright. Well, I did install the latest drivers from Nvidia, and that didn't solve the issue earlier. And just to be sure, I tried to run it again just now, and I got this error:
Error: Unable to initialize display device!
File:J:\src\cvs\fs2_open_3_6_9.final\code\graphics\gropengl.cpp
Line: 4658
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
This error has not been there earlier.
Another symtpom I have failed to mention is that when I do try to run it, the process continues to run, forcing me to end it in Task Manager.
-
Alright, I've gotten the retail game from GOG.com. Now what? Uninstall the Source and install it in the GOG.com download folder or..? Because that's going to suck. Really bad. Because it takes hours to reinstall it.
-
And waste precious bandwidth. No. Don't remove anything. Just stick the FSO stuff and your GOG FS2 to the same folder.
Edit: ... and you said you've acquired the latest graphics drivers. What about the chipset drivers? They were also mentioned.
-
And waste precious bandwidth. No. Don't remove anything. Just stick the FSO stuff and your GOG FS2 to the same folder.
Edit: ... and you said you've acquired the latest graphics drivers. What about the chipset drivers? They were also mentioned.
Having trouble finding MSI's latest drivers. There's nothing listed on their homepage. I'm using the http://www.msicomputer.com/product/p_spec.asp?model=K9A2GM-FIH&class=mb Motherboard, or a very close relative to it. Anyone else more adept at searching for chipset drivers? I'd love the help.
-
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.
-
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.
-
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!.
-
i had a problem a little like this .......
go here http://www.realtech-vr.com/glview/ (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 (http://www.hard-light.net/forums/index.php/topic,57370.msg1157682.html#msg1157682)
-
i had a problem a little like this .......
go here http://www.realtech-vr.com/glview/ (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 (http://www.hard-light.net/forums/index.php/topic,57370.msg1157682.html#msg1157682)
Yeah, no, that didn't help.
-
its not a fix , its just to see if your missing open gl extensions , which i was ...
-
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.
-
Does retail work? Try running Freespace 2 without FSOpen.
-
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.]
-
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....
-
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.
-
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.
-
With 3.6.9 and Direct3D it definitely shouldn't give the same OpenGL error.
-
*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.
<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. :nervous:
-
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.
-
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......
-
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.
-
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.
-
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
-
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.
-
The short summary of the excerpt Herra posted is try adding this in your registry:
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.)
-
New error whilst playing the FSO-FS 1 campaign:
Could you run a debug build (an FSO .exe with the filename ending in "-d" or "-debug"). It'll generate a file called fs2_open.log in your \freespace2\data\ folder, which you must post here, preferrably as an attachment or by copypasting the contents using the forums' "code" tags.
I'll get back on trying to fix this tomorrow. But goddamnit, there's barely good news.
Calm down, mon. At least the big issue seems to have vanished.
-
The short summary of the excerpt Herra posted is try adding this in your registry:
Windows Registry Editor 5.0
[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.)
Okay, followed your instructions, but where am I supposed to put it? I've never tampered with registries before. And on my own intuition, I put it in the main Freespace folder, garnering me the error message: Cannot import C:\Program Files\GoG.com\FreeSpace 2\riva.reg: The specified file is not a registry script. You can only import binary registry files from within the registry editor.
I'm aware that it's a hassle to guide others step-by-step, but I greatly appreciate it.
And Lobo, the error didn't occur again. It now runs smoothly. In D3D, that is. Still cannot run it in OpenGL.
-
You would simply doubleclick the registry file to add it, it would prompt you if you want to add it to the registry, or to cancel. It does not need to be in any particular folder to run it, I would just leave it on your desktop or something, and take it out of your FS2 folder.
-
You would simply doubleclick the registry file to add it, it would prompt you if you want to add it to the registry, or to cancel. It does not need to be in any particular folder to run it, I would just leave it on your desktop or something, and take it out of your FS2 folder.
I get the same error;
Cannot import C:\Program Files\GoG.com\FreeSpace 2\riva.reg: The specified file is not a registry script. You can only import binary registry files from within the registry editor.
-
Re: As far as I can tell; Unusual bug/error.
« Reply #40 on: December 13, 2008, 11:36:23 AM » Quote
Quote from: Fjellsveis on December 13, 2008, 12:25:43 AM
New error whilst playing the FSO-FS 1 campaign:
Could you run a debug build (an FSO .exe with the filename ending in "-d" or "-debug"). It'll generate a file called fs2_open.log in your \freespace2\data\ folder, which you must post here, preferrably as an attachment or by copypasting the contents using the forums' "code" tags.
and please can you post your open gl settings using the application i left link for earlier in the topic
this problem is sounding more and more familiar....... groundhog day
-
**** sticks.
Put in the word "Editor" between Registry and 5.00
Or, go back to my post, I have corrected it.
I actually exported mine and pasted it rather than typing it in from memory.
-
Does it matter that he's running it out of C/Program Files/whatever, instead of C/Games?
For some reason I thought it was important to have FSOpen under C/Games.
-
Does it matter that he's running it out of C/Program Files/whatever, instead of C/Games?
For some reason I thought it was important to have FSOpen under C/Games.
Well, don't have a choice whilst using GoG.com, which I was forced to.
Also, how can that possibly be a matter of importance?
And Zacam, it was as you corrected the first time. it still refuses to work.
-
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
This refuses to import when saved as riva.reg? What OS are you using?
All else fails, run regedit and manually do it.
What about the rest of my potential questions, any 3rd party desktop enhancements in place?
-
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
This refuses to import when saved as riva.reg? What OS are you using?
All else fails, run regedit and manually do it.
What about the rest of my potential questions, any 3rd party desktop enhancements in place?
That code did the trick, registry successfully altered. And no, no third party desktop enhancements. I'm using Windows XP Prof. - Somethingsomething-pack 2.
-
You mean Service Pack 2? :)
You may want to consider installing Service Pack 3 from their website or through Windows Update at some point. Helps out quite a bit.
-
That code did the trick, registry successfully altered. And no, no third party desktop enhancements. I'm using Windows XP Prof. - Somethingsomething-pack 2.
Okay, so now that the code is in, does it actually fix the problem?
-
That code did the trick, registry successfully altered. And no, no third party desktop enhancements. I'm using Windows XP Prof. - Somethingsomething-pack 2.
Okay, so now that the code is in, does it actually fix the problem?
No.
chief1983,
Hahahahahaha no.