Jump to content

View more

Image of the Day

Boxes as reward for our ranking mode. ヾ(☆▽☆)
#indiedev #gamedev #gameart #screenshotsaturday https://t.co/ALF1InmM7K
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

Order your draw calls..

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
2 replies to this topic

#1 kilah   Members   

514
Like
1Likes
Like

Posted 14 July 2013 - 11:14 AM

Hi everyone,

 

Just curious I was reading http://realtimecollisiondetection.net/blog/?p=86 when I decided to think about actually implementing the system as mention, but I faced a dilema. When sorting by key, which includes depth, what depth is that? The centroid of the renderable based on camera position? How do you deal with overlapping objects which centroids are properly sorted? Isn't that a problem? how are you supposed to handle those kind of issues?

 

In fact I was thinking how does this handles concave objects that wrap other objects within. My first guess was about splitting object into smaller sub meshes and then form the drawcall on the fly by combining those meshes, but seems quite suboptimal.

 

Any hints would be greatly appreciated, thanks.



#2 Arkhyl   Members   

626
Like
0Likes
Like

Posted 14 July 2013 - 12:49 PM

Overlapping objects will be an issue when you are dealing with transparent objets, and in this case the only solution, beside OIT techniques, is not to sort objects but triangles by depth to avoid potential artifacts, which might be impracticable in real-time (Unigine seems to do it, but I don't know how).

So, in the general case, centroid distance is generally enough for draw call sorting.



#3 Waterlimon   Members   

4398
Like
0Likes
Like

Posted 14 July 2013 - 12:49 PM

For opaque objects it isnt that huge of an issue because Z testing will still make them render correctly.

 

For translucent objects, to achieve absolute correctness you must pretty much do the sorting triangle by triangle and in some cases even split up the individual triangles (if theyre overlapping for example)

 

If you only have windows and glass objects to worry about, it doesnt really matter how you sort them. If they get too close, the orientation and geometry of the objects will affect what the best way to sort them is.


o3o





Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.