Does setting Mipbias in FSX (Acceleration) do anything or is it obsolete?

 

I'm trying to improve the texture resolution of 'mid distance' photo scenery. LOD_radius helps, but only to a point. (I've tried a variety of settings out to 8.5, currently using 7). Textures that seem to be well within the LOD_Radius are still loaded at a lower resolution and 'snap in' to the next level of detail as I get closer. I want this to happen further away from my viewpoint. I thought setting Mipbias would force higher resolution textures to load further out, but maybe I don't understand this tweak, or it no longer works?

 

Can someone set me straight one this? Is there another way to accomplish what I'm after?

 

here's what I tried in my fsx.cfg:

[DISPLAY.Device.NVIDIA GeForce GTX 680.0]

Mode=1920x1080x32

Anisotropic=1

AntiAlias=1

Mipbias=7

Hi Odourboy

 

This is a known issue called "popping" caused by a lack of z-buffering within the game. Nothing can be done about it (as far as im aware) as its part of the fsx code, so mipbias will not help. The only thing ive tried that seems to reduce this "popping" effect is to run autogen density at normal. Ultimately it's just a case of having to put up with it I'm afraid.

 

Im running the gtx 680 aswell, you might want to try nvidia inspector for your fsx graphics settings. It has improved my overall sim performance. Also i personally use the nvidia 314.22 driver which I think works best for the card.

Thanks addison. Too bad! I'm already running Autogen at sparse (don't care for too many trees popping up in front of me) so I guess what I've got is about as good as it's going to get.

 

I'm running DX10 mostly and have a well tweaked Nvidia Inspector profile. Actually using the 320.18 driver - did you find a problem with it that would suggest I roll back to 314.22?

 

So, just what does setting Mipbias do then?

At the end of the day it all depends on your card's capabilities.

I have a Geforce 9600 GSO 512

my settings are:-

[TERRAIN]
TERRAIN_ERROR_FACTOR=100.000000
TERRAIN_MIN_DEM_AREA=10.000000
TERRAIN_MAX_DEM_AREA=800.000000
TERRAIN_MAX_VERTEX_LEVEL=21
TERRAIN_TEXTURE_SIZE_EXP=8
TERRAIN_AUTOGEN_DENSITY=5
TERRAIN_USE_GRADIENT_MAP=1
TERRAIN_EXTENDED_TEXTURES=1
TERRAIN_DEFAULT_RADIUS=9.0000
TERRAIN_EXTENDED_RADIUS=9.9
TERRAIN_EXTENDED_LEVELS=4

 

The first one in red extends the area of the "cross" so from high altidude the view looks normal!

Anisotropic filtering reduces the shimmering. Mine is set to 16x

My card set will all the slider at max does around 60fps.

However, feed in antialiasing 8x and that reduces to 30fps!

 

 

Thanks addison. Too bad! I'm already running Autogen at sparse (don't care for too many trees popping up in front of me) so I guess what I've got is about as good as it's going to get.

 

I'm running DX10 mostly and have a well tweaked Nvidia Inspector profile. Actually using the 320.18 driver - did you find a problem with it that would suggest I roll back to 314.22?

 

So, just what does setting Mipbias do then?

Mipbias has very little, if any effect in fsx in terms of the user CFG file. It is still used by scenery developers to mip buildings etc. It used to funcion well in fs9, it helped to load distant textures quickly but is unfortunately no longer relevant. Your best off editing you LOD_Radius to a figure between 5.5 and 6.5 (I personally use 5.5) I'm running a 3770k i7 @ 4.5ghz and get a massive performance hit at LOD 6.5 and I don't think it's really worth it.

 

As for drivers I was using 320.48?? But I had a shimmering problem at certain payware airports. I tried different drivers, but settled with 314.22 as this reduced the shimmering to a less noticeable level, which I can just about tolerate haha.

 

Ultimately with the game if you give with one hand it takes with another. I.e you solve one problem and another arises. It's just the way it is, at least until p3d 2.0 comes out...