If you experienced disappearing traffic in FSX:SE – I have an easy fix for you! SmallPartRejectRadius will prevent planes vanishing and popping in 0.3-0.5 mile distance.
FSX tweak / fix guide
Effect on performance: minimal to severe
Good for: all users of FSX Steam Edition
Disappearing planes – the problem
When I moved “full time” to FSX Steam I noticed that some objects (mostly planes but also some boats) are disappearing or popping out in a small distance. It did not bother me until I flew online with a friend. It was really annoying when I lost sight of him while he was flying just 0.3 miles in front of me (I checked his position and distance using FSX traffic labels). We discussed the problem and thought about a tweak that was used for a completely different purpose but had a similar effect.
How it looks in fsx.cfg:
SmallPartRejectRadius tweak allows you to improve performance slightly by removing the smallest objects you see. Turn it to 2 and it will eliminate all objects smaller than 2 pixels (after some tests – I think it means “if a width or height is equal or smaller than”). 4 will take away even larger objects and 8 will kill some pretty large stuff (and causes unpleasant popping – when objects finally appear).
It seems that FSX:SE use a default setting of “2”. It’s different than in legacy FSX that defaulted to “0”. That is why some objects disappear in FSX:SE.
What do you need to do? Add the SmallPartRejectRadius=1 to [SCENERY] section of your fsx.cfg file.
If you are not sure where your fsx.cfg file is – read my note on fsx.cfg location.
Setting it to 0 will help with object popping even more, but there is a severe cost in performance with some sceneries. In some cases (high-end PC and some sceneries) you will see no problems. In other cases (heavy sceneries – even on high-end PCs) you will notice a severe decrease in performance.
Who should use this tweak?
I think it’s good for all users who have a medium or high-end PC.
Users of low-end PCs who do not fly online may consider keeping the default value or playing with values between 2 and 8 (I suggest using 2 and 4).