Jump to content
  • Advertisement
Sign in to follow this  
rumpfi88

OpenGL One or multiple octrees

This topic is 1055 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

Hey guys,

 

I want to implement octrees in my hard coded raycasting/raytracing algorithm (no OpenGL or DirectX). I'm also able to load Wavefront OBJ files. But with more and more triangle meshes involved rendering takes longer and longer.

 

I think octrees are a good data structure for storing surfaces. I don't know which form of octrees is better.

  • one octree for the whole rendering scene
  • multiple octrees, one for each object

What's your opinion?

 

PS: Visit my blog where I explain computer graphics

Link: http://computergraphicsguide.blogspot.com/

Share this post


Link to post
Share on other sites
Advertisement

Both are needed usually.

 

You mean an object is within an octree, and that octree is within an octree surrounding the whole scene.

 

Scene octree consists of object octrees.

Share this post


Link to post
Share on other sites
You can always see what the professional raytraces are doing :
 
 
"Meshes are exported to a special .vrmesh file format. It contains all geometric information for a mesh - vertices and face topology as well as texture channels, face material IDs, smoothing groups, normals - in short, everything that is needed to render the mesh. In addition, the mesh is preprocessed and subdivided into chunks for easier access. "

Share this post


Link to post
Share on other sites

I only analysed Wavefront OBJ/MTL files and partly 3DS Max files.I don't know how vrmesh will help me with that.

The purpose of my framework is to do everything with the support of high quality graphic libraries. It shall help students to understand render algorithms.

Share this post


Link to post
Share on other sites

The idea is that the V-Ray guys, are creating a tree for every mesh(and ofc. a tree for the scene) Is to support fast instancing.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • 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!