Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Page 47 of 63 FirstFirst ... 37454647484957 ... LastLast
Results 461 to 470 of 623

Thread: The ARB announced OpenGL 3.0 and GLSL 1.30 today

  1. #461

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod


  2. #462
    Member Regular Contributor
    Join Date
    Mar 2007
    Location
    California
    Posts
    396

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    Yeah, I am learning about the Larabee stuff. There's supposed to be a dev kit out soon from Intel. I'm very interested in this. My gut says it won't work out, but I hope it does. I want to see DirectX and OpenGL get wiped out.

  3. #463
    Junior Member Regular Contributor
    Join Date
    Feb 2006
    Location
    greece
    Posts
    181

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    I will add my 2 cents as well. Nothing that has not been voiced already, just had to reinforce the message myself as well. OpenGL3 is an utter failure. Plain and simple. There is no excuse. They could have opted to better support GL2.1 with extensions(All DX10 extensions are only available on NVIDIA chipsets). It would be the same thing, and everyone would be happy. Really, GL 3.0 is nothing new compared to what we already had. So, please ARB, it's not too late, apologize to people, start communicating again and give what you promised. All this 'fanfare for nothing' at the main site is only making people more disappointed at how underrated their (the people's, not the ARB's) intelligence is. I am but an amateur game programmer but it is plain simple that anyone serious about that will switch to Direct3D sooner rather than later. so, hurry ARB...you may still have some eggs unbroken in the end.

    Oh and one more thing that really unnerved me. I really appreciate, given the current state of the API that people still work on it. If people could refrain from calling efforts like GL_EXT_direct_state_access a joke it would make things easier for people who are making the effort. I,for sure, despise it when my work is discarded as useless just like that...it just extinguishes any incentive.
    while(1){keyboardsolo(FORTE, BPM_190);}

  4. #464
    Junior Member Regular Contributor
    Join Date
    Jul 2007
    Location
    Alexandria, VA
    Posts
    211

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    Quote Originally Posted by Y-tension
    OpenGL3 is an utter failure.
    Quote Originally Posted by Y-tension
    If people could refrain from calling efforts like GL_EXT_direct_state_access a joke it would make things easier for people who are making the effort.
    It's ok to criticize GL3.0 but not GL_EXT_direct_state_access? Weird.

  5. #465
    Senior Member OpenGL Guru
    Join Date
    Mar 2001
    Posts
    3,576

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    It's ok to criticize GL3.0 but not GL_EXT_direct_state_access? Weird.
    That could be because DSA goes farther than GL 3.0 in providing what Longs Peak promised.

  6. #466
    Member Regular Contributor
    Join Date
    Apr 2006
    Location
    Irvine CA
    Posts
    299

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod


    Longs Peak aimed to solve the "bind to edit" issue in OpenGL, by eliminating "edit" - and providing only immutable objects. If you can't edit objects, yep, no worries about bind to edit any more.

    DSA aims to solve "bind to edit" by removing the need to bind an object to the state vector (context) before altering it.

  7. #467
    Senior Member OpenGL Guru knackered's Avatar
    Join Date
    Aug 2001
    Location
    UK
    Posts
    2,833

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    it's nvidia's last gasp attempt at forcing an object model on OpenGL. Like, ok you won't let us have LP so we're going to copy and paste some kind of object model from the existing API. It's appreciated, but really highlighted what a joke 3.0 itself became. I feel sorry for nvidia.

  8. #468
    Senior Member OpenGL Pro
    Join Date
    Sep 2004
    Location
    Prombaatu
    Posts
    1,386

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    Quote Originally Posted by Y-tension
    I am but an amateur game programmer but it is plain simple that anyone serious about that will switch to Direct3D sooner rather than later. so, hurry ARB...you may still have some eggs unbroken in the end.
    Seems pretty clear to me that anyone serious, or at least a bit curious, would have / should have / could have tested the API greenness on the other side some time ago. For the rest of the graphics development community, I'd say things turned out pretty darn good, as GL3 turned out pretty much the way they, the majority, wanted it to - to the possibly chagrin of some, the minority, game coders.

    Clearly the big question right now is when do we get stable drivers from the "big 3", and to a lesser extent how this deprecation/profile model will play out in practice. This first question is the only interesting one to me, since whether or not vendors want to drop functionality is entirely up to them... no skin off my nose either way.

  9. #469
    Member Regular Contributor
    Join Date
    Apr 2004
    Location
    UK
    Posts
    420

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    I wonder who this 'majority' are, because from my understanding this wasn't a mass 'no to 3.0' vote but a case of 'we aren't getting it done on time, lets release 2.2, oh hi mr Khronos PR, what's that? call it 3.0? ok...'.

  10. #470
    Junior Member Regular Contributor
    Join Date
    Feb 2000
    Location
    Santa Clara, CA
    Posts
    172

    Re: The ARB announced OpenGL 3.0 and GLSL 1.30 tod

    Quote Originally Posted by Rob Barris
    Longs Peak aimed to solve the "bind to edit" issue in OpenGL, by eliminating "edit" - and providing only immutable objects. If you can't edit objects, yep, no worries about bind to edit any more.
    Not quite true Rob. State could not be edited - but data could. For example if you want to read or write buffer data, GL2 requires that you bind it first. LP did not.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •