Jump to content
  • Advertisement


This topic is now archived and is closed to further replies.


world size in d3d

This topic is 6845 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

This may be a rather stupid question, so I apologize ahead of time :-).

I'm building a isometric, top-down sort of RPG in d3d IM using height map based data. In attempting to create a smooth scrolling world, minus large load intervals in the middle of play I've come across this problem:

How large can you're world values be? I'd rather avoid transforming my whole mesh to always be from <0,0,0> on every frame but then if I did not the z and x could become rather large as the player walked further from the initial world origin. Would this be problem? I understand that d3d will only render items that would appear in the viewing area and I also intend to only transform items that are in that area. By going this route, though, I could have z and x unit values in the several thousands if not more. As for my app itself, becuase this is a simple tile map based engine mem requirements to store large world segments are not very high, so that is not an issue for me. I wanted to make sure that there was not issue with d3d, particulary performance wise, in doing my engine in this manner. Does d3d consider world space to be always a tight area around the camera or are the limitations simply the application data?

Thanks ahead of time and hopefully this makes sense.

Share this post

Link to post
Share on other sites

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!