Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd say probably not number 1.. you have a limited number of registers for shader uniforms, which varies by card. You can query GL_MAX_FRAGMENT_UNIFORM_COMPONENTS to find out your limit. On newer cards it runs into the thousands, e.g. a Quadro FX 5500 has 2048, apparently. (http://www.nvnews.net/vbulletin/showthread.php?t=85925). It depends what hardware you want it to run on, and what other uniforms you might want to send to the shader too.</p> <p>Number 2 could be made to work depending on your requirements. Sorry for the vagueness here, hopefully someone else can give you a more precise answer, but you must be explicit in how many texture calls you make in older shader model cards. It also depends how many texture reads you want to do per fragment, you probably wouldn't want to be trying to read 1000's of elements per fragment, again, depending on your shader model and performance requirements. You could pack values into RGBAs of a texture, giving you 4 reads per texture call, but with random access as a requirement, this might not help you.</p> <p>I'm not sure about number 3, but I'd suggest maybe looking at UAV (unordered access views) although i think that is DirectX only, with no decent openGL equivalent. I think there's an nVidia extension for openGL, but again you then restrict yourself to a pretty strict minimum spec.</p> <p>It's unlikely that passing 1000's of items of data to your fragment shader is the best solution to your problem.. perhaps if you gave more details on what you're trying to achieve you may get alternative suggestions?</p>
    singulars
    1. This table or related slice is empty.
    1. POPassing a list of values to fragment shader
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHybrid
    1. USHybrid
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. I would probably do a single read from this array per fragment. It is a list of values that influence the final fragment value, and when I think of it that way perhaps a 1d-texture is the natural way to go. Only problem is that I'd rather have exact integer look-up instead of a floating point texture coordinate.
      singulars
      1. PO
      1. USVille Krumlinde
    2. COFor a single read per fragment, it sounds like a texture is definitely the way to go, yep. As long as you use nearest filtering on your 1D texture, you'll always receive a value that matches one you put into your texture (subject to floating point and texture format precision errors, of course)
      singulars
      1. PO
      1. USHybrid
    3. CO@VilleKrumlinde If you want plain array access using integer index, TBOs are the way to go (at least on GL3/DX10 hardware). Look at my answer.
      singulars
      1. PO
      1. USChristian Rau
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload