Sign in to follow this  
CDProp

OpenGL Implementing Simplex Noise with Shaders

Recommended Posts

I was wondering, how is this typically done? All of the implementations I can find have been in C or Java. Some parts of the algorithm, as-is, aren't supported by the shader profile that I'm using (I'm running on a GeForce 6800, using OpenGL 2.1). So, for instance, when it comes to using the bitwise & as a quick modulus, it tells me: error C5508: the operator "&" is not supported by this profile And I have a permutation table (array of ints), and another array of gradients, however I cannot index into them from the fragment shader. I am told: error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable So I suppose I could replace the bitwise & with a normal modulus (%). When I try, I don't get any compiler errors, but I can't run my shader yet to test it because compilation fails on those array look-ups. I guess I could replace those array lookups with texture lookups? I'm pretty sure this would work, but is it the best way or is it a naive method? Also, bonus question: I see a lot of people confused about how to create tiling simplex noise. Shouldn't this be trivial? The pattern repeats itself every 256 units anyway, so just render something that is 257x257?

Share this post


Link to post
Share on other sites
Quote:
Original post by Geometrian
Bitwise operators aren't yet supported.


They in GL 3.0 or the GL_EXT_gpu_shader4 extension. But just using a texture is fine.

Share this post


Link to post
Share on other sites
Draw a noise texture. Most painting packages have a noise function. If you don't just want random noise, you could produce the textures yourself with a Perlin noise implementation eventually. There is ready-to-use code for that on the net.

Then in your shader read the texture. Probably you want the texture coordinates varying. You could use the model original texture coordinates and shift them with a timer-parameter and/or vertex/pixel position. If you don't need to randomize for each pixel, you can do the texture fetch also in the vertex shader already, if you have support for shader model 3.0.

Share this post


Link to post
Share on other sites
Just a quickie: SM3 is not a defacto way to assume VTF, so don't rely on that.

I've realised this to my horror recently whilst implementing grass. A lot of DX10 (or better) cards will do VTF properly under DX9 drivers, but not all, or only handle R32F or R16F (and not even both).

My Radeon 4800, which isn't brand new but is hardly a piece of crap either, will only do R32F for example. The DX9 cards we have at work won't do it at all, which kinda sucks, even though they support all other SM3 features.

You really need to check the texture compat stuff as I'm sure the situation under OGL can't be much/any better.

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  

  • Forum Statistics

    • Total Topics
      627726
    • Total Posts
      2978816
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      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. 
  • Popular Now