[SC4RY_Z0MB13]

I recently bought Freespace 1 and 2 on GoG and have only started playing Freespace 2 Open and I noticed that all ships and objects in-game are textured black and red in my installation of Freespace 2 Open. I ran FS2 and FSPort in the Launcher and the same problem happened with both of them.

I used the java installer to install The Works.

My System is as follows:
64-bit Windows 7
Intel Core 2 Quad CPU Q8200 @ 2.33 GHz
4.00 GB of DDR2 1200 RAM
ATI HD4650 DDR2 1GB

I followed the guide here http://www.hard-light.net/wiki/index.php/Installing_fs2_open very well.

Any help would be appreciated.

[Galemp]

OH GOD, THE SHIVANS HAVE WON!

...

So does this happen on FS2 Retail as well? And maybe you could post a screenshot, that would help us track down the problem.

[SC4RY_Z0MB13]

Here is an image of what is going on.

http://i776.photobucket.com/albums/yy49/SC4RY_Z0MB13/fs2_open_3_6_102010-06-2200-45-50-7.jpg

[Jeff Vader]

Sorta looks like there's a red sun in the mission, but I don't remember there being one in that mission. Curious.

Another thing that might help would be your fs2_open.log. Follow the "Your fs2_open.log" instructions as described here. And remember one of the most important steps: deliver the fs2_open.log to us! Some people seem to think it is an insignificant step, but it is not.

[SC4RY_Z0MB13]

I attached the logs for running FSPort and FS2.

[attachment deleted by admin]

[FUBAR-BDHR]

Wasn't there a bug like this reported ages ago that was driver/card related?  Kind of like the 1600 series one?   If so then a driver update may be the answer.  If not then there may be an existing solution that has been long forgotten.  

On second thought I'm going with a driver issue:

Compiling shader ->  null-v.sdr / null-f.sdr ...
  Shader in_error!  Disabling GLSL!

If updating the drivers doesn't work try disabling GLSL

[SC4RY_Z0MB13]

I've updated drivers and ran without glsl.

Unfortunately it did not fix the textures and I have attached the new log.

[attachment deleted by admin]

[FUBAR-BDHR]

OK I'm grasping as straws here.  Try disabling normal map first.  That doesn't work disable MediaVPs if you have them enabled (close the dang log before I looked).  Either way set to FS2 defaults (all features off) in the launcher and see if you get the same problem.  We can work from there on what might be causing it

[SC4RY_Z0MB13]

Ran with Normal Maps unchecked and have attached that log.

Ran default FS2 in Launcher and problem persists and have attached that log as well.

[attachment deleted by admin]

[FUBAR-BDHR]

Well I'm a bit too tired to help at the moment but all that info should help as soon as our resident Sith Lords wake up. 

[Galemp]

This may sound crazy, but... try a different mission. Like one of the standalone missions in the tech room.

That first mission is in Betelgeuse, with a large red sun. If you don't have any glowmaps, and the ambient is turned way down, it could actually look like that.

[Jeff Vader]

as soon as our resident Sith Lords wake up. 

I just run the Death Star.

Code: [Select]

  -spec_exp 11
  -ogl_spec 80
  -spec_static 0.8
  -spec_point 0.6
  -spec_tube 0.4
  -ambient_factor 0
  -no_emissive_light
You seem to have these in your "Custom flags" field. I can't begin to understand how they could be responsible for this kind of behaviour, but just for kicks, try removing them. Copy them into a safe location (a .txt file, for example), if you want to keep them safe.

That first mission is in Betelgeuse, with a large red sun.

My memory failed me, it seems.

[FUBAR-BDHR]

I just run the Death Star.

Yea and I'm still waiting on that reactor to be build on the detention level.  How do you expect me to keep my beer cold up there while interrogating the hot female prisoners? 

Anyway with all features off shouldn't that kill those flags?

[Jeff Vader]

Anyway with all features off shouldn't that kill those flags?

Oh, right. Yes, I checked the Wiki page and at least any flag beginning with "-spec_" requires -spec in order to do anything.

[Galemp]

Nope, lighting settings are command-line only and not in the launcher. The options  -ambient_factor 0 and -no_emissive_light, with no glowmaps, and a big red sun, would give you exactly that effect.

[The E]

On second thought I'm going with a driver issue:

Compiling shader ->  null-v.sdr / null-f.sdr ...
  Shader in_error!  Disabling GLSL!

If updating the drivers doesn't work try disabling GLSL

That would be wrong. No mediavps == No shaders == Error when trying to compile them.

On that note, how do the missions look with mediavps enabled?

[SC4RY_Z0MB13]

I selected mediavps from the Launcher in the mod tab and the ships were no longer textured red.

I must admit my jaw dropped when I saw Freespace 2 playing with mediavps.  I had assumed that Freespace 2 Open would use mediavps automatically since you can only mount one mod at a time.

For example FSport has its own mediavps but I can't run them and fsport in the launcher.

Thanks The E, Galemp, Jeff Vader, FUBAR-BDHR for getting me this far!

[attachment deleted by admin]

[The E]

That's what mod.inis are for.

Also note that to get the upgraded graphics for the fsport, you will have to select the "fsport mediavps" mod. That'll increase your enjoyment somewhat.

Longer explanation: While you can select only one mod in the Launcher, mod creators can use a little file called mod.ini to tell the Launcher what other mods to load as well, most mods use this to load up the mediavps in addition to their own data.

Some mods, like the fsport, are built to bypass the mediavps however.

[Jeff Vader]

http://www.hard-light.net/wiki/index.php/Mod.ini

[SC4RY_Z0MB13]

I feel bad for not realizing that I was supposed to modify the mod.ini (or use fsport - mediavps since it has the secondary mod as fsport) to get the best results.

I had no idea...

Thanks for all the help!