Jump to content

View more

Image of the Day

The night is still, but the invasion brings chaos. #screenshotsaturday #hanako #indiegame #gameart #ue4 #samurai https://t.co/cgILXuokoS
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

Does the tessellator require a 32-bit index buffer for safety reasons?

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
1 reply to this topic

#1 mrheisenberg   Members   

360
Like
0Likes
Like

Posted 11 January 2014 - 03:03 PM

Assuming I use DXGI_FORMAT_R16_UINT and not DXGI_FORMAT_R32_UINT for an index buffer format and an unsigned short array for the indices, I get 65536 vertices for a mesh.Now this is good, because it's not like I would ever bind a mesh that huge, but what if I bind a mesh that has 20000 vertices and I use tessellation to generate new vertices, so the new mesh has 4 times more vertices(80000).Will this be an issue with a 16-bit index buffer?



#2 MJP   Moderators   

19468
Like
1Likes
Like

Posted 12 January 2014 - 01:43 AM

No, it shouldn't cause any issues. The indices in your index buffer will only correspond to control points pre-tessellation, and not the vertices generated between the hull and domain shaders.






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.