[Zacam]

Did a clean install of XP with 169.21. Ran Tureys installer. So, everything clean.

Grabbed latest XT build. Only four ships are screwed-ish up. (This is with normal mapping enabled, but with the nm_test.vp not yet installed):

Herc Mark II
Myrmidon
Serapis
Aten

All four show funcky-fresh texturing even under default settings. Might the problem with the texture more be a fault of models and not necessarily the engine or drivers? Granted, driver revisions always break something, but what if it broke something by fixing something nobody ever knew was broken in the first place?

I've ran both the 169.21 Beta and WHQL with the exact same results. Other than the texturing, it all looks and runs perfectly.

[diceman111]

I posted in this thread before but ARSPR wanted me to post here instead, I also get the checkerd ships and I use the new 169.25 Official drivers for Vista 32-bit.
Still dosent seem to work, and by the way the "no_glsl" flag you simply input as "no_glsl" in the custom flag field in the launcher right????

[ARSPR]

I posted in this thread before but ARSPR wanted me to post here instead, I also get the checkerd ships and I use the new 169.25 Official drivers for Vista 32-bit.
Still dosent seem to work, and by the way the "no_glsl" flag you simply input as "no_glsl" in the custom flag field in the launcher right????

Several comments:

• GLSL (shaders) rendering is only present in newest beta builds. As example this one, although it's a bit old and it's not really going to become 3.6.10. Official 3.6.9. doesn't have GLSL so it isn't going to run fine, (it's like disabling GLSL in newest builds).
• 169.21 and 169.25 should work fine with a GLSL capable build and GPU. Or at least you will be the very first one with troubles...
• All the flags are typed with a - before. So it's -no_glsl, not no_glsl. Instead of typing it you can tick it in Troubleshot flag group IIRC. Something like "Disable GLSL". (I'm not in my PC so I don't have FSOpen available right now). BUT you always need a GLSL capable build in order to disable it  . GLSL >> it should render fine; no GLSL >> chess board, (or maybe zebra stripes), effect.

[diceman111]

Ok fixed it with the new build everything seems to work now so thank you. maybe you should make an anouncement or a sticky or something it seems to me that this is something that of people will ask about.

[Nx]

Did a clean install of XP with 169.21. Ran Tureys installer. So, everything clean.

Grabbed latest XT build. Only four ships are screwed-ish up. (This is with normal mapping enabled, but with the nm_test.vp not yet installed):

Herc Mark II
Myrmidon
Serapis
Aten

All four show funcky-fresh texturing even under default settings. Might the problem with the texture more be a fault of models and not necessarily the engine or drivers? Granted, driver revisions always break something, but what if it broke something by fixing something nobody ever knew was broken in the first place?

I've ran both the 169.21 Beta and WHQL with the exact same results. Other than the texturing, it all looks and runs perfectly.

For me, the Herc 2 is fine except in the targeting box. (169.25 and 3.6.10-20071028 on Vista64 and 8800gt)

[attachment deleted by ninja]

[ARSPR]

For me, the Herc 2 is fine except in the targeting box. (169.25 and 3.6.10-20071028 on Vista64 and 8800gt)

Although it's a resource waste, try forcing LOD0 in target window (by default LOD1 is used).

Use the next WhatEverNameYouWant-shp.tbm file placed in MediaVPS\data\tables folder:

Code: [Select]

#Ship Classes

$Name: GTF Hercules Mark II
+nocreate
$POF target LOD: 0

#End

Nevertheless, I get good rendering even in target window  (Vista 32 bit + 8800 GTX + 169.25)

EDITED ------

OTOH your screen is distorted because FS2 is designed to work with a 4:3 resolution aspect ratio. I also have a 1680x1050 monitor but I use:

• Standard 1280 x 960.
  
  OR
  
  
• I've enabled a custom 1400 x 1050 x 32 bit x 60 Hz through RivaTuner utility >> Custom display modes / refresh rate wizard.

[Nx]

For me, the Herc 2 is fine except in the targeting box. (169.25 and 3.6.10-20071028 on Vista64 and 8800gt)

Although it's a resource waste, try forcing LOD0 in target window (by default LOD1 is used).

Use the next WhatEverNameYouWant-shp.tbm file placed in MediaVPS\data\tables folder:

Code: [Select]

#Ship Classes

$Name: GTF Hercules Mark II
+nocreate
$POF target LOD: 0

#End

Nevertheless, I get good rendering even in target window  (Vista 32 bit + 8800 GTX + 169.25)

That fixes it. But if I set detail to low, none of the lods in the main view look bad.

Wait a second... I deleted the tbm file and now it's fixed... 

Ok, I figured it out: I start the mission, Herc2 in targeting box has zebra textures. I set model detail to 3 "lights" (4 and 5 have the zebra textures), and it's ok. I set it back to 5 lights, and it's still fine... And I don't see any change in the targeting box model

EDIT: yeah, i know about the distortion. Doesn't bother me now, since I don't play, just test. Widescreen has a bug though, the targeting boxes and all that stuff is incorrectly placed

EDIT2: I took that with 1680x1050, there shouldn't be any distortion there

[ARSPR]

ForceWare mysteries...

I've got all my detail settings at maximum.



Nx, in case you haven't read it, please check my edited former post comments about your resolution.

Ah, and remember to set your ForceWare settings so NO SCALING is applied when displaying a resolution smaller than your LCD capabilities.

[Nx]

ForceWare mysteries...

I've got all my detail settings at maximum.



Nx, in case you haven't read it, please check my edited former post comments about your resolution.

Ah, and remember to set your ForceWare settings so NO SCALING is applied when displaying a resolution smaller than your LCD capabilities.

Try setting them to minimum, going back to the game, then back to maximum. That's what fixes it form me

[pecenipicek]

this also happens on Linux, with official 169.07 drivers.


crap on a crutch

[ARSPR]

nVidia has launched 169.28 beta which at least in Vista:

• runs fine in GLSL
• doesn't run fine with -no_glsl
• still miss a lot of resolutions. I'm using RivaTuner to enable useful resolutions as example standard 1280x960 and custom 1400x1050 so this issue doesn't bother me any more.

Till now, nothing new.


But now, the important part of this post starts. 

I've discovered that I can get the models to render fine WITH NO GLSL at least in F3 Lab. Maybe this can be a clue to detect what the hell happens. I'm using XT1207 + shaders from sdr1119.vp + Mediavps 3.6.8. zeta.

• Run the game in GLSL (default, no flag needed). Go to F3 Lab. Tick Render Options > Fixed Render Pipeline (ie. no shaders).
• Then open any model. As example Ulysses LOD 0. I get the expected messed up textures. (See attached 01-Fixed Pipeline is ticked before selecting.jpg)
• Then untick Fixed Render Pipeline. Shaders, and then normal & parallax, are enabled and you get the new and pretty looking. (See attached 02-Fixed Pipeline is unticked - GLSL.jpg)
• Then tick AGAIN Fixed Render Pipeline. Shaders are disabled, but the model looks fine with no messed textures. (See attached 03-Fixed Pipeline is ticked AGAIN.jpg)
• This happens with every new model you load. If Fixed Render Pipeline is selected BEFORE you load that model, the textures are FUBAR. But if you load the model with enabled shaders, and then you disable them, the model is rendered fine.

I hope this info can be useful ...

Can anyone confirm this behaviour? (Remember that used shaders need a SM 3.0 capable GPU - so 6xxx or above)

[attachment deleted by ninja]

[feltoar]

According to ARSPR Ive had a related issue.

Running both Forceware 169.21 & 169.03 and fs2_open_3_6_9.exe I got this:


The newer build slightly fixed it.

Running 169.21 and either fs2_open_3_6_10-20071028T.exe or fs2_open_3_6_10-20071007T.exe I get something similar. The ship in the middle will now appear 100% correctly (all of them do), but the same ship in the lower left corner where it shows your target still suffers the same bug as before (but not all of them). Iy only happens on the ships which are well lit.

[edit]My bad, in that particular picture both ships are fixed. However the results I explained can still be seen in many other missions, for eg A Lion at the Door.[/edit]

I guess what ever was done to normal ships between those 2 versions needs to happen for target view ships? I have no idea.

Running a 7900GS, AMD 64 X2 4600+ on Windows XP Pro SP2. Want more info/testing, just ask.

Just want to add, everyone involved in updating FS2 does an excellent job. Ive never seen community support for a game like this before.

[Zacam]

Hmm. I've just gone back and done a clone of a fresh install on three machines. All of the eVGA cards. 8800 GTS 640, 8800 GT and 7600 GTS. Using every foreceware driver since 163.44 to current beta, I can no longer reproduce this issue under 3.6.9 or 3.6.10 provided by Turey's installer (that I cloned to the other machines) or the 1207 XT Build.

Buh? Now _I'm_ confused....and yes, I know these were clean installs of the driver, I used a clean install of the OS.

The only thing I can think of is how I'm doing the OS. Each install is actually being installed and run from a USB Stick with the forceware drivers directly integrated into the install source. (Meaning that the nVidia drivers are installed during the "Setup will complete in 39 Minutes" portion where it's installing new hardware.)

