normals

I was playing around with WEBGL and today and a encountered a problem with my cube's vertex normals . I checked my code with a cube mesh from internet and it works great. The thing is that the cube from internet has 24 vertices (4 for each face * 6 faces) which is way to much for I cube I think. FIDDLE MY CUBE | FIDDLE INTERNET CUBE (my code stars at line 200) I figured out that a cube needs no more than 8 vertices and 12 indices. But when I render my cube I get a weird shape on screen like this(because of the normals?): This is the cube form internet in almost the same rotation position as my

I'm trying to calculate smooth normals for a cone. In looking around for code samples and explanations, I consistently come across directions for face normals. I've posted a couple pictures below of what I'm doing. The first -- which basically just normalizes the vertex position -- gives me decently smooth shading, but the edges are "missing" and the bottom face isn't solid. The second has edges, but the shading is flat (face normals) and my light isn't reflecting off of them correctly. The cone is built out of GL_TRIANGLES. Click the images for larger versions. (source: bantherewind.com )

First of all let me clear .. I am not asking about 2D mesh, to determine the winding order of 2D mesh its very easy with normal-z direction. Second is, I am not asking any optimized algorithm, I do not worry about the time or speed, I just want to do it with my mesh. When I triangulate a 3D object using Greedy Projection Triangulation algorithm, This problem happens. check the attached images. If I apply 2D approaches to this model using "Calculate Signed Area" or "Cross production of AB and BC vectors of a triangle", it only solves the 2D mesh but how about a 3D mesh? First we need to check

I have been searching around and haven't found any really good answer to my question yet.. The thing is that I have this sphere.. just a basic sphere, and I want to flip the normals so the sphere gets the sort of "hollow/carved effect" and then plater on apply my textures to the "inside" of the sphere. any ideas of how to flip the normals? Also.. if its not possible to do this in three.js.. would it be possible to import a model where the normals are already flipped and get the effect I'm looking for? You can flip the normals in your geometry by reversing the winding order of your faces. You

I have a THREE.PlaneGeometry , with ComputeFaceNormals() . I create two meshes using this geometry, with different rotations applied to them. I want to compute the two angles between the camera and the two meshes central face normal. It should be : vLocalCamera = vCamera.position - mesh1.position; mesh1.normal() . vLocalCamera = cos(angle); The problem is that I don't know how to get the mesh normal in world coordinate (from geometry and mesh rotation) with three.js API If you want to convert a face or vertex normal, normal , from local space to world space, you do it like so: var normalMatrix

I want to display mesh models in OpenGL ES 2.0, where it clearly shows the actual mesh, so I don't want smooth shading across each primitive/triangle. The only two options I can think about are Each triangle has its own set of normals, all perpendicular to the triangles surface (but then I guess I can't share vertices among the triangles with this option) Indicate triangle/primitive edges using black lines and stick to the normal way with shared vertices and one normal for each vertex Does it have to be like this? Why can't I simply read in primitives and don't specify any normals and somehow

My Task I currently creating a terrain for Unity3D which is specialized for mobile-devices with low memory for a running app. Allowing a terrain with a size of 15.000 x 15.000 kilometers and a height from -1.000 meters to 10.000 meters and it's only limits are the space on the hard disk. Situation Everything is running fine right now except that the normals between different meshes ( each mesh has a subdivision level ) are not calculated correctly. Here are two pictures which visualize the problem: The problem only occurs on a transition from one subdivision level to another. If both mesh have