• Advertisement
Sign in to follow this  

OpenGL Vulkan is Next-Gen OpenGL

This topic is 487 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

Advertisement
Yeah, as I said in the other thread, it seems sane... a Khronos take on the Mantle API.

Interested to see the complete model; do we get separate command queues for graphics and compute? (based on the ImgTec blog this looks to be the case!) how does it deal with multiple gpu machine? what about upload/download control?

But on the face of it things look sane... which I still find confusing... biggrin.png Edited by phantom

Share this post


Link to post
Share on other sites

BTW, this paves the way for a true HLSL->SPIR-V compiler, evntually allowing people to use their existing source files 
vec4 master race represent!

Share this post


Link to post
Share on other sites
Will work on any platform that supports OpenGL ES 3.1 and up

 

Now THAT is exciting news.

 

EDIT: Maybe I spoke too soon, AMD doesn't support it then?  Weird.

Edited by Boreal Games

Share this post


Link to post
Share on other sites
ES3.1 is just a target hardware level; AMD just don't have a driver for it is all and ES is used because Mobile.

AMD's hardware will support this, likely anything which can support GL3.3 (which is roughly where ES3.1 is) has the ability to support this API which means basically all hardware in the wild today on the desktop. (driver allowing.)

Share this post


Link to post
Share on other sites

This is all pretty damn awesome.  If the driver support is there too, then D3D12 is dead in the water for me.

Share this post


Link to post
Share on other sites


AMD's hardware will support this, likely anything which can support GL3.3 (which is roughly where ES3.1 is) has the ability to support this API which means basically all hardware in the wild today on the desktop. (driver allowing.)
I can only hope. OpenGL 3.3 support in AMD hardware goes back to HD 2xxx series, but they stopped supporting newer extensions on that hardware after OpenGL 4.2, whereas nVidia stopped at 4.4. Thus why something really useful like ARB_direct_state_access is only available in OpenGL 4.5 hardware, or why something simple like ARB_vertex_attrib_binding works in a nVidia GeForce 8800 GT from 2007, but doesn't works on an ATI Radeon HD4870 from 2009.

 

I'm not seeing them supporting Vulkan on anything pre-HD5xxx, maybe they'll go as far as not supporting Vulkan on anything that is pre-GCN.

Share this post


Link to post
Share on other sites

If the driver support is there too, then D3D12 is dead in the water for me

Microsoft is not listed as supporter (they didn't support OGL for years now,right ?), and if vulkan will hold its promises and mantle is the preferred console API, why should someone want to use D3D12 ? To support Win10 games ? With microsoft history of loosing interest in projects (starting from DirectPlay/DirectSound over to several DirectX version up to XNA), who want to risk to use a version which might be unsupport in 1-2 years ?

Edited by Ashaman73

Share this post


Link to post
Share on other sites

Looks like Khronos finally got their API redesign, pretty good timing too.

 

But in order for this to take off there needs to be good drivers. Not sure if Apple will keep up-to-date drivers (past bad OpenGL support, Metal) and not sure how Microsoft will cooperate (DX12 still not available). So it's mostly up to the GPU manufacturers (NV, AMD, Intel, PowerVR) to maintain good drivers. From [0], it looks like there's still a lot of work to be done.

 

[0] -

Share this post


Link to post
Share on other sites

and not sure how Microsoft will cooperate (DX12 still not available).


Why would MS have to do anything?
They don't support OpenGL, Mantle, OpenCL and CUDA and yet they all work just fine... this is no different.

Share this post


Link to post
Share on other sites

why should someone want to use D3D12 ?

 
The reason to prefer D3D has always been more robust drivers and better tools on an API that hits ~95% of the target market.  That's it.  Preference for one vendor or one platform comes nowhere into it, nor do any malicious backdoor shenanigans.  The D3D driver model was simply a better driver model that, once the emotional aspect of the original API war burned out, became obvious to everyone that it allowed for this to happen.  But that's also the hurdle that Vulkan now has to get over (and Khronos are making the right kind of noises about this, which is encouraging).
 
Right now Vulkan seems to have a head-start, and if we can get a spec, sample apps, some functional tools and reasonable drivers from all 3 desktop vendors by SIGGRAPH, it should eat D3D 12.
 
On the other hand if Khronos stall or if the vendors fail to deliver then D3D 12 will have a chance to jump back ahead.
 
Either way the next year is going to be interesting. biggrin.png


Robust tools are a huge winning point there. OpenGL could target 95% of the market as well, but the lack of decent vendor agnostic tools made it a real pain in the keister to use. Using an API where you can actually debug what is going on (PIX for example) is really important. Unfortunately, OpenGL never really had that capability and you were stuck with whatever tools the various GPU vendors provided. Which, frankly, all suck in their own unique ways.

Vulkan certainly looks interesting, but I also recall the LAST TIME we were promised something great OpenGL wise. You might remember how that ended. So at the moment I'm going to go with current mood: Pessimistic without further evidence. Edited by Washu

Share this post


Link to post
Share on other sites

 


Why would MS have to do anything?
They don't support OpenGL, Mantle, OpenCL and CUDA and yet they all work just fine... this is no different.

 

Not on tablet/phone hardware they don't. Neither is there VS support, without wacky plugins from IHVs. Still, I don't know if I dare to dream that the new standards-attentive MS will actually boost Vulkan to first class support.

Edited by Promit

Share this post


Link to post
Share on other sites

Not on tablet/phone hardware they don't.

I'm not sure that Microsoft-based phones and tablets represent a credible enough install-base to be worried about.

 

More interesting to see if Apple will let this in the door to iOS - without that chunk of the mobile market, you'll be stuck supporting Vulcan and Metal for the foreseeable future.

Share this post


Link to post
Share on other sites
Any idea how vulkan will be "deviding" the support for lots of different devices?
Meaning that you don't have a disadvantage when developing for current gen consoles/pc versus a gui for a washing machine.

Share this post


Link to post
Share on other sites

AMD published a new release: http://community.amd.com/community/amd-blogs/amd-gaming/blog/2015/03/03/one-of-mantles-futures-vulkan

The main point being that Vulkan is essentially an iterated cross platform version of Mantle. I like that AMD was willing to describe their own press release hours earlier as cryptic.

Share this post


Link to post
Share on other sites

 

and not sure how Microsoft will cooperate (DX12 still not available).


Why would MS have to do anything?
They don't support OpenGL, Mantle, OpenCL and CUDA and yet they all work just fine... this is no different.

 

 

I was trying to bring up the fact that some people believe that Microsoft sabotaged the OpenGL implementation on Windows to increase DirectX adoption. And whether Microsoft will allow Vulkan and Mantle to be first-class citizens with DX12 (if it's even possible) and whether Microsoft will keep their open-source friendly ways up (like Promit mentioned).

 

IIRC, Apple has to explicitly allow support for new APIs because they write their own drivers. So "it just works" isn't always possible.

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