If an AI a/c is any more than maybe 1000-2000 feet away, I cannot see them, even when I try to zoom in on them. FS still recognizes they're still there, as they're making announcements on the ATC frequency and such. I'm using MyTraffic X. Anybody else had this problem?

No guarantee but if you have RejectThreshold=(something) in your FSX config file under the heading of [bUFFERPOOLS], try cancelling out the entry by adding two slashes (//) in front of it and see what happens (as opposed to deleting it which allows you to easily put it back in if you ever wanted to). My understanding of the entry is that it restricts FSX from displaying objects at a given distance which is controlled by the 'number' after the equal sign, for example, RejectThreshold=524288 or RejectThreshold=131072. I believe the higher the number, the further away objects will be displayed and that if you cancel the entry, then FSX will attempt to display objects that could have a negative effect on performance. I use "524288' which works for me by allowing AI to be seen from quite a distance while restricting the display of other objects beyond that point.

 

Hope this helps.

 

JJ

ejectThreshold=(something) in your FSX config file under the heading of [bUFFERPOOLS], try cancelling out the entry by adding two slashes (

JJ, you might be mixing this up with smallpartradius=x. I have it removed from my fsx cfg. BTW, I might have worded the tweak incorrectly, but you get the jist.

RejectThreashold will not effect objects, and how they are drawn at a distance.

Hi Julian,

 

I probably am mixing the two. Thanks for the clarification.

 

JJ

I was hoping this would fix my missing boats but no luck :-(

Smallpartradius= whatever size pixel is drawn. So, smallpartradius=4, means that any texture will be drawn at 4 pixels wide and any smaller than that it will not appear. Smaller the number the further away you'll be able to see AI.

I have the same problem as the original poster, at least with invisible textures. I did a search in my fsx.cfg and did not find an entry called smallpartradius. If I add it in, will it make a difference? If so, under which section should it be added?

 

- Kenneth J Kerr

Apologies guys, typo (and wine!) It should read SmallPartRejectRadius, place it in your [scenery] section and add SmallPartRejectRadius= 1, 2, 3, or 4. try different values to see which is best. Although I have read that it doesn't work after SP2, but it's worth a go.

Thanks for the clarification Howard. Unfortunately, you seem to be right with regards to SP2. Despite the addition of the smallpartrejectradius line, there was no change, even when trying various numerical values.

 

It is strange how all ai aircraft are globally affected by this texture disappearance. Even when using fs recorder on playback, the same issue is apparent. I wonder if there is a global fix to this, or if a line could be invented in the fsx.cfg to change it?

 

Anyone else been successful in extending the global visible range of ai textures in fsx with sp2?

 

Kenneth J Kerr

I wonder... unsure on this one, but how do you have your filtering set? in FSX, anisotropic?