|
Nuke Mexico posted:One of the few reasonable STL re-implementations was done for the pupose of exposing more memory-management options, i.e. using a pool- or cached allocator of some point, so I might be able to buy that. There's almost never any excuse for re-implementing your own vector or linked list or hash table yourself "because it is faster" because it almost certainly never is. Link to dis: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2271.html
|
#
¿
Jun 9, 2008 17:47
|
|
|
|
| # ¿ May 5, 2024 22:54 |
|
|
Zakalwe posted:Ray tracing/casting is computationally expensive. With M rays and N triangles, you get M*N intersection tests. Let's say you're rendering a 1024x1024 image with 1 ray cast per pixel and 6 million triangles. That's 1,048,576,000,000 intersection tests per frame. Wasn't the idea of the raycasting suggestion to skip the triangles altogether though, and just march through the volume data?
|
|
#
¿
Jul 2, 2008 11:42
|
|
|
Adhemar posted:Better to leave the image in the centre and move the inputs to the left to line up with it. Please. And right-align the text labels! Edit:  This is going to be the best in-house configuration tool ever! 
pseudopresence fucked around with this message at 20:30 on Jul 8, 2008 |
|
#
¿
Jul 8, 2008 20:06
|
|