Jump to content

  • Log In with Google      Sign In   
  • Create Account


Back face of a pyramid is missing


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
6 replies to this topic

#1 Hseptic   Members   -  Reputation: 146

Like
0Likes
Like

Posted 07 June 2012 - 03:37 PM

I'm trying to texture map a pyramid. However, what should be the back side of the pyramid is somehow missing from view.

Here is a view from the front. This is the default orientation when my demo first executes.
mypyramid1.PNG
As we rotate about the y axis to get a view of the back face of the pyramid, we find that the back face is missing! Instead, we see that the diagonal cross section is texture mapped. Obviously, the viewer should never be able to see inside the pyramid much less have it texture mapped.
mypyramid2.PNG
Here is a map of the vertices for clarity.
pyramid0.PNG
Here is some code.
void PyramidDemo::buildPyrGeometry()
{
// Create the vertex buffer.
HR(gd3dDevice->CreateVertexBuffer(24 * sizeof(VertexPNT), D3DUSAGE_WRITEONLY,
  0, D3DPOOL_MANAGED, &mPyrVB, 0));
// Write Pyr vertices to the vertex buffer.
VertexPNT* v = 0;
HR(mPyrVB->Lock(0, 0, (void**)&v, 0));
D3DXVECTOR3 pyrV0( 0.0f,  0.0f,  0.0f);
D3DXVECTOR3 pyrV1(-1.0f, -1.0f, -1.0f);
D3DXVECTOR3 pyrV2( 1.0f, -1.0f, -1.0f);
D3DXVECTOR3 pyrV3(-1.0f, -1.0f,  1.0f);
D3DXVECTOR3 pyrV4( 1.0f, -1.0f,  1.0f);
D3DXVECTOR3 fn_f;
D3DXVECTOR3 fn_b;
D3DXVECTOR3 fn_l;
D3DXVECTOR3 fn_r;
faceNormal(&pyrV0, &pyrV2, &pyrV1, &fn_f);
faceNormal(&pyrV0, &pyrV3, &pyrV4, &fn_b);
faceNormal(&pyrV0, &pyrV1, &pyrV3, &fn_l);
faceNormal(&pyrV0, &pyrV4, &pyrV2, &fn_r);

v[0] = VertexPNT(pyrV1.x, pyrV1.y, pyrV1.z, fn_f.x, fn_f.y, fn_f.z, 0.0f, 1.0f);
v[1] = VertexPNT(pyrV0.x, pyrV0.y, pyrV0.z, fn_f.x, fn_f.y, fn_f.z, 0.0f, 0.0f);
v[2] = VertexPNT(pyrV2.x, pyrV2.y, pyrV2.z, fn_f.x, fn_f.y, fn_f.z, 1.0f, 0.0f);

v[3] = VertexPNT(pyrV4.x, pyrV4.y, pyrV4.z, fn_b.x, fn_b.y, fn_b.z, 0.0f, 1.0f);
v[4] = VertexPNT(pyrV0.x, pyrV0.y, pyrV0.z, fn_b.x, fn_b.y, fn_b.z, 0.0f, 0.0f);
v[5] = VertexPNT(pyrV3.x, pyrV3.y, pyrV3.z, fn_b.x, fn_b.y, fn_b.z, 1.0f, 0.0f);

v[6] = VertexPNT(pyrV1.x, pyrV1.y, pyrV1.z, 0.0f, 1.0f, 0.0f, 1.0f, 1.0f);
v[7] = VertexPNT(pyrV2.x, pyrV2.y, pyrV2.z, 0.0f, 1.0f, 0.0f, 0.0f, 1.0f);
v[8] = VertexPNT(pyrV4.x, pyrV4.y, pyrV4.z, 0.0f, 1.0f, 0.0f, 0.0f, 0.0f);
v[9] = VertexPNT(pyrV3.x, pyrV3.y, pyrV3.z, 0.0f, 1.0f, 0.0f, 1.0f, 0.0f);

v[10]= VertexPNT(pyrV4.x, pyrV4.y, pyrV4.z, fn_l.x, fn_l.y, fn_l.z, 0.0f, 1.0f);
v[11]= VertexPNT(pyrV0.x, pyrV0.y, pyrV0.z, fn_l.x, fn_l.y, fn_l.z, 0.0f, 0.0f);
v[12]= VertexPNT(pyrV1.x, pyrV1.y, pyrV1.z, fn_l.x, fn_l.y, fn_l.z, 1.0f, 0.0f);
v[13]= VertexPNT(pyrV2.x, pyrV2.y, pyrV2.z, fn_r.x, fn_r.y, fn_r.z, 0.0f, 1.0f);
v[14]= VertexPNT(pyrV0.x, pyrV0.y, pyrV0.z, fn_r.x, fn_r.y, fn_r.z, 0.0f, 0.0f);
v[15]= VertexPNT(pyrV4.x, pyrV4.y, pyrV4.z, fn_r.x, fn_r.y, fn_r.z, 1.0f, 0.0f);

HR(mPyrVB->Unlock());

// Create the vertex buffer.
HR(gd3dDevice->CreateIndexBuffer(36 * sizeof(WORD), D3DUSAGE_WRITEONLY,
  D3DFMT_INDEX16, D3DPOOL_MANAGED, &mPyrIB, 0));
// Write Pyr indices to the index buffer.
WORD* i = 0;
HR(mPyrIB->Lock(0, 0, (void**)&i, 0));

i[0]  = 0; i[1]  = 1; i[2]  = 2;
i[3]  = 3; i[4]  = 4; i[5]  = 5;
i[6]  = 6;   i[7] = 7; i[8]  = 8;
i[9]  = 8; i[10] = 9; i[11] = 6;
i[12] = 10; i[13] = 11; i[14] = 12;
i[15] = 13; i[16] = 14; i[17] = 15;

HR(mPyrIB->Unlock());
}
void PyramidDemo::faceNormal(D3DXVECTOR3* v0, D3DXVECTOR3* v1, D3DXVECTOR3* v2, D3DXVECTOR3* n)
{
D3DXVECTOR3 u = *v1 - *v0;
D3DXVECTOR3 v = *v2 - *v0;
D3DXVec3Cross(n, &u, &v);
D3DXVec3Normalize(n, n);
}
I tried to list the vertices of the back face in a counterclockwise winding order. I tried disabling culling, and it still is missing. What could be wrong?

