Post by fried_oreos on Jan 15, 2024 21:22:12 GMT
I found out that it is possible to change the elevation exaggeration setting in the registry editor, bypassing the normal limit of 0.01 - 3.
If you want to do this yourself, the key is at Computer\HKEY_CURRENT_USER\SOFTWARE\Google\Google Earth Pro\Render. You will have to restart Google Earth for it to apply.
To start out, I set EE to 100. In the oceans, I tried to zoom in to the bottom, but when I crossed around -2m feet, terrain would unload and kick me back up. Additionally, a second water layer would appear at around -1.64m feet in deep ocean, but near land, the water layer would appear at 0 elevation as normal.
I wanted to see if Google Earth would still work if terrain went through the center, so I set EE to 581, which would push the Mariana Trench through the middle. Surprisingly, Google Earth did not crash.
This strange shape might be related to the glitch I discovered in this thread.
Then, I set elevation exaggeration to 10000 to see what would happen. Severely distorted portions of the earth would occasionally flash on screen, but mostly, it failed to render anything. Interestingly, the terrain pushed my camera out past even the 39000 mile altitude limit, causing "eye alt" to be measured in AU.
Next, I tested 0 and negative EE values. This caused all terrain to be set to 0 feet, but the actual visible terrain rendered in a low quality format under 0 feet in a weird polyhedron shape.
Finally, I tested a small positive value of EE below the 0.01 limit. When zooming in, everything looked flat as expected, but when I zoomed out, this weird thing happened.
If you want to do this yourself, the key is at Computer\HKEY_CURRENT_USER\SOFTWARE\Google\Google Earth Pro\Render. You will have to restart Google Earth for it to apply.
To start out, I set EE to 100. In the oceans, I tried to zoom in to the bottom, but when I crossed around -2m feet, terrain would unload and kick me back up. Additionally, a second water layer would appear at around -1.64m feet in deep ocean, but near land, the water layer would appear at 0 elevation as normal.
I wanted to see if Google Earth would still work if terrain went through the center, so I set EE to 581, which would push the Mariana Trench through the middle. Surprisingly, Google Earth did not crash.
This strange shape might be related to the glitch I discovered in this thread.
Then, I set elevation exaggeration to 10000 to see what would happen. Severely distorted portions of the earth would occasionally flash on screen, but mostly, it failed to render anything. Interestingly, the terrain pushed my camera out past even the 39000 mile altitude limit, causing "eye alt" to be measured in AU.
Next, I tested 0 and negative EE values. This caused all terrain to be set to 0 feet, but the actual visible terrain rendered in a low quality format under 0 feet in a weird polyhedron shape.
Finally, I tested a small positive value of EE below the 0.01 limit. When zooming in, everything looked flat as expected, but when I zoomed out, this weird thing happened.