I don't know how to describe it otherwise:It's like the topic says. My traffic seems to disappear when a certain amount of distance from the viewpoint is acquired by the traffic.However, the sort of traffic seems to matter. I can identify 3:- default traffic- Ultimate Traffic 2 traffic- 3rd party traffic, for instance Dutch traffic as in NL2000v4 scenery.Observe some screenshots I made here. In most of the, you can see traffic appearing in chronological order as I close the distance between me and the traffic.As you can see, traffic "magically" appears when a certain amount of distance seems crossed. The closer the viewpoint (me in my aircraft) gets to the traffic, the more they become visible.When invisible the lights, labels and, if on, shadows, are visible, but not the actual aircraft.I have noticed that the default traffic is most affected, followed by the UT2 traffic. Other 3rd party traffic seems least affected.Another event I noticed, but don't have screenshots from, is 2 a/c on final, with me roughways in between on downwind, so the range to either plane is roughly the same.Both were Transavia craft, one being from NL2000v4 (spelled TRANSAVIA in its label), the other from UT2 (spelled Transavia.com in its label). The NL2000v4 was visible. The UT2 was not, only the label showing.From what I have found on the web, DX10 and any kind of shadows are normally the cause of these kinds of things. All are off in my settings.Does anyone have any clue how I can solve this. It is very annoying to have craft popping in and out of view, but knowing they are still there from radio communictions, lights and labels.Tobus

I had a similar issue, which I tracked down to a tweak I had added in the fsx.cfg.The entry: SmallPartRejectRadius=4 caused AI models to diasappear at a distance, leaving only their lights visible.Removing the tweak returned AI to normal.

It also depends on the LOD of the models being used.

I had a similar issue, which I tracked down to a tweak I had added in the fsx.cfg.The entry: SmallPartRejectRadius=4 caused AI models to diasappear at a distance, leaving only their lights visible.Removing the tweak returned AI to normal.

My SmallPartRejectRadius=8 is now removed from fsx.cfg. Will report back.

It also depends on the LOD of the models being used.

Thanks, figured as much. That would account for different sources of traffic showing different behavior.

Works like a charm, all traffic back at all ranges.Thanks a lot!

Works like a charm, all traffic back at all ranges.Thanks a lot!

If you still want to reap the benefit of using SmallPartRejectRadius, try a smaller number like 3 to 5, rather than 8. Keep in mind the number you were using, 8, means 8 pixels at which the object will no longer render. So, if you choose a smaller value like 3,4, or 5, then the object will appear sooner once it would take at least 3 to 5 pixels to render.8 is a pretty big numeber to use and 10 is the max. Personally, I have never used or even tried anything larger than 5, but find the 3 works pretty well.

If you still want to reap the benefit of using SmallPartRejectRadius, try a smaller number like 3 to 5, rather than 8. Keep in mind the number you were using, 8, means 8 pixels at which the object will no longer render. So, if you choose a smaller value like 3,4, or 5, then the object will appear sooner once it would take at least 3 to 5 pixels to render.8 is a pretty big numeber to use and 10 is the max. Personally, I have never used or even tried anything larger than 5, but find the 3 works pretty well.

I don't even know how this "tweak" got into my fsx.cfg, since I do not tweak, apart from highmemfix=1 and bp=0. I also do not know what the use of this particular smallpartrejectradius is. Can someone explain?What I do know is, that all traffic is back at all ranges, and fps are even improved.