All Projects β†’ SnapperTT β†’ bgfx-header-extension-library

SnapperTT / bgfx-header-extension-library

Licence: other
Header-only effects and helper library for Bgfx to help you hit the ground running. Includes a bunch of post processing filters to complete common graphical tasks

Programming Languages

c
50402 projects - #5 most used programming language
C++
36643 projects - #6 most used programming language

Projects that are alternatives of or similar to bgfx-header-extension-library

RavEngine
A fast, easy to use C++20 3D game library for modern computers
Stars: ✭ 122 (+248.57%)
Mutual labels:  metal, vulkan, bgfx, directx
bgfx-python
Python 3.7+ wrapper for the BGFX library. 🐍
Stars: ✭ 99 (+182.86%)
Mutual labels:  metal, vulkan, bgfx, directx
spirv cross
Safe Rust wrapper around SPIRV-Cross
Stars: ✭ 75 (+114.29%)
Mutual labels:  metal, vulkan, directx
harfang3d
HARFANG 3D source code public repository
Stars: ✭ 173 (+394.29%)
Mutual labels:  vulkan, bgfx, directx
Bgfx
Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.
Stars: ✭ 10,252 (+29191.43%)
Mutual labels:  metal, vulkan, directx
virtualGizmo3D
Virtual GIZMO - 3D object manipulator / orientator, via mouse, with pan and dolly/zoom features
Stars: ✭ 36 (+2.86%)
Mutual labels:  metal, vulkan, directx
wgpu-mc
Rust-based replacement for the default Minecraft renderer
Stars: ✭ 254 (+625.71%)
Mutual labels:  metal, vulkan, directx
Crossshader
βš”οΈ A tool for cross compiling shaders. Convert between GLSL, HLSL, Metal Shader Language, or older versions of GLSL.
Stars: ✭ 113 (+222.86%)
Mutual labels:  metal, vulkan, directx
CrossWindow-Graphics
A header only library to simplify creating πŸŒ‹ Vulkan / βšͺ OpenGL / 🌐 WebGL / ❎DirectX / πŸ€– Metal data structures with CrossWindow.
Stars: ✭ 48 (+37.14%)
Mutual labels:  metal, vulkan, directx
LowLevelAPIDemo
Evergine Low-Level API samples.
Stars: ✭ 12 (-65.71%)
Mutual labels:  metal, vulkan, directx
CrossWindow-Demos
πŸ₯ͺ Examples of how to use CrossWindow for things like rendering graphics, listening to events, etc.
Stars: ✭ 48 (+37.14%)
Mutual labels:  metal, vulkan, directx
Llgl
Low Level Graphics Library (LLGL) is a thin abstraction layer for the modern graphics APIs OpenGL, Direct3D, Vulkan, and Metal
Stars: ✭ 1,011 (+2788.57%)
Mutual labels:  metal, vulkan, directx
Fiber2d
Cross-platform 2D Game Engine in pure Swift
Stars: ✭ 415 (+1085.71%)
Mutual labels:  metal, vulkan, directx
The Forge
The Forge Cross-Platform Rendering Framework PC Windows, Linux, Ray Tracing, macOS / iOS, Android, XBOX, PS4, PS5, Switch, Quest 2
Stars: ✭ 2,710 (+7642.86%)
Mutual labels:  metal, vulkan, directx
Fna3d
FNA3D - 3D Graphics Library for FNA
Stars: ✭ 111 (+217.14%)
Mutual labels:  metal, vulkan
Veldrid
A low-level, portable graphics library for .NET.
Stars: ✭ 1,784 (+4997.14%)
Mutual labels:  metal, vulkan
Substrate
A cross-platform render-graph based rendering system written in Swift
Stars: ✭ 94 (+168.57%)
Mutual labels:  metal, vulkan
Filament
Filament is a real-time physically based rendering engine for Android, iOS, Windows, Linux, macOS, and WebGL2
Stars: ✭ 13,215 (+37657.14%)
Mutual labels:  metal, vulkan
Floor
A C++ Compute/Graphics Library and Toolchain enabling same-source CUDA/Host/Metal/OpenCL/Vulkan C++ programming and execution.
Stars: ✭ 166 (+374.29%)
Mutual labels:  metal, vulkan
Aether3d
Aether3D Game Engine
Stars: ✭ 177 (+405.71%)
Mutual labels:  metal, vulkan

Bgfx Header Utils And Effects Library

An extension library for bgfx to help you hit the ground running by wrapping common tasks in simple header files. It also provides a number of Effects to provide an off-the-shelf solution to common rendering demands, such as post processing filters, shadow mapping and more.

