[feltoar]

Hey everyone. Just discovered this game yesturday and it looks AMAZING. Just finished downloading it using the Windows FSO installer.

Ive got an issue when running the game in OpenGL (it doesnt do it in D3D). Basically this is what the tutorial looks like in OpenGL:



Sorry if this has already been answered. I didnt know what search terms to look for.

[FUBAR-BDHR]

Well it's been discussed but not really answered.  The discussion was around Forceware graphics drivers.   What OS and graphics card are you using?  Also try turning off the MediaVPs in the launcher and see if you still get it.  If it works without the MediaVPs try reinstalling them. 

[Jeff Vader]

Ive got an issue when running the game in OpenGL (it doesnt do it in D3D). Basically this is what the tutorial looks like in OpenGL:

Indeed has this issue popped up here before. Trying different sets of drivers might help. And, if at all possible, keep playing in OpenGL. Direct3D hurts more than it helps in FSO.

Sorry if this has already been answered. I didnt know what search terms to look for.

As surprising as it might seem, 'black and white stripes' would have been a functioning search term.

And,

[feltoar]

When I turn off mediavp (thats when you select No Mod in the Launcher right?) the ships appear normal even in OpenGL. How do I reinstall mediavp with the FSO Installer?

Im running a 7900GS with Forceware 169.21. Running Windows XP SP2 and 2GB RAM.

EDIT: I might add its only happening to some ships, not others.

[karajorma]

To turn them on again simply click the Select Mod button and select the mediavps folder. The set of drivers before 169.21 should be fine actually. It's just the last 2 or 3 releases that have had problems.

[feltoar]

I had an old BETA set, 169.09 I think. I updated today because I thought it might be because the drivers were betas. Please let me know what version works before I go ahead and do it though.

[ARSPR]

To turn them on again simply click the Select Mod button and select the mediavps folder. The set of drivers before 169.21 should be fine actually. It's just the last 2 or 3 releases that have had problems.

NOPE, all 169.xx seems to have troubles.

AND since 169.21, if you have a new fsopen build (GLSL capable), it will render fine.

With your card (a 7xxx series) 163.75 will run completly fine (but if you play Crysis, your performace will drop).

Nevertheless, please continue reporting info in this thread which concentrates the trouble: http://www.hard-light.net/forums/index.php/topic,50345.0.html

[feltoar]

[whole post edited]
Cheers ARSPR, I swapped to fs2_open_3_6_10-20071028T.exe and it is half fixed.

Ships in direct view now appear properly, but the ships in the target box in lower left corner are still messed up. Will that be fixed by updating the mVPs to 3.6.10 using these files? http://www.hard-light.net/forums/index.php/topic,51229.0.html

Reason I ask is I left this thing running all night last night to get the game, dont feel like downloading half of it again unless I know itll fix it.

[edit 2]I came back and edited my post because I found where to get it. Then replied while I was doing so. Thanks again anyway!

[ARSPR]

The 2007-10-28 build: http://www.hard-light.net/forums/index.php/topic,50258.0.html

(There are other newer, the latest is Taylor's XT1207 but unless you know where and how to get them, you should keep sticked to "public" builds).

[ARSPR]

[whole post edited]
Ships in direct view now appear properly, but the ships in the target box in lower left corner are still messed up. Will that be fixed by updating the mVPs to 3.6.10 using these files? http://www.hard-light.net/forums/index.php/topic,51229.0.html

Reason I ask is I left this thing running all night last night to get the game, dont feel like downloading half of it again unless I know itll fix it.

The problem is that nobody knows what happens, why this ForceWare series are defective. Or even if they are just more restrictive in some way and FSOpen is having trouble with them because of that.

Some models/textures are messed up and others not. IIRC, in my system 3.6.10 has less render fails than 3.6.8. but this is not a media vps issue.

[Zacam]

What's funny is that some of the drivers in the 169.xx series actually manage to break crysis and in bad ways.

Which is funny when you figure it was released to boost crysis performance and to flagship the new GT card.

Even funnier when fewer people actually see a boost in crysis between 169.xx and 163.75.

Find whatever works for you for everything you play and _read the release notes_ before upgrading. If there are no release notes, then my suggestion is to not bother with them.

There is no fixing perfection.

[Terashell]

I figured rather than start a new topic for the same problem with a different system... I figured I'd just resurrect this one.

I'm running a GeForce 7900GS (driver version 6.14.11.6909) , fresh install using Turey's with every option selected, all graphics options enabled, and I'm still getting this problem on cargo containers and capital ships, and some fighters.  It really takes the joy out of the game when half the vessels are zebra-striped.

[feltoar]

Try the new 3.6.10 beta media vps and the 3.6.10 beta executables. I havent noticed since.

[Terashell]

Try the new 3.6.10 beta media vps and the 3.6.10 beta executables. I havent noticed since.

Thanks, that seems to have fixed it.  I tested it in the mission that I gave up on (Small Deadly Space) where the freighters and containers were borked, and they're fine now.

[McCall]

Having experienced this problem with my nVidia GeForce 7600GT on the newest driver, I've found there are two ways to get around it. Using the 3.6.10 build reduces it, but doesn't eliminate.

I fixed mine completely (fingers crossed) by rolling back to the "162.65_quadro_winxp2k_english_whql" driver. It's one of the archived XP/2K drivers that you can access through the link on the left of the latest driver download page.

[castor]

Maybe we need a lookup table, to sort out this issue for once and all..

Code: [Select]

FSO 3.6.9 + MVP 3.6.8Z + old NV driver = good
FSO 3.6.9 + MVP 3.6.8Z + new NV driver = bad
FSO 3.6.9 + MVP 3.6.8Z + old NV driver = good
FSO 3.6.9 + MVP 3.6.8Z + new NV driver = bad
FSO 3.6.9 + MVP 3.6.10 + old NV driver
FSO 3.6.9 + MVP 3.6.10 + new NV driver
FSO 3.6.9 + MVP 3.6.10 + old NV driver
FSO 3.6.9 + MVP 3.6.10 + new NV driver
FSO 3.6.10 + MVP 3.6.8Z + old NV driver
FSO 3.6.10 + MVP 3.6.8Z + new NV driver
FSO 3.6.10 + MVP 3.6.8Z + old NV driver
FSO 3.6.10 + MVP 3.6.8Z + new NV driver
FSO 3.6.10 + MVP 3.6.10 + old NV driver
FSO 3.6.10 + MVP 3.6.10 + new NV driver
FSO 3.6.10 + MVP 3.6.10 + old NV driver
FSO 3.6.10 + MVP 3.6.10 + new NV driver

Feel free to fill in the rest

[taylor]

Maybe we need a lookup table, to sort out this issue for once and all..

Not needed really, it's confirmed as a NVIDIA driver bug.  It affects other games well but it hits us pretty hard since it's data related, and we make heavy use of that sort of data ("that sort" being DXT compressed DDS images).  It is supposed to be fixed in newer drivers though (the 17x.xx series).