Comments for Lighthouse3d.com

Comment on Setup Basics by Nathan

Nathan — Mon, 20 Feb 2012 17:05:38 +0000

Thanks for the instruction on removing the console window! That was huge for me. I don’t know why this isn’t in more tutorials as I think most people would be using Microsft Visual Studio.

Comment on GLUT Tutorial by anonymous

anonymous — Mon, 20 Feb 2012 12:30:38 +0000

Hi there, Thank you very much for taking the time to write this. Cheers, it’s big help. thanks again.

Comment on Keyboard Example: Moving the Camera by %$&#YEAH

%$&#YEAH — Mon, 20 Feb 2012 08:32:41 +0000

%$&# yeah… This is best tutorial I have ever got… THANKS MAAAAN!!!!

Comment on Importing 3D Models with Assimp by John

John — Sat, 18 Feb 2012 13:38:18 +0000

i am getting an unhandled exception
Unhandled exception at 0x01e6e620 in Adv_Graphics.exe: 0xC0000005: Access violation reading location 0×00000000.

its in the line 26 of the Model Render code
// draw
glDrawElements(GL_TRIANGLES,myMeshes[nd->mMeshes[n]].numFaces*3,GL_UNSIGNED_INT,0);

pls help

Comment on Importing 3D Models with Assimp by John

John — Sat, 18 Feb 2012 12:55:44 +0000

I was trying to run the program. but i got a breakpoint

#undef _CrtDbgBreak

/* These methods don’t need a separate
wchar version. Hence they need to be compiled only once from
the original file */

_CRTIMP void _cdecl _CrtDbgBreak(
void
)
{
__debugbreak();
}

can u please help

Comment on Data Types and Variables by ARF

ARF — Sat, 18 Feb 2012 00:53:06 +0000

Yes there is, but it is far different from reading back a variable. You can write values to textures, read back the frame buffer, use transform feedback to store values in buffers, among other possibilities

Comment on Preparing the window for a reshape by ARF

ARF — Sat, 18 Feb 2012 00:51:18 +0000

Hi,

Have looked at the code in the sample? to replace the projection matrix just do as follows:

1. Declare vsml as a global variable
VSMathLib *vsml;

2. Init VSMathLib stating which variable in your shader corresponds to the projection matrix, for instance:
vsml->setUniformName(VSMathLib::PROJECTION, “projectionMatrix”);

3. Whenever you want to build the matrix just call it as you would call gluPerspective:
vsml->loadIdentity(VSMathLib::PROJECTION);
vsml->perspective(53.13f, ratio, 0.1f, 10000.0f);

4. To send the matrices (projection and any others you are using) to the shaders, before the glDraw call invoke the method:
vsml->matricesToGL();

Hope this helps

Comment on Data Types and Variables by Nikola

Nikola — Fri, 17 Feb 2012 00:12:14 +0000

It seems to me that all communication with shaders is going only in one direction – from our program to shaders. How can I read some data that was created by shaders? For example, If I need to know the value of gl_Position variable how can I retrieve it?

Is there a way a shader could write data to a piece of memory that could be read from the “main” program?

Comment on GLSL Core Tutorial – Geometry Shader by Dave

Dave — Thu, 16 Feb 2012 01:34:27 +0000

I am with kaoD. I figured that geometry shaders were used for displacement maps (amongst other things). I imagine that the max_vertices parameter in the out layout comes into play here, so are there maximums on what that parameter can be set to?

Also, does anyone have an example of using the invocations parameter of the in layout? It’s not obvious how this parameter works, or where you would want to use it. Does it recursively process the primitives? (seems like no if the out primitive type is different than the in primitive).

Comment on The Code So Far III by squaknmoose

squaknmoose — Thu, 16 Feb 2012 00:02:22 +0000

It worked for me by changing the code to:

case ‘s’:
if (!menu_Flag)
glutChangeToMenuEntry(2, “Shrink”, shrinkMenu);
glutChangeToSubMenu(2, “Shrink”, shrinkMenu);
break;
case ‘c’:
if (!menu_Flag)
glutChangeToMenuEntry(2,”Color”, colorMenu);
glutChangeToSubMenu(2, “Color”, colorMenu);

it seems to have fixed the issue.