Don't set forest=3
#1

Well, at least don't do that if you have nVidia GeForce 7950GT with 96.89 x64 driver on a 64bit WinXP system.
Do your own experiments and find out what's best for you but don't assume that a higher setting = better rendering.: sometimes it's the exact opposite.

I had always run with forest=3 because I assumed that =3 would be better than =2. Turns out that using forest=3 some trees are not rendered AT ALL (!). I learned about this when I lowered the setting to =2 during a series of experiments to aimed at finding the best quality/performance compromise for my system.






These screenies are from the campaign "Weisse Schwalbe & the Galland circus", mission #11.
Here's how it looks like at take off with forest=3




forest=3
[Image: 2295416427_4e08b45bea_o.jpg]

forest=3
[Image: 2295416429_6ed14e6ec9_o.jpg]

forest=3
[Image: 2295416425_e0c68a4aeb_o.jpg]

forest=3
[Image: 2295416423_bf26872909_o.jpg]







...and this, believe it or not, is how that very same mission looks like with forest=2



forest=2
[Image: 2295415569_3368ded431_o.jpg]

forest=2
[Image: 2295415575_879296c9c6_o.jpg]

forest=2
[Image: 2295415573_520b95bd56_o.jpg]

forest=2
[Image: 2295415565_301f9ab13d_o.jpg]
Reply
#2

Seems to me that is a long standing issue with just a couple types of trees.
Reply
#3

it could just be too much for your driver.
Reply
#4

I'm now running with all those settings to =0 (see THIS thread)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)