{"id":1991,"date":"2015-11-29T03:49:23","date_gmt":"2015-11-29T03:49:23","guid":{"rendered":"http:\/\/phoenixgamedevelopment.com\/blog\/?p=1991"},"modified":"2015-11-29T03:49:23","modified_gmt":"2015-11-29T03:49:23","slug":"p-152-virtual-world-concept-update-77-chunked-levels-of-detail-using-quad-trees-part-44","status":"publish","type":"post","link":"https:\/\/phoenixgamedevelopment.com\/blog\/p-152-virtual-world-concept-update-77-chunked-levels-of-detail-using-quad-trees-part-44\/","title":{"rendered":"P-152: Virtual World Concept Update 77: Chunked Levels of Detail Using Quad Trees Part 44"},"content":{"rendered":"

I have made progress in identifying the issue that was causing the seams to incorrectly line up.<\/p>\n

I now believe that this problem has existed at least since I implemented the quad based rendering, and possibly even further back than that. The reason why I didn’t notice it is that it becomes far less obvious at higher resolutions. The first images shown below are the current state of the terrain. The seams are visible, but far less so then they were in the previous images I posted. The below images were taken with a terrain size (per quad sphere face) of 1024, while the previous images were taken at a terrain size of 64.<\/p>\n

While testing the terrain previously, I generally used a resolution of 4096, which means the seams just weren’t noticeable, but the problem was there. I was able to confirm this by reverting to a previous version of the file I was working on, and lowering the resolution.<\/p>\n

I believe the problem is caused by an error in one row in the points generation algorithm. This algorithm works by generating a set of points to match the resolution, so a resolution of 64 will generate 64*64 points, or 4096 points. I have had to create a complex function to iterate through these points however, since they need to be created in quads, with all 4 points of the quad beside each other. This means that I can’t use a conventional nested for loop. I believe that this algorithm is slightly wrong, and one iteration of the algorithm is off, causing the seaming issues.<\/p>\n

Since there are more points at higher resolutions, (eg, 1024*1024 = 1,048,576 \u00a0points) having one row out of sync is far less noticeable.<\/p>\n

This problem will need to be fixed, of course, but it does not have to be fixed now. I will be conducting the rest of my work at a reasonably high resolution, so this problem shouldn’t be too obvious. If I achieve proof of concept, I can come back to this and fix it.<\/p>\n

 <\/p>\n

\"PhoenixGameDevelopment185\"PhoenixGameDevelopment183\"PhoenixGameDevelopment187\"PhoenixGameDevelopment182\"PhoenixGameDevelopment177<\/a> \"PhoenixGameDevelopment167\"PhoenixGameDevelopment179<\/a> \"PhoenixGameDevelopment178\"PhoenixGameDevelopment135\"PhoenixGameDevelopment157<\/a> \"PhoenixGameDevelopment154<\/a> \"PhoenixGameDevelopment151<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I have made progress in identifying the issue that was causing the seams to incorrectly line up. I now believe that this problem has existed at least since I implemented the quad based rendering, and possibly even further back than that. The reason why I didn’t notice it is that it becomes far less obvious […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,10,11],"tags":[],"class_list":["post-1991","post","type-post","status-publish","format-standard","hentry","category-astral-realms","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\/1991"}],"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=1991"}],"version-history":[{"count":2,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/1991\/revisions"}],"predecessor-version":[{"id":1993,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/1991\/revisions\/1993"}],"wp:attachment":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/media?parent=1991"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/categories?post=1991"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/tags?post=1991"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}