{"id":1811,"date":"2015-11-01T23:57:27","date_gmt":"2015-11-01T23:57:27","guid":{"rendered":"http:\/\/phoenixgamedevelopment.com\/blog\/?p=1811"},"modified":"2015-11-02T04:35:41","modified_gmt":"2015-11-02T04:35:41","slug":"p-152-virtual-world-concept-update-61-chunked-levels-of-detail-using-quad-trees-part-29-2","status":"publish","type":"post","link":"https:\/\/phoenixgamedevelopment.com\/blog\/p-152-virtual-world-concept-update-61-chunked-levels-of-detail-using-quad-trees-part-29-2\/","title":{"rendered":"P-152: Virtual World Concept Update 62: Chunked Levels of Detail Using Quad Trees Part 30"},"content":{"rendered":"

 <\/p>\n

I have made a lot more progress in investigating the problems I have been having with the spherical terrain.<\/p>\n

Firstly, I now believe that these problems are actually preexisting. Below are some screenshots that I took with the old codebase, which I believed was working correctly (using triangle based rendering).
\nHowever, there are some missing polygons, and some visible graphical distortion occuring at the edges of the quad spheres faces. \u00a0I hadn’t paid much attention to these before, I assumed they were simply minor bugs that could be corrected later, but I now believe that these are actually more serious issues with the underlying algorithms.<\/p>\n

I have, after much effort, managed to get the points to be generated in groups of four. What was happening is that the loop I was using to generate the points was incrementing and decrementing in the conventional way, like this:<\/p>\n

for(int i = 0;i<maxvalue;i++)<\/p>\n

{<\/p>\n

for(int j= 0;j<maxvalue;j++)<\/p>\n

{<\/p>\n

}<\/p>\n

}<\/p><\/blockquote>\n

This produced the correct number of points, but, each group of 4 points was arranged in a line, not a quad, (since it was being incremented by 1 at a time).<\/p>\n

I have now modified this algorithm to produce points in contiguous groups of 4. This is significant progress, however, I have still not completed the quad rendering. I have had to completely re-evaluate and modify the existing spherical terrain system, including the rendering. I am confident that I will solve this issue, and I feel that I could be relatively close, but I am not quite there yet.<\/p>\n

I have put a lot more work into this project that I have had time to post here, these are just snippets of what I have actually done. I feel that, even though this has taken a lot of time, I have a much greater understanding of how this whole system fits together now. So much so that I have been able to make complex optimisations to the code as I am working through it, removing older code that I had added when I clearly didn’t fully understand the workings of the system. I have even removed an entire loop from the codebase, which was used to rearrange the order of the vertices so that they rendered correctly. I have now incorporated this into the first loop, which generates the vertices.<\/p>\n

I have also completely refactored most of the other code in the spherical terrain generation functions, improving and optimising it. I had quite a bit of redundant code in there that has now been removed, and other code that worked in some cases, but failed for others. This would no doubt have resulted in irritating bugs at some point, if I hadn’t dealt with it now.<\/p>\n

Since the terrain system needs to be fast and reliable, this time has certainly been well spent.<\/p>\n

\"PhoenixGameDevelopment181<\/a> \"PhoenixGameDevelopment180<\/a> \"PhoenixGameDevelopment179<\/a> \"PhoenixGameDevelopment175<\/a> \"PhoenixGameDevelopment187<\/a> \"PhoenixGameDevelopment186<\/a> \"PhoenixGameDevelopment203<\/a> \"PhoenixGameDevelopment201<\/a> \"PhoenixGameDevelopment213<\/a> \"PhoenixGameDevelopment217<\/a> \"PhoenixGameDevelopment220<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

  I have made a lot more progress in investigating the problems I have been having with the spherical terrain. Firstly, I now believe that these problems are actually preexisting. Below are some screenshots that I took with the old codebase, which I believed was working correctly (using triangle based rendering). However, there are some […]<\/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-1811","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\/1811"}],"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=1811"}],"version-history":[{"count":6,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/1811\/revisions"}],"predecessor-version":[{"id":1823,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/1811\/revisions\/1823"}],"wp:attachment":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/media?parent=1811"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/categories?post=1811"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/tags?post=1811"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}