Discovered an interesting fact: Configuring visibility of 12,000 meters, then place the helicopter at an altitude of 56,000 meters, you get 200 FPS. After that the helicopter itself will fall. At an altitude of 55,000 meters below you get a sharp decrease FPS several times. Then do the same thing, only with a visibility range of 6000, at an altitude of 55,000 meters below you get a sharp decline in FPS.
If I understand correctly, this means that all objects in the game begin to be processed on the computer range 55000 meters instead of visibility that you configure in the game. In this regard, I daresay, if this option (which is responsible for 55,000 meters) to make customizable, and bind it to the range of visibility, you can get a huge performance boost.

P.S.
Discovered another interesting fact:
The first time I put the camera in the far west of the island at an altitude of 55,000 feet above sea level, at an altitude of 54,899 meters has been a sharp decrease in FPS.
The second time I put the camera over the island at an altitude of 55,000 from the surface of the earth at an altitude of 54690 has been a sharp decrease in FPS.
Height of land above sea level in the place where I put the camera for the second time is 209 meters, so 54690 + 209 = 54899, is the same as in the first case. This means that the distance at which water begins to boot the computer is always 54899, because of this great loss FPS! What do you think about this? I think that it is unnecessary to load water at a distance of 54,899 meters from the player, it leads to poor performance This range of load water need to bind to the overall visibility. {F23010}