The current goal is to find an efficient way to switch between the different distances that I am dealing with.<\/p>\n
I have made some progress in transitioning between high-detail rendering and low-detail rendering. I have achieved this by first assuming a “max view distance”, beyond which the planet is not rendered. This view distance is 100 million Kilometers, or, 100,000,000,000 meters.<\/p>\n
I have tried various techniques to subdivide the terrain within this distance, but the difficulty is that at these extreme ranges it is not really possibly to subdivide individual nodes, I would have to subdivide the entire planet, and this causes performance problems leading to infinite loops in some cases.<\/p>\n
I have also changed a lot of the variables in the spherical terrain distance code to “long long ints”, or, as Torque called them, “U64” for Unsigned int, 64 bit. This will give me plenty of precision.<\/p>\n
The solution I am working on now it to\u00a0use a small number (no more than 3-4) of low\u00a0resolution LOD’s\u00a0for very long distances. This should not be noticeable, since\u00a0the terrain will appear mostly as just a dot at these distances. I will then subdivide at closer distances using the current system.<\/p>\n
Once I have this solution working, I will need to fix the texture painter, and correctly scale the planet with respect to distance. I will also need to come up with some way to\u00a0test the various distances in code by simulating the players movement.<\/p>\n P152_DEBUG![\"P152_DEBUG](\"https:\/\/phoenixgamedevelopment.com\/blog\/wp-content\/uploads\/2016\/08\/PhoenixGameDevelopment-11_08_2016-01_01_02-AM.jpg\")
<\/a>
11\/08\/2016 , 01:01:02 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n<\/a>
11\/08\/2016 , 01:01:25 AM
Torque 3D MIT – P152
[SCM]actwin,0,0,1617,1008;<\/figcaption><\/figure>\n<\/a>
11\/08\/2016 , 01:01:23 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n<\/a><\/p>\n
\n10\/08\/2016 , 05:02:04 AM
\nTorque 3D MIT – P152<\/p>\n