Post by fried_oreos on Oct 1, 2022 2:46:44 GMT
This is the continuation of the previous thread I made about going far from the earth with the flight sim, but now I figured out how to get images on it.
Recap: 39k miles is normally the maximum distance possible to zoom out, but through modification of flith. At about 50-60k miles of altitude the units for eye alt on the bottom right change to AUs (Astronomical Units)
0.001 au ^
This is the view back to earth from about 0.002 au (about the distance from the moon to the earth)
Much farther. The speeds needed to reach this distance in a reasonable amount of time are so high it is now possible to start flight sim on one side of the earth, point straight down, and fly through the other side without triggering a crash.
I decided to try to reach the sun. Normally, the sun disappears at high altitudes (probably intentional) but when the daylight option is turned on, you can get it to stay.
At about 125 au, I assume I passed through the sun layer. Screenshots don't depict this well, but basically stars started disappearing in a circle closing in on the sun before I finally passed through the layer and the sun disappeared.
After that, there's nothing interesting. So I decided to push the flight simulator itself to its limits. At around 10^14 speed, some floating point precision errors start to occur and the plane's speed and heading begin to jitter.
Then the HUD began to break:
The final frontier is the 64-bit integer limit, the highest possible value google earth can store.
Surprisingly Google Earth did not crash and the flight sim kept working but the altitude indicator broke.
Same thing happened upon reaching 64-bit-integer limit velocity.
Another few orders of magnitude and the HUD broke further (notice several billion au altitude) and it became very laggy.
Last interesting thing before google earth straight up crashes.
Recap: 39k miles is normally the maximum distance possible to zoom out, but through modification of flith. At about 50-60k miles of altitude the units for eye alt on the bottom right change to AUs (Astronomical Units)
0.001 au ^
This is the view back to earth from about 0.002 au (about the distance from the moon to the earth)
Much farther. The speeds needed to reach this distance in a reasonable amount of time are so high it is now possible to start flight sim on one side of the earth, point straight down, and fly through the other side without triggering a crash.
I decided to try to reach the sun. Normally, the sun disappears at high altitudes (probably intentional) but when the daylight option is turned on, you can get it to stay.
At about 125 au, I assume I passed through the sun layer. Screenshots don't depict this well, but basically stars started disappearing in a circle closing in on the sun before I finally passed through the layer and the sun disappeared.
After that, there's nothing interesting. So I decided to push the flight simulator itself to its limits. At around 10^14 speed, some floating point precision errors start to occur and the plane's speed and heading begin to jitter.
Then the HUD began to break:
The final frontier is the 64-bit integer limit, the highest possible value google earth can store.
Surprisingly Google Earth did not crash and the flight sim kept working but the altitude indicator broke.
Same thing happened upon reaching 64-bit-integer limit velocity.
Another few orders of magnitude and the HUD broke further (notice several billion au altitude) and it became very laggy.
Last interesting thing before google earth straight up crashes.
