|
nonono the normals have been calculated already!!! (via SSE-asm)
I stored them in a group.
so iterating:
<br />
if (ModelToDraw.shownormals)<br />
{<br />
for (int k = 0; k < ModelToDraw.Objects[i].numVerts * 3; k += 3)<br />
{<br />
glBegin(GL_LINES);<br />
glVertex3f(ModelToDraw.Objects[i].Vertexes[k],<br />
ModelToDraw.Objects[i].Vertexes[k+1],<br />
ModelToDraw.Objects[i].Vertexes[k+2]);<br />
glVertex3f(ModelToDraw.Objects[i].Vertexes[k]+ModelToDraw.Objects[i].Normals[k],<br />
ModelToDraw.Objects[i].Vertexes[k+1]+ModelToDraw.Objects[i].Normals[k+1],<br />
ModelToDraw.Objects[i].Vertexes[k+2]+ModelToDraw.Objects[i].Normals[k+2]);<br />
glEnd();<br />
}<br />
}<br />
is no problem at all... just hopping around in the array like described above makes problems!
I don't want to calculate the normals again and again when I render the triangles!
|
|
|
|
|
have you considered using an interleved array? this allows you to put both vertexes and normals in the same grouping, color as well.
http://www.opengl.org/documentation/specs/man_pages/hardcopy/GL/html/gl/interleavedarrays.html[^]
are you having problems because of the slowdown on displaying normals? if so, you might consider moving the glBegin out of the loop. glBegin(GL_LINES) draws individual line segments every two vertices set. Which means you don't need to keep stopping and starting the set, you can group them all together.
<br />
glBegin(GL_LINES);<br />
for ()<br />
{<br />
glVertex3f();
glVertex3f();
}<br />
glEnd();<br />
if you don't mind loosing memory, keep paired buffers, one for vertex and normal separately, one for drawing the vertex normals as you referenced here. this is faster because you can use VBO buffers or vertex arrays to send the data in one unit down to the graphics card.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
zqueezy wrote: a little clearer what the problem is??
it looks relatively correct. the issue is actually in the storage structures of subfaces[] verses normals. Notice you are using an index offset to the vertex:
index = subFaces[i];
_tempArray=(float*)(((char*)k) + index * 12);
but when you get to the normal, you don't reference the fact that there is 3 floats
_tempArray=&(pNormal[i]);
you have a normal for every vertex, so you can reference it similarly to the vertex information from above:
index = subFaces[i];
_tempArray=(float*)(((char*)pNormal) + index * 12);
or if you don't like the pointer math you are using which is rather confusing, try this:
_tempArray=&pNormal[index*3]; // normals are 3 floats
and
_tempArray=&pVertex[index*3]; // vertexes are 3 floats
this reads much nicer and helps match the vertex/normal pairs. Generally speaking for vertex array buffers there is one normal per vertex. You can specify one normal per face, but not easily with a vertex array. A vertex array uses an interleaved or separate memory buffer to reference each color, vertex, normal in matching form. If you have 100 vertices, you have 100 color references, and you have 100 normals. Color reference can be 4 units, vertices 2,3 or 4 units, and normals are always 3 units. The units can be float, double, etc.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
Jeffry J. Brickley, You are a genius
you saved my life!!!
thanx e^256 times!
|
|
|
|
|
zqueezy wrote: You are a genius
No... I only know OpenGL well, no more, no less.  But thank you.
zqueezy wrote: you saved my life!!!
hehe, well, I doubt that... but thank you again.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
Hi
I want to add a toolbar to my application but when I use 'standard' CToolBar class I can't load my 32x32 24-bit bitmaps into it (Visual Studio 2003 resource editor converts them to some ugly-looking 8-colors bitmaps...) Is it possible to create nice looking toolbars (ie. like those in IE6) with handle for changing its position and locking/unlocking feature just using CToolBar class??
I also want to create my app menu "File Edit ..." on a toolbar like IE6 does. Is it possible using this base MFC control? If not, could someone point me to the article where I could find some more informations?
Thanks for any help.
|
|
|
|
|
PatrykDabrowski wrote: (ie. like those in IE6)
Look up CReBar.
|
|
|
|
|
|
|
PatrykDabrowski wrote: I can't load my 32x32 24-bit bitmaps into it (Visual Studio 2003 resource editor converts them to some ugly-looking 8-colors bitmaps...)
When you create the image list for the toolbar control, try building it like this...
CBitmap bitmap;
bitmap.LoadBitmap(IDB_TOOLBARBITMAP);
// (the '2' in the following call is the number of buttons in the bitmap)
m_ToolBarImageList.Create(32, 32, ILC_COLOR24|ILC_MASK, 2, 1);
// (RGB(0x00,0xFF,0x00) sets the transparent color to bright green)
m_ToolBarImageList.Add(&bitmap, RGB(0x00,0xFF,0x00));
|
|
|
|
|
Hi,
I get an error while running the application but i don't get when i debug it..the error is:
the exception Breakpoint
A breakpoint has been reached.
(0X80000003) occured in the application at location 0X7c901230
can anyone help me out with this?
thnx,
Priya
|
|
|
|
|
this happens in an ASSERT() when the condition is false...
|
|
|
|
|
i created xml file need to read, the file read the data (  ??? might be !!
not sure ,
when i print that data in the messagebox it gives the square box like.
hFile=CreateFile ( L"c:\\FileProperty.XML"
, GENERIC_READ | GENERIC_WRITE
, FILE_SHARE_READ
, NULL
, OPEN_EXISTING
, FILE_ATTRIBUTE_NORMAL
, NULL
);
if(hFile == INVALID_HANDLE_VALUE)
{
MessageBox(0,_T("File is not created"),_T("Create File"),0);
}
else
{
MessageBox(0,_T("File is created"),_T("Create File"),0);
}
bool bSucced=ReadFile(hFile,&szBuff,5000,&dwRecvLen,NULL);
szBuff[dwRecvLen] = '\0';
MessageBox(0,LPCWSTR(szBuff),L"Message",0);
how can i print that data in the string form?.
amit
|
|
|
|
|
Well, there seems to be a some errors in the code you posted.
You seem to have made the memory allocation for szBuff out-commented.
You assume that the file size doesn't exceed 5000 bytes.
I don't exactly get what you mean by "square box like", but I guess that you have enabled unicode for your build configuration and the first bytes in the "string" you want to display evaluates to a token that doesn't match a writeable character.
You even type cast to a LPCWSTR, which in this case doesn't have any effect since the MessageBox parameter is dependant on whether you have enabled unicode support or not.
The bottom line is that you have to be consistant: if you have enabled unicode support then you have to make sure that the file data is converted unless the file is already in unicode format, which I suspect it's not and that's what I think gives the result you've described.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
ya exactly , i forget to write that thing  its unicode thats why its come like
square box but how can do it in readable form?
because the messagebox show the unicode character so how to make that data to
read meaningful.
ok i made that file unicode then will it give me the data in the proper
readable form?
amit
|
|
|
|
|
amitmistry_petlad wrote: ok i made that file unicode then will it give me the data in the proper
readable form?
Technically: yes.
But, perhaps other applications that are supposed to use the file may no longer use it since you've changed the file format.
My suggestion:
Read the file as usual and then convert to unicode with ::MultiByteToWideChar().
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
But for that how can i convert my DWORD TO string look the following code:
std::string source(szBuff);
WCHAR w_Out[MAX_PATH];
MultiByteToWideChar(CP_ACP,MB_PRECOMPOSED,source.c_str(),(int)(source.length() + 1),w_Out,MAX_PATH);
MessageBox(0,LPCWSTR(w_Out),L"Message",0);
amit
|
|
|
|
|
amitmistry_petlad wrote: DWORD
What DWORD?
If you mean values read from the xml-file, you can convert them from textual format into DWORDs by calling ::wcstol().
I'm just guessing that the above is your problem. If it's not, describe it further.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
i think you might forget the previous code so  ,
look i explain with detail code .
WCHAR szBuff[5000]={}; // which i have declare global
//below is my function which used the gelobal variable szBuff read data from file
void _FilePersistandata()
{
HANDLE hFile;
DWORD dwFileSize, dwHighSize, dwBytesRead ;
DWORD dwRecvLen = 0;
hFile=CreateFile ( L"c:\\FileProperty.XML"
, GENERIC_READ | GENERIC_WRITE
, FILE_SHARE_READ
, NULL
, OPEN_EXISTING
, FILE_ATTRIBUTE_NORMAL
, NULL
);
if(hFile == INVALID_HANDLE_VALUE)
{
MessageBox(0,_T("File is not created"),_T("Create File"),0);
}
else
{
MessageBox(0,_T("File is created"),_T("Create File"),0);
}
bool bSucced=ReadFile(hFile,<big>&szBuff</big>,5000,&dwRecvLen,NULL);
szBuff[dwRecvLen] = '\0';
<code>
std::string source(szBuff);
</code>
WCHAR w_Out[MAX_PATH];
MultiByteToWideChar(CP_ACP,MB_PRECOMPOSED,source.c_str(),(int)(source.length() + 1),w_Out,MAX_PATH);
MessageBox(0,LPCWSTR(w_Out),L"Message",0);
}
let me know if something is wrong here ,then i'll change it.
amit
|
|
|
|
|
Instead of making assumptions about my memory, you should get your datatypes straight.
The things you claim to be DWORD is never DWORD in the code you've posted.
You declare szBuff as an array of WCHAR and WCHAR is a typedef that can be either 8 or 16 bits wide, but never 32 as a DWORD. In your configuration it's 16 bits wide since you've enabled support for unicode.
The only thing about szBuff that is 32 bits wide is its address you provide as argument in the call to ReadFile, but do not mix up an address with a 32 bit integer value.
ReadFile read the contents of a file in raw format, i.e. byte-wise, and puts it at a memory location you provide as argument, szBuff in your case. If the format of the data read doesn't fit your needs, convert it! In this case by calling MultiByteToWideChar providing the buffer with the data read as input and a pointer to a new location where you want the resulting data to be stored.
Bring up the memory debug window and have a look at your <codes>zBuff. After a successful call to ReadFile you will see the contents of your file there.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
|
 hello friends
char ch[10];
Cstring str ="Rahul"
memset(ch,0,10);///set ch to '\0';
memcpy(ch,str,5);
plz tell me where ch will be stored..on heap or on stack..thanks
Born To Code
|
|
|
|
|
as you don't allocate it with a new, it will be in the stack...
|
|
|
|
|
Both of your variables will be located on the stack. Even the 10 bytes referred to by ch will be located on the stack.
To use the heap you have to allocate memory by calling new in C++ or malloc or similar in C and you always get a pointer in return to be able to refer to the allocated memory.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
rahul.shendurnikar wrote: char ch[10];
CString str ="Rahul"
Both of those allocate the specified objects on the stack - that is, the array of char and the CString object will be allocated on the stack.
However, note the memory used by the CString object will be allocated on the heap, because that is how CStrings work. In other words, you are causing two kinds of allocations when really only one is required. Oh, and since heap allocation operations can raise exceptions, you should be assigning to that string object in a try/catch block just to be safe!
Note that you are getting really lucky by using memcpy to copy into the string object's buffer - that is generally not the correct way to get data into or out of a real object.
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