Like bgfx, this is rendering library. Its not a game engine and does not aim to be. Rather it simply gives you the pieces to rapidly assemble a graphics pipeline in a cross platform, api agnostic manner. Bgfxh aims to bridge the gap between using a potentially large or bloated generalist graphics library or game engine for simple rendering jobs, and reinventing the wheel by creating an engine from scratch. By thinly relying on bgfx maintenance requirements are kept low.

Contact:

Liam Twigger - @SnapperTheTwig

Features:

  • Header only library, inspired by stb, requires no changes to your build system. Simply use #define BGFXH_IMPL before #include to generate an implementation
  • Only pay for what you use. Don't want texture loading? Then don't #include <bgfxh/loadTexture.h>. Only want it
  • SDL Window management with initSdlWindow()
  • Texture Loading with loadTexture() - supports what bimg supports (most of this is extracted from the bgfx examples and repackaged to be used here)
  • Shader Loading with loadShader()
  • Inspect textures/framebuffers with debugDrawFramebuffer() and debugDrawFramebufferMono() for monochromatic framebuffers (such as depth buffers).
  • Frustum culling utility
  • A variety of Effects, see below for more info
  • Thin layer ontop of bgfxh. Rather than hiding the underlying framework under a complex layer of abstraction, bgfxh just provides free functions that do some job. Effects are c++ classes, are optional
  • Few dependencies - only on bgfx/bimg/bx and some standard c/c++ libraries
  • Permissive license

Effects:

