maximum number of vertices and surfaces per entity
Blitz3D Forums/Blitz3D Programming/maximum number of vertices and surfaces per entity
| ||
| The search feature of the forums is off, so ... I remember someone having tested blitz/directX limits in terms of vertices and surfaces per entity. I would like to find back this post or if somebody knows something about it... |
| ||
| It is approximately 30000 of each per surface, and probably around 30000 surfaces per mesh as well. The indexes are stored using signed shorts, so the actual figure is something like 32767 +/- one or two. |
| ||
| *estimates how long ago it was* *clicks "3"* *posts Link* http://www.blitzbasic.com/Community/posts.php?topic=47912 so the actual figure is something like 32767 +/- one or two. You said.. Unsigned... so double that :) *thinks* Man, blitz' maths system is a bit low isnt it? Even my BBC could handle more than 65525.... |
| ||
| Doh, I meant signed shorts :) |
| ||
| I saw that edit! ;) ;) |
| ||
| So to summarize I have in Edzup post: ~18200 polygons per surface ~54600 vertices per surface And according to fredborg and cygnus: ~32767 polygons per surface ~32767 vertices per surface and ~32767 surfaces in a mesh And DirectX has a limit at 65525 polygons per mesh, that's a bit confusing, I never heard anyhting from Blitz Research on the subject... Thanks guys |
| ||
| 32767 should be safe, anything above that will bomb out on some graphics cards. |
| ||
| It should handle way more than 32767 as i dont think it makes sense to store vertex count as signed :P Just that some cards might fart at it. |
| ||
| Does it not also depend on the hardware??? Rhy :) |
| ||
| I get 65535 max vertices per mesh/surface. Tested. |
| ||
| Anything above 32000 Tris per surface may load nicely, but as soon as Renderworld is excuted, it's MAVed. I've just tested a mesh with 1.60 Million tris, saved it as B3D (28 Megs, without UV Coords), and then loaded it again. It's pretty slow, but it works. You may use 64k Vertices, not sure of that, but since most meshes are welded and use shared vertices, the number of tris is about the same as the number of vertices. So I'd suggest to use a 32000 limit. But it's funny, not so long ago computer architecture used to hit the 64k Ram segmentation border and they had to fix a lot of problems due to the lack of imagination in the times of the development of the 16 Bit adressing medthod. And right now the same happens with 3D stuff. We're doomed to work with segmented Maps... How does OGL handle this? |
| ||
| 65,535 here tested OK. I don't think the limit is graphics card derived. |
   |