• Advertisement
Sign in to follow this  

Vulkan Your opinion on BGFX

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

What's your opinion on using a library like bgfx instead of a custom GLFW + GLM + GLAD approach? With the upcoming release of Vulkan, should i wait for it and use it, or work on top of an abstraction like bgfx? It has it's own shading language.

Edited by vinnyvicious

Share this post


Link to post
Share on other sites
Advertisement

What's your opinion on using a library like bgfx instead of a custom GLFW + GLM + GLAD approach? With the upcoming release of Vulkan, should i wait for it and use it, or work on top of an abstraction like bgfx? It has it's own shading language.


The shading language of bgfx can be, fairly trivially, replaced with whatever you want. bgfx is fairly easy to get up and going, and Branimir has been working pretty heavily on the DX12 stuff, so that's available (although the performance wasn't up there with DX11 yet, the last time I tried it, but he's actively working on that).

Share this post


Link to post
Share on other sites

I'm a big fan of bgfx. It certainly takes a little getting used to but once you get your bearings things start moving along very quickly. Branimir is a smart fellow and extremely active on the project. He's quick to reply to email and github issues. Would definitely recommend.

Edited by AndrewMac

Share this post


Link to post
Share on other sites

With the upcoming release of Vulkan, should i wait for it and use it, or work on top of an abstraction like bgfx?

When Vulkan comes out, I assume that if bgfx development is still active, then a vulkan back-end will be created underneath the bgfx abstraction, so you'll get that for free (or you can help work on the vulkan back-end yourself, toosmile.png
 
Unless you want to create a GPU abstraction for the sake of it, then use a library like bgfx (or a full engine). Writing a game on top of a low-level API like D3D/GL/Vulkan is a terrible idea, and creating a well-designed abstraction-layer on top of D3D/GL/Vulkan is a big project in itself.
 
I haven't used bgfx but I've had a quick peek at it's code. The abstraction seems very good, but some of the internal code is terrible sad.png That just means it's got a lot of room for improvement and optimization though laugh.png

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 turanszkij
      Hi, right now building my engine in visual studio involves a shader compiling step to build hlsl 5.0 shaders. I have a separate project which only includes shader sources and the compiler is the visual studio integrated fxc compiler. I like this method because on any PC that has visual studio installed, I can just download the solution from GitHub and everything just builds without additional dependencies and using the latest version of the compiler. I also like it because the shaders are included in the solution explorer and easy to browse, and double-click to open (opening files can be really a pain in the ass in visual studio run in admin mode). Also it's nice that VS displays the build output/errors in the output window.
      But now I have the HLSL 6 compiler and want to build hlsl 6 shaders as well (and as I understand I can also compile vulkan compatible shaders with it later). Any idea how to do this nicely? I want only a single project containing shader sources, like it is now, but build them for different targets. I guess adding different building projects would be the way to go that reference the shader source project? But how would they differentiate from shader type of the sources (eg. pixel shader, compute shader,etc.)? Now the shader building project contains for each shader the shader type, how can other building projects reference that?
      Anyone with some experience in this?
    • By mark_braga
      I am working on a compute shader in Vulkan which does some image processing and has 1024 * 5=5120 loop iterations (5 outer and 1024 inner)
      If I do this, I get a device lost error after the succeeding call to queueSubmit after the image processing queueSubmit
      // Image processing dispatch submit(); waitForFence(); // All calls to submit after this will give the device lost error If I lower the number of loops from 1024 to 256 => 5 * 256 = 1280 loop iterations, it works fine. The shader does some pretty heavy arithmetic operations but the number of resources bound is 3 (one SRV, one UAV, and one sampler). The thread group size is x=16 ,y=16,z=1
      So my question - Is there a hardware limit to the number of loop executions/number of instructions per shader?
    • By AxeGuywithanAxe
      I wanted to see how others are currently handling descriptor heap updates and management.
      I've read a few articles and there tends to be three major strategies :
      1 ) You split up descriptor heaps per shader stage ( i.e one for vertex shader , pixel , hull, etc)
      2) You have one descriptor heap for an entire pipeline
      3) You split up descriptor heaps for update each update frequency (i.e EResourceSet_PerInstance , EResourceSet_PerPass , EResourceSet_PerMaterial, etc)
      The benefits of the first two approaches is that it makes it easier to port current code, and descriptor / resource descriptor management and updating tends to be easier to manage, but it seems to be not as efficient.
      The benefits of the third approach seems to be that it's the most efficient because you only manage and update objects when they change.
    • By khawk
      CRYENGINE has released their latest version with support for Vulkan, Substance integration, and more. Learn more from their announcement and check out the highlights below.
      Substance Integration
      CRYENGINE uses Substance internally in their workflow and have released a direct integration.
       
      Vulkan API
      A beta version of the Vulkan renderer to accompany the DX12 implementation. Vulkan is a cross-platform 3D graphics and compute API that enables developers to have high-performance real-time 3D graphics applications with balanced CPU/GPU usage. 

       
      Entity Components
      CRYENGINE has addressed a longstanding issue with game code managing entities within the level. The Entity Component System adds a modular and intuitive method to construct games.
      And More
      View the full release details at the CRYENGINE announcement here.

      View full story
    • By khawk
      The AMD GPU Open website has posted a brief tutorial providing an overview of objects in the Vulkan API. From the article:
      Read more at http://gpuopen.com/understanding-vulkan-objects/.


      View full story
  • Advertisement