Sponsor:

#2 MJP   Moderators   -  Reputation: 11010

Like
0Likes
Like

Posted 07 June 2012 - 04:27 PM

From your picture it doesn't look like your back triangle isn't missing, but rather one of its indices are wrong. See how the triangle connects to the bottom right corner and the top of the pyramid, but then connects to the front left corner instead of the back left corner?

Edited by MJP, 07 June 2012 - 04:27 PM.


#3 Hseptic   Members   -  Reputation: 146

Like
0Likes
Like

Posted 07 June 2012 - 04:42 PM

Yeah, I checked the indices but didn't find anything unusual. I'll double check though...

#4 jefferytitan   Crossbones+   -  Reputation: 2031

Like
0Likes
Like

Posted 07 June 2012 - 04:54 PM

Agreed, or similarly the normal is facing the wrong way and it is being back-face culled. That could also be related to indices; the order that you specify them.

#5 Hseptic   Members   -  Reputation: 146

Like
0Likes
Like

Posted 07 June 2012 - 06:34 PM

Like I said, I disabled culling and it still won't show. Also, I tried specifying the vertices that make up the back face of my pyramid both clockwise and counterclockwise, and it still didn't do what I wanted. Do both the vertices and the indices that correspond to those vertices have to be in a special order?

#6 Tom KQT   Members   -  Reputation: 1568

Like
0Likes
Like

Posted 08 June 2012 - 12:39 AM

That really doesn't look like windingorder-related problem (face culling).
Maybe you should give us another picture, from a slightly different camera orientation, but my best guess at this moment is this:

Let's name the vertices one the second picute (the wrong one) this way - the top one is T, the bottom square consist of A (closer to us, left), B (closer to us, right), C (further from us, left), D (further from us, right).
I would bet that the triangle which should form the front face and should be made of T, B, A is instead made of T, B, C.
But as I said, another camera angle would confirm/disprove it.

And if I'm right, then it really means that you have some error in your code. Most probably in the indices, even though you double-checked it already.

Edited by Tom KQT, 08 June 2012 - 12:41 AM.


#7 Inukai   Members   -  Reputation: 1297

Like
0Likes
Like

Posted 08 June 2012 - 03:09 AM

i[12] = 10; i[13] = 11; i[14] = 12;


These indices are looking like a diagonal (v1, v0, v4).

However, I could be wrong since I'm quite new to this 3d stuff.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS