![\"P152_DEBUG](\"https:\/\/phoenixgamedevelopment.com\/blog\/wp-content\/uploads\/2016\/07\/PhoenixGameDevelopment-14_07_2016-05_42_29-AM-300x194.jpg\")
<\/a><\/p>\nP152_DEBUG
\n14\/07\/2016 , 05:42:29 AM
\nTorque 3D MIT – P152
\nHowever, I have discovered a problem with my concept.<\/p>\n
Currently, the process is:
\nThe coordinates for the terrain nodes are in local space, so I scale these to world space (64-bit numbers).<\/p>\n
I then get the distance from the center of each terrain node to the player, and cull everything further than a specified distance.<\/p>\n
I then take the nodes that haven’t been culled, rescale them to 32-bit space, and apply the LOD subdivision to them.<\/p>\n
The problem here is that when I scale to 32-bit space I am basically scaling the entire world to a radius of 10,000 units. Even though I have a floating origin system, I am essentially not using it.
\nAs the player moves around the world in 64-bit space, the terrain in 32-bit space will update correctly, but that 32-bit terrain will have a radius of 10,000 units, which will not work.<\/p>\n
What I need to do, is to cull all nodes not close to the player, as I am currently doing, but then, instead of scaling them to 10k and then subdividing them using LODs, I would subdivide the 64-bit nodes without scaling. The initial terrain mesh is low resolution, so each node is far bigger than 10k. If I continuously subdivide each node,\u00a0and then continue to cull any nodes outside of the 10k boundary around the player, I should eventually end up with a finely detailed mesh containing only nodes within 10k of the player, which is exactly what I want.<\/p>\n
These changes will hopefully not be too difficult to implement.<\/p>\n","protected":false},"excerpt":{"rendered":"
I have made significant progress with the terrain’s floating origin system. I have added and tested all of the distance calculations, and I can now move the player in world space and have that world space position influence the rendering of the terrain nodes. This means that the terrain “pages” as the player moves in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,17,10,11],"tags":[],"class_list":["post-3233","post","type-post","status-publish","format-standard","hentry","category-astral-realms","category-p-0","category-software-and-games","category-spiritus-astrum","has-post-title","has-post-date","has-post-category","has-post-tag","has-post-comment","has-post-author",""],"aioseo_notices":[],"builder_content":"","_links":{"self":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/3233"}],"collection":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/comments?post=3233"}],"version-history":[{"count":3,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/3233\/revisions"}],"predecessor-version":[{"id":3237,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/3233\/revisions\/3237"}],"wp:attachment":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/media?parent=3233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/categories?post=3233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/tags?post=3233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"P152_DEBUG](\"https:\/\/phoenixgamedevelopment.com\/blog\/wp-content\/uploads\/2016\/07\/PhoenixGameDevelopment-14_07_2016-01_32_30-AM.jpg\")
<\/a>