Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

In an IndexedFaceSet or Extrusion with caps, why is my L-shaped, T-shaped, arrow-shaped, other concave polygon drawn incorrectly?

April 26, 2017caps concave drawn Extrusion incorrectly l-shaped polygon t-shaped

0

Posted

In an IndexedFaceSet or Extrusion with caps, why is my L-shaped, T-shaped, arrow-shaped, other concave polygon drawn incorrectly?

1 Answer

0

Posted

If the polygon (or extrusion cross section) is not convex, be sure to specify convex FALSE. If the “convex” field is TRUE (the default), the browser uses a faster triangulation algorithm which is only guaranteed to be correct within the convex hull of a concave polygon. Navigation speed is slower than other browsers. Cosmo Player 2.x strictly interprets the NavigationInfo node’s “speed” field; this is covered in the Release Notes under “Navigation Speed”. Also, see below under User Interface Issues for more info. Using a PlaneSensor I get a jump in the z direction. This was a bug in the beta 1 release of Cosmo Player 2.0. It’s fixed in the final version of 2.0, and in Cosmo Player 2.1. My HTML link (or VRML Anchor) to a URL like “filename.wrl#ViewpointName” doesn’t take me to the specified Viewpoint! This was a known bug in Cosmo Player 2.0, but it’s fixed in Cosmo Player 2.1. (According to the VRML spec, this URL syntax is supposed to cause the specified Viewpoint to be bound initiall