Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: darthvader420 on March 20, 2008, 02:54:01 pm
-
Hi everyone
I just used the FSOpen installer and I'm having some texture problems. When I'm using opengl, about half of the ships in game have corrupted textures (textures looks like static/random colours.) Everything works fine in D3D but I'm afraid I might be missing out on some of the graphics.
Running windows xp with a Geforce 7900 GTO (latest drivers) if that helps.
Anyone have any ideas?
Edit: I selected all of the media vps when I ran the installer
-
Enable jpg/tga textures.
Make sure that both the OS and the Launcher have 32bit colours selected.
-
I should have mentioned that I tried enabling jpg/tga textures and it made no difference. Everything is 32 bit colour.
-
Hmm. Well, keep it on. Otherwise you'll get partially invisible ships. But I suppose you might have a corrupt vp somewhere. Try to redownload the mediavps.
-
Thanks for the quick reply. I'll see if replacing the VPs works.
-
I replaced the media vps, same problems. Am I missing out on anything if I use D3D?
-
The cutscenes, for starters. And performance. And there are some graphical glitches. I had blurry warp effects. But, if OpenGL really doesn't work, there aren't that many choices.
-
By latest drivers: define? What version # is particularly helpful. Also: are they nVidia drivers or modified nVidia drivers?
GTO, if I recall, is a mobile gpu? If so, that would mean Laptop, so a make and model (or specifications) would help.
As well, if you could post the command line settings in the launcher, we won't have to keep guessing what you do or do not have enabled.
-
By latest drivers: define? What version # is particularly helpful. Also: are they nVidia drivers or modified nVidia drivers?
GTO, if I recall, is a mobile gpu? If so, that would mean Laptop, so a make and model (or specifications) would help.
As well, if you could post the command line settings in the launcher, we won't have to keep guessing what you do or do not have enabled.
The 7900 GTO is a 7900 GTX with underclocked memory. It's not a mobile card, just a cheaper but almost-as-good gtx. I've been using it for well over a year with no problems. The drivers are forceware 169.21, just updated them today. As for the command line, I've tried disabling all the graphics options and I get the same problems. I hope this info helps!
-
Short answer to your problems: You are seing ForceWare 169.xx OGL issues not FS2Open issues. :(
Long answer: Read this thread (http://www.hard-light.net/forums/index.php/topic,50345.0.html)
Solutions:
- Go back to 163.75. (Usually slower for Crysis)
- Latest 169.xx seems to work fine at least with glsl capable builds (ie. if you see normal mapping)
-
Short answer to your problems: You are seing ForceWare 169.xx OGL issues not FS2Open issues. :(
Long answer: Read this thread (http://www.hard-light.net/forums/index.php/topic,50345.0.html)
Solutions:
- Go back to 163.75. (Usually slower for Crysis)
- Latest 169.xx seems to work fine at least with glsl capable builds (ie. if you see normal mapping)
Well that explains it! Yeah, I don't care at all about playing crysis anymore, but the 163.75 drivers were also causing problems in COD4. And I thought nvidia used to make good drivers :o
Well, I still have the old forceware installer on my desktop so I might as well give that a try. Thanks.
Edit: Yup, opengl works with the old drivers
-
Grab the 171.17 XP WHQL (http://downloads.guru3d.com/ForceWare-171.17-WHQL-XP-(32-bit)-download-1848.html) drivers. They only work for 8xxx series cards and XP.
They have been holding rock solid for me on everything, including Crysis, COD4 3.6.9 and 3.6.10.
You may have performance issues under 3.6.9 with them, or that could just be my rig being quirky, but there are no rendering problems at all.