# OpenGL Two-sided lighting for DirectX

## Recommended Posts

OpenGL uses glLightModelf to specifiy two sided lighting of polygons. Is there an equivalent for DirectX? Currently, I've had to recalculate face normals if I am rotating a primitive. This can be quite time consuming if it's a surface model with thousands of polygons.

##### Share on other sites
D3DCULL_NONE using the SetRenderState function. This will cause all triangles to render back and front.

device->SetRenderState(D3DRS_CULLMODE, D3DCULL_NONE);

EDIT* Not sure if the above is what you are looking for. Haven't tested if turning off culling will affect the lighting on the backfaces. I am assuming that the lighting will affect the triangle normally, but this may not be the case. I'm not in a place where I can test it so, I hope it helps :)

Webby

##### Share on other sites
Webby:
Thanks for the reply. I'm already setting the CULLMODE off. It does not appear to affect the lighting. Polygons that are not facing the light source appear as dark.

##### Share on other sites
If I understand you correctly, you want to light each side differently.

If that is the case, then there is no way to avoid drawing everything twice -- once for each side. You normally would have to reverse all the normals, but if you are using only direction and ambient lights, then you can change the direction of the lights when drawing the opposite side instead. Note that if you draw twice, you have to turn the culling back on and switch it for each side.

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627653
• Total Posts
2978440
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 12
• 22
• 13
• 33