Effects are basically C++ objects that wrap bgfx commands and resources do some graphical task. To use, simply:

  • Include the relevant file (eg #include <bgfxh/effects/bloom.h>)
  • Create an object bgfxh::bloomEffect mBloomEffect;
  • Choose your settings for the filter, then call mBloomEffect.init(); - this generates the uniforms, samplers and framebuffers for the filter and loads the relevant shaders
  • In your rendering loop, call mBloomEffect.submit(framebufferToBloom); - this will set up the views
  • On object destruction all resources created will be freed.

Shaders ''can'' be embedded in the Effects. Use #define BGFXH_EMBED_EFFECT_SHADERS to embed at compile time.

Each filter has detailed use instructions in the top of their respective header file.

Availiable Effects:

  • atmosphere.h - Implementation of Sean O'Niel's atmospheric shader from Gpu Gems 2. Works at all altitudes, can shade the atmosphere and the ground, can work either in the vertex or the fragment shader. Includes a utitlity to generate sky dome/sphere meshes
  • cascadingShadowMap.h - Cascading shadowmap generation (both regular and VSM, with frustum checking)
  • bloom.h - Bloom with a fixed gaussian kernal. Uses bilinear filtering for efficiency
  • guassianBlur.h - Guassian blur with setable kernal. Also has a function to generate a suitable sigma for a given kernal
  • lum.h - Time averaged luminance calculation
  • tonemapping.h - ACES Filmic Tonemapping + can combine the outputs of other Effects

Shaders:

Simply copy the shaders you want and merge the folders together. So to add bloom and luminance shaders to your application copy the contents of bgfxh/shaders/bloom/ and bgfx/shaders/lum/ to yourApp/<yourShaderPath>/, and set bgfxh::shaderSearchPath to "<yourShaderPath>/" + bgfxh::getShaderDirectoryFromRenderType() + "/" to point the shader loader to the right shaders. For OpenGl this will be "<yourShaderPath>/glsl/", for dx11 this will be "<yourShaderPath>/dx11/", for Vulkan this will be "<yourShaderPath>/spriv/"

Note that bgfxh::shaderSearchPath only effects the location of shaders loaded for bgfxh filters! Eg bgfxh::bloomEffect will load bloom_brightpass by invoking bgfxh::loadShader(bgfxh::shaderSearchPath + "vs_bloom_brightpass.bin", bgfxh::shaderSearchPath + "fs_bloom_brightpass.bin")

loadShader will handle Windows or POSIX file paths (it internally invokes bgfxh::fixPath(path))

If you are lacking a build system for your own shaders you can use the one provided.

Shaders come already compiled + are embeddable, so you can use them right away!

Contributing:

More Render Jobs = more better! I do have plans to specifically make the following, but any input will be greatly appreciated

  • A light sprite/tile engine (sprites should use the transient buffer, tiles should use a vertex buffer).
  • Screenspace reflection
  • A simple forward renderer

Be sure to create/edit the .lzz files, not the generated .h files. The tools + scripts to create the header files from the .lzz sources are provided.

How Do I?

Create a SDL Window?

#include <SDL>
#include <bgfx>

#define BGFXH_IMPL
#include <bfgxh/bgfxh.h>
#include <bfgxh/sdlWindow.h>

int main (int argc, char *argv[]) {
	SDL_Init(0);
	SDL_Window * mWindow = SDL_CreateWindow("BGFXH Test", SDL_WINDOWPOS_UNDEFINED, SDL_WINDOWPOS_UNDEFINED, 1200, 720, SDL_WINDOW_SHOWN | SDL_WINDOW_RESIZABLE);
	bgfxh::initSdlWindowAndBgfx(mWindow); // Creates a bgfx context in an sdl window
	
	// You now have a window + a bgfx context!
	while (true) {
		drawStuff();
		bgfx::frame();
		}
	}

initSdlWindowAndBgfx() internally calls bgfx::init() with some default parameters. You can avoid this by calling initSdlWindow(mWindow);, then call bgfx::init(); when you like;

Load a Texture? (.dds/.ktx) Or an Image as a Texture (.jpg, .png, .tga, etc).

#define BGFXH_IMPL
#include <bfgxh/loadTexture.h>

...

bgfx::TextureHandle foo = bgfxh::loadTexture ("filename.ext", BGFX_TEXTURE_FLAGS | BGFX_SAMPLER_FLAGS);

NOTE: that this file adds a linking dependency on libbimg_decode(Debug/release).a. This is from bimg and is built alongside bgfx

It is recommended that you use texturec (part of bgfx, see tools) to create a texture file (.dds/.kxt) as these are optimised for loading and can contain pre-computed mipmaps. On the fly mipmap generation is not supported (and is slow anyway).

Initialise BGFX and BGFXH?

#define BGFXH_IMPL
#include <bfgxh/bgfxh.h>
#include <bfgxh/sdlWindow.h> // If using SDL Windows!

...

initSdlWindowAndBgfx(mWindow);
bgfxh::init(backbufferWidth, backbufferHeight, "path/to/shaders"); //<-- shaders, uniforms and vertexDecl's for debug drawing are made here

.... OR ....

bgfx::Init mInit;
// Set mInit's parameters here
initSdlWindowAndBgfx(mWindow, mInit);
bgfxh::init(backbufferWidth, backbufferHeight, "path/to/shaders"); //<-- shaders, uniforms and vertexDecl's for debug drawing are made here

.... OR ....

initSdlWindow(mWindow); // Don't call bgfx::init() internally. Infact if you're not using SDL you can omit this line altogether
bgfx::init();
bgfxh::init(backbufferWidth, backbufferHeight, "path/to/shaders");

View the Contents of a Framebuffer?

#define BGFXH_IMPL
#include <bfgxh/bgfxh.h>

...

bgfx::init();
bgfxh::init(backbufferWidth, backbufferHeight, "path/to/shaders"); //<-- shaders, uniforms and vertexDecl's for debug drawing are made here

...

// Initialises a 2D view, with tag, size, no framebuffer attachement (render to backbuffer), doesn't clear, and is not a unit ortho matrix 
bgfxh::initView2D (VIEW_ID_OUTPUT_PASS, "output pass", backbufferWidth, backbufferHeight, BGFX_INVALID_HANDLE, false, false);
// Viewing a texture
// ViewId, thingToInspect, xPos, yPos, xSize, ySize, (backbufferWidth), (backbufferHeight)
// (backbufferWidth), (backbufferHeight) are only used for pixel-perfect dx9 rendering and can be ommitted if you don't care about that
bgfxh::debugDrawTexture (VIEW_ID_OUTPUT_PASS, textureHandleToView, 10, 10, 120, 120, backbufferWidth, backbufferHeight); 

// Viewing a framebuffer
bgfxh::debugDrawFramebuffer (VIEW_ID_OUTPUT_PASS, framebufferToInspect, 10+130, 10, 120, 120, backbufferWidth, backbufferHeight);

// Viewing the output of a bgfxh::effect
bgfxh::debugDrawFramebuffer (VIEW_ID_OUTPUT_PASS, mBgfxhLumEffect.getOutputFramebuffer(), 10+130*2, 10, 120, 120, backbufferWidth, backbufferHeight);

// Inspecting a cascading shadow map (eg, cascadingShadowMapEffect.h)
for (unsigned int i = 0; i < mBgfxhCsmEffect.nShadowLevels; ++i)
	bgfxh::debugDrawFramebuffer (VIEW_ID_OUTPUT_PASS, mBgfxhCsmEffect.getOutputFramebuffer(i), 10 + 130*i, 130, 120, 120, backbufferWidth, backbufferHeight);
		

Create a Rendering Pipeline With The Provided Effects and My Stuff?

#define BGFXH_IMPL
#include <bfgxh/bgfxh.h>
// Optionally #define BGFXH_EMBED_EFFECT_SHADERS if you want shaders embedded at compile time
#include <bfgxh/effects/bloom.h>
#include <bfgxh/effects/lum.h>

class GfxPipeline {
public:
	// Effect objects
	bgfxh::bloomEffect mBloomEffect; // Each "job" or is a class! 
	bgfxh::lumEffect mLumEffect;
	bgfxh::tonemappingEffect mTonemappingEffect;
	// Your resources
	bgfx::ProgramHandle m_myProgram;
	bgfx::FrameBufferHandle m_myFramebuffer;

	GfxPipeline () {}
	~GfxPipeline() {} // Each "job" will clean up its resources on destruction

	void init () {
		// Set parameters
		mBloomEffect.setSize (600, 360);
		mBloomEffect.nBloomBlurPasses = 2;
		mBloomEffect.init(); // Resources are created here!
		mLumEffect.init();
		
		mTonemappingEffect.setSize (1200, 720);
		mTonemappingEffect.maxAdditonalSamplerSlots = 1; // Configure the tonemapping filter to accept a blended attachement
		mTonemappingEffect.init ();
		
		// Your stuff
		m_myProgram = bgfxh::loadProgram("path/vs_forwardRenderer.bin", "fs_forwardRenderer.bin");
		m_myFramebuffer = ... ; // Gbuffer? Or just a colour/depth buffer for forward rendering!
		
		}
		
	void submitScene (YourScene) {
		mLumEffect.viewId = 1; // A lum filter will take up 5 views
		mBloomEffect.viewId = 1 + mLumEffect.getViewIncrement();  // A bloom filter will take a number of views depending on how many blur passes you are doing
		mTonemappingEffect.viewId = mBloomEffect.viewId + mBloomEffect.getViewIncrement();
		
		...
		// Render your scene to a framebuffer (m_myFramebuffer)
		// You still have to implement your own forward or gbuffer here
		//bgfx::submit(0, m_myProgram)
		
		...
		// Apply Post Processing using the filters!
		mLumEffect.submit (bgfx::getTexture(m_myFramebuffer, 0));
		// Get the output of a effect as a texture that you can use in another effect!
		mBloomEffect.submit (mLumEffect.getOutputTexture(), bgfx::getTexture(m_myFramebuffer, 0)); 
		// Configure the tonemapping filter to additively blend the bloom
		mBgfxhTonemappingEffect.setExtraComponent (0, mBgfxhBloomEffect.getOutputTexture(), 1.0f, 0.f);
		// Does the tonemapping. Renders to backbuffer by default
		mTonemappingEffect.submit (bgfx::getTexture(m_myFramebuffer, 0), mLumEffect.getOutputTexture()); 
		
		// Debug render the lum filter's output to see if it is calculating sensible lum values
		const int OUTPUT_PASS_ID = 200;
		bgfxh::initView2D (VIEW_ID_OUTPUT_PASS, "output pass", backbufferWidth, backbufferHeight, BGFX_INVALID_HANDLE, false, false);
		bgfxh::debugDrawFramebuffer (VIEW_ID_OUTPUT_PASS, mLumEffect.getOutputFramebuffer(), 10, 10, 120, 120, backbufferWidth, backbufferHeight);
		}
		
		
	}

Speed Up Compile Times By Making A Seperate Compilation Unit?

//Wrapper.h
#include <bfgxh/bgfxh.h>
#include <bfgxh/...>
#include <bfgxh/...> //etc
//Wrapper.cpp
#define BGFXH_IMPL
#include <bfgxh/bgfxh.h>
#include <bfgxh/...>
#include <bfgxh/...> //etc

Frustum Cull?

#define BGFXH_IMPL
#include <bfgxh/bgfxh.h>

...

bgfxh::frustum mFrustum;
mFrustum.setFromViewAndProjMatrix (viewMtx, projMtx);

for (each object in scene) {
	if (mFrustum.frustumCheck (object.positionVec3, object.radius)) continue; // Where radius is the radius of some bounding sphere for the object
	... Alternatively ....
	if (mFrustum.frustumCheck (object.bgfxModelMtx, object.radius)) continue;
	// Set uniforms, transform matricies, etc
	bgfx::setTransform (object.bgfxModelMtx);
	bgfx::submit();
	}

Use the Built-In Shaders?

Submit using one of: bgfxh::m_programUntexturedPassthrough - Renders geometry without any texture or any fancy stuff. Handy for wireframe rendering bgfxh::m_programTexturePassthrough - Renders a texture. Handy for GUI stuff bgfxh::m_programTexturePassthroughMonochromatic - Renders a texture in greyscale. Handy for inspecting a framebuffer

Thanks

Thanks To Branimir Karadzic and all others who have contributed to Bgfx!

License

Public Domain Various code snippets have been adapted from bgfx and are thus under the BSD license.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].