Documentation | Tutorial | Blog
gfx is a high-performance, bindless graphics API for the Rust programming language. It aims to be the default API for Rust graphics: for one-off applications, or higher level libraries or engines.
- Graphics APIs are mostly designed with C and C++ in mind, and hence are dangerous and error prone, with little static safety guarantees.
- Providing type safe wrappers around platform-specific APIs is feasible, but only pushes the problem of platform independence to a higher level of abstraction, often to the game or rendering engine.
- Modern graphics APIs, whilst providing a great degree of flexibility and a high level of performance, often have a much higher barrier to entry than traditional fixed-function APIs.
- Graphics APIs like OpenGL still require the developer to 'bind' and 'unbind' objects in order to perform operations on them. This results in a large amount of boiler plate code, and brings with it the usual problems associated with global state.
Graphics backends:
- OpenGL 2.1+
- OpenGL ES2+ (works on Android)
- Direct3D 11
- Metal (WIP 75%)
- Vulkan (WIP 40%)
Hardware features:
- off-screen render targets
- multisampling
- instancing
- geometry shaders
- tessellation
- computing
- persistent mapping
Biggest open-source projects are:
- Amethyst engine
- Piston engine - 2d graphics
- LazyBox engine
- Zone of Control game
- Vange-rs game
- Claymore game/engine
Shiny screens, including some older projects:
The gfx-rs git repository contains a number of examples. Those examples are automatically downloaded if you clone the gfx directory:
$ cd <my_dir>
$ git clone https://github.com/gfx-rs/gfx
where <my_dir> is a directory name of your choice. Once gfx is downloaded you can build any of the gfx examples.
The examples are listed in the <my_dir>/gfx/Cargo.toml file.
For example try:
$ cd gfx
$ cargo run --example cube
If you compile the example for the first time, it may take some while since all dependencies must be compiled too.
If you want to build your own stand-alone gfx program, add the following to your new Cargo.toml:
[dependencies]
gfx = "0.14"
For gfx to work, it needs access to the graphics system of the OS. This is typically provided through some window initialization API. gfx can use a couple of those to acquire graphical contexts. For example; glfw or glutin.
To see how the graphic context is acquired, see the cube example or the triangle example.
To use glutin, for example, your Cargo.toml must be extended with the following dependencies:
[dependencies]
...
glutin ="*"
gfx_window_glutin = "*"
You may want to inspect <my_dir>/gfx/Cargo.toml for other crates typically used in gfx programs.
Alternatively, an excellent introduction into gfx and its related crates can be found here.
gfx is still in development. API may change with new backends/features to be implemented. If you are interested in helping out, checkout contrib.md and do not hesitate to contact the developers on Gitter.