Hello,
I come to share with you an amazing thing I've seen on Fg in 2016.1.0
release. Another person has reached the same conclusion as me with the
same version of FG, both using a 777 Seattle.
We took off from TFFF to land at LFLL. For my part, my cruising altitude
was 35,000 feet. I found that, more I climbed in altitude, more I was
losing FPS. Initially I had 60 FPS and more than 35000 feet 22-25 FPS.
During the flight, I went down to 9,000 feet to see if the FPS went up,
in vain. I decided to go up to 35,000 feet for the rest of the flight.
My friend, stole 9,000 feet at 60 FPS all along. Just before he made the
same flight but gaining altitude in steps and it also lost FPS.
I should point out one thing, it has accelerated the simulation speed
and sometimes handed over to normal speed for this test.
On arrival, my friend, flying at 9000 feet, was still 60 FPS and i, i
had no more than 15 FPS.
In summary, during this test, we made the same observation: the higher
you go, more you lose FPS and we not recover if we descend to an
altitude of 9000 feet.
I give you my hardware configuration:
- Intel Core i5 4690 (3.5GHz)
- 16 GB of DDR3 RAM
- Nvidia GTX970 with 4GB GDDR5
- FG 2016.1.0 updated this afternoon (12 january)
---------------------------------------------------
Friend's view point (Xavier, usually AF2222).
This seems to be fully confirmed.
Linux Mint mate 1.6.1.
I7
FX 965.
FG Compilation 2016/01/12 13H UTC.
B77 200ER Seattle.
Constatation:
If standing FL 90, everything seems to be all right.
If climbing to FL 330, slow but constant fps loose.
On LFLL -> TFFF, about 10 fps remainding when arriving (60 fps at
departure).
This phenomena is present for about 2 monthes (with same aircraft data).
It is fully reproductible.
It is is NOT dependent on simulation rate.
Reloading aircraft restores initial fps rate(but no sound after).
This seems to be dependant only on altitude (or inducted parameters,
like ground speed?).
Best regards.