{"id":3550,"date":"2016-08-28T23:00:18","date_gmt":"2016-08-28T22:00:18","guid":{"rendered":"http:\/\/phoenixgamedevelopment.com\/blog\/?p=3550"},"modified":"2016-08-28T23:00:18","modified_gmt":"2016-08-28T22:00:18","slug":"p-152-virtual-world-concept-update-163-planet-sized-terrain-part-42","status":"publish","type":"post","link":"https:\/\/phoenixgamedevelopment.com\/blog\/p-152-virtual-world-concept-update-163-planet-sized-terrain-part-42\/","title":{"rendered":"P-152: Virtual World Concept Update 163: Planet-sized Terrain: Part 42"},"content":{"rendered":"

After some hassle, I was able to get the 3D vector problem solved. It now works in all cases, regardless of the players position on the surface of the planet.<\/p>\n

I also fixed a minor bug with the collision system.<\/p>\n

The next, and hopefully minor, issue is to add the ability for the player to move around the terrain, and have it’s position correctly update, in both 32 and 64 bit space. This could be quite difficult, since there are so many translations going on.<\/p>\n

Preliminary testing began\u00a0quite well, the terrain can be updated as the user moves. However, I need to implement a “floating origin” system with the terrain, which means that when the user exceeds 10,000 meters, I need to move the visible terrain nodes back along a vector of length 10,000, and return the user to the origin, to ensure that the user never leaves the 10k boundary.<\/p>\n

This should be easy, but I am noticing that when I move the terrain nodes, they do not move cleanly, but instead, they seem to scale up, which shouldn’t happen. This problem becomes worse the further the player moves. This could end up being very serious.<\/p>\n

\"P152_DEBUG<\/a>
P152_DEBUG
25\/08\/2016 , 02:05:18 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
25\/08\/2016 , 06:57:18 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
25\/08\/2016 , 08:58:47 PM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
25\/08\/2016 , 01:47:54 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
23\/08\/2016 , 06:58:52 PM
Torque 3D MIT – P152
[SCM]actwin,0,0,1617,1008;<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
24\/08\/2016 , 02:26:50 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
24\/08\/2016 , 02:27:00 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
24\/08\/2016 , 05:37:06 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
24\/08\/2016 , 05:41:03 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
24\/08\/2016 , 06:04:26 AM
Torque 3D MIT – P152<\/figcaption><\/figure>\n
\"P152_DEBUG<\/a>
P152_DEBUG
24\/08\/2016 , 07:47:58 PM
Torque 3D MIT – P152<\/figcaption><\/figure>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

After some hassle, I was able to get the 3D vector problem solved. It now works in all cases, regardless of the players position on the surface of the planet. I also fixed a minor bug with the collision system. The next, and hopefully minor, issue is to add the ability for the player to […]<\/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-3550","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\/3550"}],"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=3550"}],"version-history":[{"count":4,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/3550\/revisions"}],"predecessor-version":[{"id":3566,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/posts\/3550\/revisions\/3566"}],"wp:attachment":[{"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/media?parent=3550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/categories?post=3550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phoenixgamedevelopment.com\/blog\/wp-json\/wp\/v2\/tags?post=3550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}