Sign in to follow this  

OpenGL Cel-shading & actual lighting?

Recommended Posts

Gamble007    122
Ok, I'm hoping someone can help out with this question... My team and I are currently developing a game in OpenGL that we hope to cel-shade. Now, from what I understand, lighting has to be disabled in order to do this and you then use a light vector to simulate lighting from a particular direction in order to create the shading. My question is, can you somehow get "actual" lighting to work on cel-shaded models? The scenario that we're considering is having a spotlight moving across cel-shaded models or maybe characters walking underneath a streetlight with a spotlight projecting downward. Any help or advice would be greatly appreciated.

Share this post

Link to post
Share on other sites
tok_junior    229
Well, it IS possible, but only if you want to have every single object on the screen celshaded and untextured.
You can use gammaramp to divide the colors into 2-3 different intensities, but that affects the whole screen.
Just do it using shaders instead.

Share this post

Link to post
Share on other sites
Monder    993
Shaders are the way to go. One way to do cel-shading within shaders is to create your normal lighting shader, only intead of directly outputing the RGB triplet you get you use each component of it to look up a 1d texture, this texture is basically a gradient only it's only a few blocks of colour, i.e. you may have 4 or 5 blocks in it going from black to white. You then use the value looked from this 1d-texture as the final value for one of the components in the output colour. E.g something like this:

//calculate lighting as normal for this fragment
//ending up with a colour LightColour that you
//would directly output if not cel shading

OutColour.R = Tex1D(CelTex, LightColour.R);
OutColour.G = Tex1D(CelTex, LightColour.G);
OutColour.B = Tex1D(CelTex, LightColour.B);

//OutColour now contains the final colour to
//output from the fragment shader

Doing it this way basically allows you to do lighting however you want and have it in a cel-shading style.

[edit]Actually I'm not so sure how good it would look doing it this way, another (very similar) way is apply the same technique but to the diffuse and specular intensity terms (i.e. n dot l and n dot h respectively) instead (so you'd calculate the value as normal then use it to lookup into a texture to get a different value which is the one you'd actually use) [/edit]

[Edited by - Monder on October 3, 2004 12:59:23 PM]

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now