[X3D-Public] Support for submeshes?

[Tony Parisi]

Hmm maybe my rendering knowledge is out of date. Well if you are correct
than the only reason to have X3D support submesh materials is so that it's
truly one object for the purposes of picking and so on. And even then maybe
it's only an efficiency, since the input sensors only return hitPoint,
hitNormal etc. and those values would be the same whether you have one or
more Shape nodes in that part of the hierarchy.

Tony

On Tue, Feb 5, 2013 at 10:27 AM, Michalis Kamburelis <
michalis.kambi at gmail.com> wrote:

> Tony Parisi wrote:
>
>> I guess if it's just for interchange, Michalis and Cecile are correct;
>> you can use Shape nodes all you want. It just won't render the way
>> expected in a compliant X3D player (you'll likely see seams).
>>
>
> Why? You will not see seams if you use exactly the same sets of
> coordinates, sharing them by DEF/USE, for all shapes. GPUs guarantee a
> proper pixel fill here, if all the shapes are under the same
> transformation, and rendered internally by the same method (e.g. all by
> OpenGL display lists, or none by OpenGL display lists, all by shaders or
> none by shaders).
>
> Otherwise, the seams would be unavoidable, regardless if X3D has a special
> node for submeshes or not.
>
> Michalis
>



-- 
Tony Parisi                             tparisi at gmail.com
CTO at Large                         415.902.8002
Skype                                     auradeluxe
Follow me on Twitter!             http://twitter.com/auradeluxe
Read my blog at                     http://www.tonyparisi.com/

Read my book! *WebGL, Up and Running*
http://shop.oreilly.com/product/0636920024729.do
http://www.amazon.com/dp/144932357X
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20130205/77c6885e/attachment.html>