Jump to content
  • Advertisement


  • Content Count

  • Joined

  • Last visited

Community Reputation

122 Neutral

About stino

  • Rank
  1. Hi all, I'm rewriting my little game framework for the 3rd time and this time I want to get a good render function. I realize I have to sort my meshes and vertex buffers, if only to make sure transparent objects don't mess up the z-buffer. But to eliminate expensive pixel operations, cheap surfaces want to be rendered before expensive ones. Also, far away and really close meshes have lower priority for being rendered at all. Then again, really close meshes that are rendered -- as in the kind that blocks the camera for a frame -- want to be rendered first, because they fill the z-buffer. Actually, in general, the z-buffer wants meshes to be rendered front-to-back. Sigh. And then there's meshes that require special render modes that should not be switched to-and-back too often during one render. By those special modes I mean for example meshes using the effect classes or other shaders. Then there is highly detailed meshes, in which the amount of vertices is so high, it actually surpasses the texels in weight. Such a mesh, off course, you would like to render at a later point in the queue. So all this sounds like a few strict base rules and then a whole lot of 'fuzzy' rules. And I don't like fuzzy. So what's the best way? I was thinking of maybe giving points to each of these properties of a mesh and then adding all these up to arrive at a general how-bad-do-I-want-to-be-in-front-index for each mesh... but that would take a lot of testing. I'm hoping maybe there's some reading on this. Thanks, Stijn
  2. mattnewport, thanks for that link, it is an interesting read and exactly what I was looking for
  3. I've been playing around with the Siege Editor and enjoy the very straightforward way of editing terrain. I was wondering what you call this approach of a scenery engine. I was also wondering if the same approach is used for other games. For those who don't know the editor: you start the map with one root node, and attach nodes to it using both nodes' doors. The doors are simple face edges and they must fit to make the terrain work. Much like one of thos minature race tracks. If you create a circle (or patch) of nodes, the last and first are automaticly attached if they fit, which actually turns the tree into a graph. I'm asking because I want to figure out how to do this for my own game. Thanks!
  • 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!