<div dir="ltr">Ah. I wonder if that has something to do with remote rendering. Let's try disabling remote rendering and then export the state. Can you try this:<div><br></div><div>+ from Edit | Settings dialog (on Mac, I believe this is under the ParaView menu itself), open the "Render VIew" page and select "Server" page. There, uncheck "Remote Render Threshold" (image attached). Now all rendering will happen locally on the client side. </div>
<div><br></div><div>+ Now try and export the X3D (you may want to interact with the  just to make sure that a render happens before you export the x3d state). Any change?</div><div><br></div><div>Utkarsh</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Nov 25, 2013 at 12:03 PM, Cook, Rich <span dir="ltr"><<a href="mailto:cook47@llnl.gov" target="_blank">cook47@llnl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
Yep. Â
<div>I understand about SC. Â Let me catch you up to save some time. Â </div>
<div>In summary, when I render x3d objects from paraview that are exported from scenes rendered in serial, everything is fine.  But when rendering in parallel in ParaView, the x3d exporter hoses the colors AFAICT. </div>
<div><br>
</div>
<div>I've attached a screen shot of what your "sphere" looks like in a simple scene in blender. Â <br>
<br>
</div>
<div><img height="688" width="551" src="cid:5FB2216F-B85A-4474-BF39-F88DD9E45781@llnl.gov"></div>
<div><br>
<div>
<div>On Nov 24, 2013, at 4:05 PM, Utkarsh Ayachit <<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></div>
<div>Â wrote:</div>
<br>
<blockquote type="cite"><div><div class="h5">Rich,<br>
<br>
As Berk mentioned in another email, several members of the ParaView<br>
development team were at SuperComputing last week. Since there are<br>
several emails floating around about X3D, and I am not a very good<br>
summarizer of emails, I am not sure where things stand, so let's start<br>
at the start.<br>
<br>
I've attached a simple X3D output generated from the attached ParaView<br>
state file (for ParaView 4.1.0-RC1). I don't have much experience with<br>
Blender and hence haven't been able to show the result as expected in<br>
Blender. But if you don't mind, can you try loading the X3D file to<br>
see if it renders as expected (ParaView rendered image attached)? It's<br>
a very simple geometry with 5 points colored with 5 different colors.<br>
Let's try to see if the exported X3D file is bad in the first place.<br>
Just looking at the file, the contents seem reasonable to me.<br>
<br>
Utkarsh<br>
</div></div><span><Sphere.x3d></span><span><ExpectedRendering.png></span><span><StateFile.pvsm></span></blockquote>
</div><div class="im">
<br>
<div>--Â <br>
âœRichard Cook   <br>
✇ Lawrence Livermore National Laboratory<br>
Bldg-453 Rm-4024, Mail Stop L-557 Â Â Â Â <br>
7000 East Avenue, Â Livermore, CA, 94550, USA<br>
☎ (office) <a href="tel:%28925%29%20423-9605" value="+19254239605" target="_blank">(925) 423-9605</a>   <br>
☎ (fax) <a href="tel:%28925%29%20423-6961" value="+19254236961" target="_blank">(925) 423-6961</a><br>
---<br>
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.<br>
(opinions expressed herein are mine and not those of LLNL)<br>
<br>
<br>
</div>
<br>
</div></div>
</div>
</blockquote></div><br></div>