Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: heftig on November 26, 2007, 12:45:51 pm

Title: mediavps: textures broken
Post by: heftig on November 26, 2007, 12:45:51 pm
I first installed FSO on a laptop with a Radeon Mobility X700 graphics card. It ran perfectly fine there.

Now, I copied it to a desktop with an NVIDIA 8800GTX. When using the mediavps mod, the textures of most ships are not mapped correctly. This apparently only happens to the base texture, since the glow/specular/envmap textures are mapped correctly.

It looks horrible. Any way to fix this?
Title: Re: mediavps: textures broken
Post by: karajorma on November 26, 2007, 01:41:18 pm
Do you have jpg and tga textures turned on from the launcher's feature tab?
Title: Re: mediavps: textures broken
Post by: heftig on November 26, 2007, 02:14:38 pm
Yep, it's on. I tried a lot of settings.

I tried versions 3.6.9, 3.6.10-20071007T, 3.6.10-20071028T, and a build from 2007-11-23. They all show the same problem.
Title: Re: mediavps: textures broken
Post by: ARSPR on November 26, 2007, 02:16:12 pm
I first installed FSO on a laptop with a Radeon Mobility X700 graphics card. It ran perfectly fine there.

Now, I copied it to a desktop with an NVIDIA 8800GTX. When using the mediavps mod, the textures of most ships are not mapped correctly. This apparently only happens to the base texture, since the glow/specular/envmap textures are mapped correctly.

It looks horrible. Any way to fix this?
A fast guess. You are using 169.xx ForceWare version. These drivers are defective. Move down to official 163.75 (and suffer a slower Crysis BTW).

Check if your ships look like the ones in this thread (http://www.hard-light.net/forums/index.php/topic,50345.0.html)


OOPS. I'm being rude

3,

2,

1,

:welcome:
Title: Re: mediavps: textures broken
Post by: heftig on November 26, 2007, 11:31:21 pm
I'm indeed using a 169 Forceware. I guess your guess is right. :) Thanks.

I'll downgrade my drivers ASAP.

edit: Downgrading to 163.75 fixed it. :yes: