For grins, I've tried about every imaginable affinity setting, and IMO NONE were any better than what FSX does all on its own without any fsx.cfg help.  BTW, I do run HT off (at least for FSX) not because it helps smoothness, but because I get a better OC with lower temps and because running (using default affinity settings) with HT enabled is no better, nor no worse, FSX performance wise, so I go with the better OC.  

 

Thank you. 

I've tried both and so far can't discern anything different performance-wise.  Though I see that when FSX runs Process Monitor says 67 threads are operating.

 That's been pretty much my experience also. The concern about HT is irrelevant, except if you are trying to eke out the last few Hz in your OC.

I suppose technically, someone (and or group of developers) could code an application that would take into account your flight plan, weather, add-ons, aircraft, textures, terrain mesh, and formulate an optimal LOD_RADIUS.

 

Based on Boez' findings:

 

Optimal LOD Radius = 4.5 + [Amount of excessive, too far-away bitmaps to notice]

 

 

 

 

 

I run 5.5 for shits 'n' giggles. Any higher would be pointless anyway.

Optimal LOD Radius = 4.5 + [Amount of excessive, too far-away bitmaps to notice]

 

My original images at the start of this thread would indicate that's not the case.  You can clearly see a visual difference the higher the LOD_RADIUS.

 

I'll disable Boston Ultra and do the same screen shots at the same location and lets see if the visual radius is the same or different ... that should confirm Boez findings.

My original images at the start of this thread would indicate that's not the case.  You can clearly see a visual difference the higher the LOD_RADIUS.

 

I'll disable Boston Ultra and do the same screen shots at the same location and lets see if the visual radius is the same or different ... that should confirm Boez findings.

 

Yes, please. Maybe photoscenery reacts better to LOD_RADIUS changes than default tiles.

I was just poking around some old threads and recalled the MipBias setting in the fsx.cfg. It was stated that this setting:

[Display]
MipBias=6

would force higher res textures to be loaded further out. Boez - I presume you tried this also, but I have to ask!

 

I also came across this thread which is relevant to a question i asked you earlier:

http://forum.avsim.net/topic/391709-lod-bias-clamp-vs-allow/

Mr. Van E seems to have come to a different conclusion - placebo effect, user error on our part or perhaps a change in drivers has 'broken' LOD Bias?

Based on Boez' findings:

 

Optimal LOD Radius = 4.5 + [Amount of excessive, too far-away bitmaps to notice]

 

I run 5.5 for shits 'n' giggles. Any higher would be pointless anyway.

 

I don't agree. In areas with lots of mountains and high resolution mesh I could not fly below my standard 6.5 setting. But we all have different tolerances.

I was just poking around some old threads and recalled the MipBias setting in the fsx.cfg. It was stated that this setting:

[Display]

MipBias=6

 

 

I haven't done much testing with this value, currently using MipBias=10.  Here are some shots from Horizon VFR Scotland (lots of mountians), LOD_RADIUS = 11.

 

 

 

 

 

 

I haven't done much testing with this value, currently using MipBias=10.  Here are some shots from Horizon VFR Scotland (lots of mountians), LOD_RADIUS = 11.

 

 

So you feel the MipBias parameter does make a difference for you? I asked about this parameter about a month ago and was told it was no longer relevant in FSX. If it is relevant, I would expect Boez scenery rings should show that. Distance detail in those screen-shots doesn't blow me away but I realize that they are downsized and compressed (no offense intended!)

So you feel the MipBias parameter does make a difference for you?

 

I have no feeling, haven't really tested it extensively ... Phil Taylor suggests the parameter is used.   I believe (don't quote me) that on NVidia cards you need to set Negative LOD Bias = Clamp for this to be useful.

 

Screenshots were not intended to blow anyone away, just showing a region with high density terrain mesh that I happen to have available.  The source Horizon VFR textures are hit and miss in Scotland, some areas really good, some just so so (like this one, not great, but not bad either).  I think MSE Oregon/Washington has some better sources (again with high density terrain mesh). This shot was done with weather and haze during a one of my flights in that area (mostly trying out Sim720 Oban) in real time (no pause and wait).  If I were to "show case" a LOD_RADIUS on scenery, I probably should disable any haze/weather.

 

I'm more interested to see how my LOD_RADIUS does or doesn't change when I disable MSE Boston Ultra City, with a just MSE Mass, and then again without MSE Mass and GEX US.  Hopefully I'll have time for that tonight, maybe even try out some MipBias variances.

 

Rob.

I would presume no magic here and that the parameter in the cfg simply requests the driver to use the same mipbias as setting it in NI does...however nothing surprises me about fsx so I'll try it out....

 

 

 

 

 

 

Sent from my HTC One S using Tapatalk now Free

 

 

P.s. I also use a higher lod in mountainous areas as the vertically presented tiles are more obviously blurred otherwise. On flat terrain the acute angle of the tiles make blurring due to distance much less obvious.

 

Sent from my HTC One S using Tapatalk now Free

 

 

 

 

I'm more interested to see how my LOD_RADIUS does or doesn't change when I disable MSE Boston Ultra City, with a just MSE Mass, and then again without MSE Mass and GEX US.

Yep - me too!

 

 

 

I would presume no magic here and that the parameter in the cfg simply requests the driver to use the same mipbias as setting it in NI does...however nothing surprises me about fsx so I'll try it out....

Looking forward to your results on that as well.

A thought on photo scenery...are they fully mipmapped bitmap texture files? I wonder what effect there'd be on the rings if one or more or all of the mips was deliberately excluded? I've not got any scenery of that type so can't explore further.

 

 

 

 

I you want to try some photoscenery, there are many freeware sources. here's a couple:

 

http://www.mediafire.com/view/?nke1y9cxny2yf74

 

http://aussiex.org/forum/index.php?/files/file/12-ozx-grand-canyon-and-kgcn-holgermesh/

 

http://www.blueskyscenery.com/download.html

 

You can just download one small area for testing purposes. I don't know how to tell if these are fully mipmapped though. Haven't tried the hawaii myself, but I use Bluesky and OZ World Grand Canyon.

A thought on photo scenery...are they fully mipmapped bitmap texture files? I wonder what effect there'd be on the rings if one or more or all of the mips was deliberately excluded? I've not got any scenery of that type so can't explore further.

 

You specify to resample which LOD levels and compression you want in the photo bgl.

 

scott s.

.

And straight from the horses mouth regarding Hyper Threading:

 

There is no need to disable HT, we detect physical vs logical cores and do the right thing.

 

- Phil Taylor

 

http://blogs.msdn.com/b/ptaylor/archive/2007/04/14/fsx-sp1-beta2-posted.aspx