Yeah but nearly all good engines state-sort anyway, they can sort their operations based on appearance. I don't think it should be that cumbersome a design within the X3D. Like everything else it should be fairly straightforward and somewhat human readable. I know that's a bit oxymoronic when it comes to 3D formats but VRML/X3D always did a pretty good job in that regard.<br>
<br>As a straw-man I would do something simple like multiple Shape nodes in a single group, with one Coordinate node to rule them all.<br><br>Tony<br><br><div class="gmail_quote">On Tue, Feb 5, 2013 at 3:53 PM, Michalis Kamburelis <span dir="ltr"><<a href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Keith Victor wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That general approach was a bit messy. I would have preferred that they<br>
specify the transition between the appearances, so it forces the author<br>
to place all the triangles ( or Faces ) that share the same appearance<br>
to be next to eachother. ( so the renderer does not have to do so )<br>
</blockquote>
<br></div>
That would be my preference too --- to keep faces with the same appearance together. Otherwise, browsers will have to reorder the faces first, for efficient rendering. Which may be time-consuming and troublesome (it depends on how much dynamic we allow there, but since IndexedFaceSet has set_coordIndex event then I guess we will want to also allow to change the appearance assignment at runtime).<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
MFInt32 appearanceTransition (index of the Face where we transition to<br>
the next appearance )<br>
<br>
</blockquote>
<br></div>
Instead of specifying the transition index, it could be more consistent to follow what existing TriangleFanSet.fanCount and TriangleStripSet.stripCount fields do (<a href="http://www.web3d.org/files/specifications/19775-1/V3.2/Part01/components/rendering.html#TriangleFanSet" target="_blank">http://www.web3d.org/files/<u></u>specifications/19775-1/V3.2/<u></u>Part01/components/rendering.<u></u>html#TriangleFanSet</a> , <a href="http://www.web3d.org/files/specifications/19775-1/V3.2/Part01/components/rendering.html#TriangleStripSet" target="_blank">http://www.web3d.org/files/<u></u>specifications/19775-1/V3.2/<u></u>Part01/components/rendering.<u></u>html#TriangleStripSet</a> ).<br>
<br>
So a field like<br>
<br>
MFInt32 appearanceCount<br>
<br>
For example<br>
<br>
appearanceCount [ 44, 123, 456 ]<br>
<br>
means that first 44 faces use the first appearance, the next 123 faces use the 2nd appearance, the next 456 faces use the 3rd appearance.<span class="HOEnZb"><font color="#888888"><br>
<br>
Michalis</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
X3D-Public mailing list<br>
<a href="mailto:X3D-Public@web3d.org" target="_blank">X3D-Public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/<u></u>listinfo/x3d-public_web3d.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Tony Parisi <a href="mailto:tparisi@gmail.com" target="_blank">tparisi@gmail.com</a><br>CTO at Large 415.902.8002<br>
Skype auradeluxe<br>Follow me on Twitter! <a href="http://twitter.com/auradeluxe" target="_blank">http://twitter.com/auradeluxe</a><br>Read my blog at <a href="http://www.tonyparisi.com/" target="_blank">http://www.tonyparisi.com/</a><br>
<br>Read my book! <i>WebGL, Up and Running</i><br>
<a href="http://shop.oreilly.com/product/0636920024729.do" target="_blank">http://shop.oreilly.com/product/0636920024729.do</a><br><a href="http://www.amazon.com/dp/144932357X" target="_blank">http://www.amazon.com/dp/144932357X</a><br>
<br>