Very curious.

[castor]

Are you using the 3.6.8 Z Media VPs? They're the only ones causing trouble for me, retail and 3.6.10b work fine.

[ARSPR]

Yeap, the render troubles are dependant on the exact model and texture.

Mediavps 3.6.10beta seem to work better than 3.6.8. (there's a completely new set of textures and models), but you can still find some issues.

EDITED ----

As example Herc II is FUBAR in my system

[castor]

Hmm.. maybe we should take a closer look at the H2 maps, to try and see if we can find the critical factor, so to speak.

[ARSPR]

I've just tested nvidia 169.44

And as far as I've seen there's nothing new. -no_glsl still doesn't render fine.

[MC_Kejml]

Well, as for my SCP builds, I've been getting strange errors lately.
I was playing some modded campaigns, when the scp freezes and crashes.. then it happened in the mission room, and now i can't even 'log' with the pilot.. Previously I had some errors about low virtual momery, but I made the page fiole bigger so it's ok now..This happened in 369 and 3610, I couldn't get any logs out of debug. I have the error.log file though, if it helps.

Any ideas ?

EDIT: Got the debug file now, it's here.

[attachment deleted by ninja]

[Davros]

quick question why would you want to use no gsl ?

[Zacam]

ARSPR: What video card do you have again? I've noticed that just about any 7xxx card (with few exceptions) are having issues with the 169.xx series drivers.

If you have an 8xxx series card, find a version set 171.17. They are WHQL for XP and have been doing phenomenally for me.

I've given up on Crysis "optimized" drivers. Love the game and the patches, but I always come back to the 171.17 (once they released, previously I just stuck with the 163.75). Also, Omega is back on the scene for nVidia drivers, but I cannot recommend them. I had edge blurring and "broadcast" distortion when ever ANY method of anti-aliasing was applied, (with and without Gamma and no matter what transparency option) but other people may have different results.