Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

50%
+1 −1
Q&A How would I go about chunk loading around player in a 3 dimensional cartesian coordinate space

It seems I'm missing something since the answer should really be obvious. Nonetheless, I'll answer what you appear to be asking to get the obvious case out of the way. The method has already "f...

posted 2y ago by Olin Lathrop‭  ·  edited 2y ago by Olin Lathrop‭

Answer
#2: Post edited by user avatar Olin Lathrop‭ · 2022-11-07T13:10:13Z (about 2 years ago)
  • The method has already "fallen apart" due to the extra axis of 2D. In 1D it's nice and simple. You grab N behind and N in front, all nicely sequential.
  • Note how your diagram has lines that break the flow and start again at a new Y coordinate. 3D is just an extension of that.
  • In 2D, you already know how to load a row. You go back and load multiple rows when the Y dimension is added. In 3D, you remember from the 2D case how to load a layer. You go back and load multiple layers when the Z dimension is added.
  • It seems I'm missing something since the answer should really be obvious. Nonetheless, I'll answer what you appear to be asking to get the obvious case out of the way.
  • <hr>
  • The method has already "fallen apart" due to the extra axis of 2D. In 1D it's nice and simple. You grab N behind and N in front, all nicely sequential.
  • Note how your diagram has lines that break the flow and start again at a new Y coordinate. 3D is just an extension of that.
  • In 2D, you already know how to load a row. You go back and load multiple rows when the Y dimension is added. In 3D, you remember from the 2D case how to load a layer. You go back and load multiple layers when the Z dimension is added.
#1: Initial revision by user avatar Olin Lathrop‭ · 2022-11-07T13:07:56Z (about 2 years ago)
The method has already "fallen apart" due to the extra axis of 2D.  In 1D it's nice and simple.  You grab N behind and N in front, all nicely sequential.

Note how your diagram has lines that break the flow and start again at a new Y coordinate.  3D is just an extension of that.

In 2D, you already know how to load a row.  You go back and load multiple rows when the Y dimension is added.  In 3D, you remember from the 2D case how to load a layer.  You go back and load multiple layers when the Z dimension is added.