[feanor]

I installed Freespace 2 and then the 1.20 patch. I ran FreeSpaceOpenInstaller and chose

FreeSpace Open 3.6.9 executables
3.6.8 Zeta MediaVPs with 710 Patches
3.6.8 Zeta Advanced MediaVPs with 710 Patches

It installed successfully and I ran the launcher.

With the commandline

C:\Games\FreeSpace2\fs2_open_3_6_9.exe -mod mediavps

no ships are textured.

My system:
C2D E6600
2GB RAM
7950GT 512MB with Forceware 169.12
Vista x64

Any ideas?

[Jeff Vader]

OpenGL.

[feanor]

OpenGL.

Using it.

[ARSPR]

Use -jpgtga flag. The problem is that, till 3.6.9. (included), jpg and tga bitmaps are not used by default and lots of ships in mediavps use this kind of textures. Current beta testing builds use them by default, (-jpgtga has indeed been removed), and future mediavps release textures will be dds formated.

OTOH you should enable a lot of extra features (launcher flags or ticks). I post my launcher flags (apart from -mod whatever). Remember that a lot of them can be ticked in Launcher, (you don't need to type them):

Code: [Select]

-spec -glow -env -noscalevid -missile_lighting -no_vsync -cache_bitmaps -dualscanlines -targetinfo -rearm_timer -ballistic_gauge -ship_choice_3d -3dwarp -warp_flash -fps -window -ambient_factor 60 -no_emissive_light

Read about them here in Wiki

OTOH there are known issues with ForceWare 169.xx series. Read at least this thread and please confirm if you replicate the same issues in your system (I get them with C2Q Q6600 + 8800 GTX + Vista 32 bit). The only known solution is reverting back to 163.75 and waiting for a GOOD official nVidia release.



And the most important thing:

[Jeff Vader]

That too. You might want to take a look at the Features tab in the Launcher and try punching things on, especially from the Graphics section. Also, that Wiki page is useful too. You might want to tinker around with all those spec flags to get better looking lighting in the game.

[feanor]

Use -jpgtga flag. The problem is that, till 3.6.9. (included), jpg and tga bitmaps are not used by default and lots of ships in mediavps use this kind of textures. Current beta testing builds use them by default, (-jpgtga has indeed been removed), and future mediavps release textures will be dds formated.

I already tried that. No difference.

OTOH you should enable a lot of extra features (launcher flags or ticks). I post my launcher flags (apart from -mod whatever). Remember that a lot of them can be ticked in Launcher, (you don't need to type them):

Code: [Select]

-spec -glow -env -noscalevid -missile_lighting -no_vsync -cache_bitmaps -dualscanlines -targetinfo -rearm_timer -ballistic_gauge -ship_choice_3d -3dwarp -warp_flash -fps -window -ambient_factor 60 -no_emissive_light

Read about them here in Wiki

I did enable a bunch of stuff at first, but disabled everything for troubleshooting. I left vsync on because if I disable it, the game becomes unplayably slow.

OTOH there are known issues with ForceWare 169.xx series. Read at least this thread and please confirm if you replicate the same issues in your system (I get them with C2Q Q6600 + 8800 GTX + Vista 32 bit). The only known solution is reverting back to 163.75 and waiting for a GOOD official nVidia release.

Unfortunately other games (e.g. Crysis, even though it's barely playable on my system) need the newer drivers.

And the most important thing:

Thanks

[feanor]

I did some more testing. The models don't look like the ones in the thread you linked:


The Hercules, Ursa, Triton, Fenris, Leviathan, Argo (partial), Alastor, Nephthys, Bes, Vac 5, and Edjo are textured. None of the other ships that I can see at the beginning of the campaign are. Is there something that those have that others don't?


Ok, texturing works under Direct3D. However, the main screen and parts of the HUD are distorted...as though poorly resampled and heavily lossily compressed.

[colecampbell666]

D3D is broken, never to return.

[ARSPR]

OTOH there are known issues with ForceWare 169.xx series. Read at least this thread and please confirm if you replicate the same issues in your system (I get them with C2Q Q6600 + 8800 GTX + Vista 32 bit). The only known solution is reverting back to 163.75 and waiting for a GOOD official nVidia release.

Unfortunately other games (e.g. Crysis, even though it's barely playable on my system) need the newer drivers.

Nevertheless, please test with 163.75. It really seems that OGL support in 169.xx is FUBAR. If it works with 163.75, you can blame nvidia. If not, we have some strange issue here.

Crysis works with 163.75 although about 10% slower  . If your troubles are gone with 163.75 then, at least, you know which driver to install for each game.

OTOH, NEVER use D3D. Its support is lost and there can be a lot of glitches. You're alone if using D3D. (Future builds maybe won't have D3D available at all).

[BlackDove]

Hahahahaha, it's the Uly from PRISON.

[castor]

Ph34rrr!!

[Turambar]

JESUS CHRIST ITS A LION!

GET IN THE HERMES!

[feanor]

OTOH there are known issues with ForceWare 169.xx series. Read at least this thread and please confirm if you replicate the same issues in your system (I get them with C2Q Q6600 + 8800 GTX + Vista 32 bit). The only known solution is reverting back to 163.75 and waiting for a GOOD official nVidia release.

Unfortunately other games (e.g. Crysis, even though it's barely playable on my system) need the newer drivers.

Nevertheless, please test with 163.75. It really seems that OGL support in 169.xx is FUBAR. If it works with 163.75, you can blame nvidia. If not, we have some strange issue here.

Ok, I downgraded. All models are now textured in OpenGL. I never thought FreeSpace 2 could be so beautiful.

Does the SCP plan to support nVidia drivers > 163.75 or will nVidia make changes in the (170?) drivers for an open source project?

[ARSPR]

Ok, I downgraded. All models are now textured in OpenGL. I never thought FreeSpace 2 could be so beautiful.

Does the SCP plan to support nVidia drivers > 163.75 or will nVidia make changes in the (170?) drivers for an open source project?

I'm not a coder but I bet that something is broken in 169.xx OGL support (remember they are beta drivers and they're a special Crysis release). I suppose future releases will work fine. If not, SCP crew is going to have hard time trying to figure out what the hell happens with these drivers.

[ARSPR]

Feanor, nvidia has released a 169.21 driver. Please, test it and post your results in this thread

(Don't use this thread anymore since the issue was addressed in other one before. Let's keep it focused. If a forum moderator closes this thread it would be nice).