Databases
StackOverflow2013
Postsdbo
POSupporting between GL versions 3.1 and 4.x
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSupporting between GL versions 3.1 and 4.x
    primarykey
    data
    text
    <p>Since I've been studying OpenGL, I've been running into a bit of dilemma: while I have a good video card which supports GL 4.3 (<code>nVidia GTX 550 ti</code> model), my laptop is running off of integrated graphics (Intel HD 3000, from an <code>i5-2410M</code> to be exact), which runs version 3.1. I have no idea if this card is even capable of supporting OpenGL 3.2. </p> <p>Either way, if it turns out that a driver update is all that's needed for core i3/i5 processors to support OpenGL 3.2+, I'm still not sure where I should look or what <em>exactly</em> I need to pay attention to in order support between 3.x and 4.x.</p> <p>For example, AFAIK GLSL 1.4 doesn't support a shader which uses the <code>layout(location=x) in blah blah</code> feature. But, does GLSL 1.5? </p> <p>What about preprocessor directives in C/C++ <em>as well as</em> GLSL which I can use to distinguish between what features work with what? Or, is it more recommended (in either GLSL's or C/C++'s case) to just write completely separate header/source/shader files which take care of this?</p> <p>Since I only plan to be supporting 3.x to 4.x, I know this should be simpler than it very well could be.</p> <p><strong>Update</strong></p> <p>After a recent driver update on my laptop, it turns out that, as Nicol Bolas also stated, there currently is not (and likely won't ever be) any support for 3.2 on Intel 3000 cards. Therefore, to make this question simpler, I'd like to know what shading language features (be it in an answer or an external URL) I can and cannot implement on version 3.1 in comparison to 3.3 and above. Any OpenGL specific C/C++ features/functions which pertain to this would also be appreciated.</p> <p>My goal is to basically be able to know what I have to do in order to mediate between the project I'm working on (which is currently using a GL 4.0 context) to be compatible with a 3.1 context.</p> <p>If anything is still unclear I'll update accordingly. Thanks.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USzeboidlund
    1. USzeboidlund
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSupporting between GL versions 3.1 and 4.x
      1. USmeklarian
      1. VTFavorite
    1. CO"*I have no idea if this card is even capable of supporting OpenGL 3.2.*" It's *capable* of it. It probably never will, because Intel won't update the drivers for it, but the hardware is capable of it. Indeed, it provides 3.2 support under MacOSX.
      singulars
      1. POSupporting between GL versions 3.1 and 4.x
      1. USNicol Bolas
    2. COIt's a bit unclear as to what exactly you're asking for. The only question I can see here is what version of OpenGL provides explicit vertex attribute index specification.
      singulars
      1. POSupporting between GL versions 3.1 and 4.x
      1. USNicol Bolas
    3. CO@NicolBolas question updated.
      singulars
      1. POSupporting between GL versions 3.1 and 4.x
      1. USzeboidlund
 

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