• Advertisement
Sign in to follow this  

OpenGL optimal tessellation for use with standard lights.

This topic is 3626 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, Im looking at using the standard lights and using tessellation to get a good result, but I cant seem to come up with or find a particularly good routine. I have alread split the polygon at the point perpendicular to the light source, and done some more splitting but although it is a fair bit better it is obviously not an optimal solution. I think I need to keep splitting each polygon along a line of same brightness if the difference in brightness acrross the polygon is significant. im looking to do this within opengl 1.1. has anyone got any good solutions they know of? thanks.

Share this post


Link to post
Share on other sites
Advertisement
Hmm, I remember having this problem way back, when I wrote my first radiosity solver that would use meshed vertex colours... *shudder* Oh dear, how could I ever live without PRT maps ;)

Anyway, the basic idea is to analyse the gradients over a triangle, and split along the direction where the gradient function becomes too non-linear. Or in other words, where a linear approximation of the gradient function yields an error term larger than some quality threshold you define (or the user).

Keep in mind that linear gradients can be very well represented by Gouraud style shading, so relying on gradient differences alone will get you too much tesselation where you don't really need it. And it can easily miss triangles that really need more tesselation (imagine a blob of light at the center of a face, with all three vertices black).

Obviously, in practice this is not that easy. You have to take special cases into account, such as light sources that only affect the interior or a single edge of a face. Or shadow boundaries, penumbra, and the like.

This stuff is called "discontinuity meshing", a Google search on these terms will get you plenty of information.

That said, may I ask why you would want to do this ? Good adaptive meshing algorithms can quickly become very complex. There are plenty of other, and better methods like lightmaps (also works on OGL 1.1), and a virtually unlimited choice of per-pixel lighting methods.

Share this post


Link to post
Share on other sites
per pixel ligting is cool, ive tried shaders to do it, but can it be done without shaders / I need a solution that will work on limited hardware,
ie no pixel shader/ opengl 1.1

I was thinking tessellation would be an easy method, but like all things turns out to be more dificult than i thought would be the case with just choping up some triangles wich in itself is fairly easy.

I looked for discontinuity meshing and theres loads of hits, but mostly descriptions, are there any routines about?

I would of thought lightmaps still require some effort ...

Share this post


Link to post
Share on other sites
If you have register combiners available, you can search the internet for Ron Frazier, he made a pretty amazing (well, amazing for that time) per pixel lighting demo a long, long time ago which ran on really, really old hardware. There was a long comprehensive article with that demo too.

Other than that, I think you might be able to do some nasty trickery using ARB_texture_env_dot3 to get something like N dot L lighting... but I'd rather bite off my arm than attempt to do that (shaders are so much nicer).

Share this post


Link to post
Share on other sites
well ive spent a while going through some of those hits,
not seen much in the way of anything close to code,
but ive come up with an idea for tessellation anyway, ...

take all the lines between any two points wich spilt a quad or larger polygon
and use the one with the highest non linearity to split it. so you eventually end up with triangles.

then do the same sort of thing with remaining triangles using one point and mid point of opposite side, stopping when the worst linearity is good enough.

just need to come up with a good way to measure non linearity, maybe measure linearity along a line that runs through the mid point of the splitting line through the closest point to the light.

im not sure if register combiner are availabale but i doubt it very much.

Share this post


Link to post
Share on other sites
Ive finnally managed to get a fairly simple tessellation working, and it looks reasonable.

I just compute the actual correct lighting at the vertexes and at the midpoints of each line, then compare the interpolated, value, and split the polygon if theres a significant error.

I also do the same for the center, and I also intend to do the same for each point on the polygon closest to each light.

took me quite a while cos I just generally made a hash of it to start with lol,
I also tried to do it other ways by investigating the linearity but that was too cumbersom and not very effective, actually computing the interpolated value and comparing to the correct value at specific points proved far more effective and simpler.

it works for 8 lights, now all I have to do is extend it to more lights, by changing the lights in use to the nearest ones.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement