# Will Tetra be written in pure Rust eventually?
Probably not - SDL2 is a stable and well-tested foundation for building games, and it runs on basically every platform under the sun, so I'm hesitant to replace it. That's likely to remain the only non-Rust dependency, however.
# Do I have to install SDL manually?
It's possible to have your project automatically compile SDL2 from source as part of the build process. To do so, specify your dependency on Tetra like this:
[dependencies.tetra] version = "0.3" features = ["sdl2_bundled"]
This is more convienent, but does however require you to have various build tools installed on your machine (e.g. a C compiler, CMake, etc). In particular, this can be a pain on Windows - hence why it's not the default!
# Can I static link SDL?
If you want to avoid your users having to install SDL2 themselves (or you having to distribute it as a DLL), you can specify for it to be statically linked:
[dependencies.tetra] version = "0.3" features = ["sdl2_static_link"]
This comes with some trade-offs, however - make sure you read this document in the SDL2 repository so that you understand what you're doing!
# How do I hide the console when running my game?
On Windows, you can add the
windows_subsystem attribute to your
// To hide the console in all builds: #![windows_subsystem = "windows"] // To hide the console in release builds only: #![cfg_attr(not(debug_assertions), windows_subsystem = "windows")]
On Mac, you will need to package your game as a
.app - see this thread on the Rust forums for more info.
On Linux, you should not have to make any additional changes.
# Why am I getting a black screen?
Tetra currently targets OpenGL 3.2, so if your hardware does not support this, you might have trouble running games written with the framework. You can check your version of OpenGL by enabling Tetra's debug output - add
.debug_info(true) to your
ContextBuilder, run your game, and then look at the console.
If your OpenGL version is 3.2 or higher and you're still getting a black screen, that may indicate a bug - I currently only have access to a Windows machine with a reasonably modern graphics card, so it's not outside the realms of possibility that something that works for me might be broken for others! Please submit an issue, and I'll try to fix it and release a patch version.
# Does Tetra support drawing primitive shapes/meshes?
Not currently - there is an open issue to implement this, but it will require some refactoring of the renderer.
If you just want to draw simple rectangles, you can work around this by creating a solid colored
Texture and then drawing that. If you create a 1x1 solid white texture, you can use the
DrawParams to draw multiple rectangles of varying sizes/colors/transparencies in a single draw call.
# Why is my game running slow?
Cargo builds projects in debug mode by default. This can lead to your game running slowly, as the compiler does not fully optimize your code.
Optimizations can be enabled by passing
--release when building/running your project, but this increases build times quite significantly and removes debug info from the binary, meaning you cannot easily debug or profile your code.
To work around this, add one of the following snippets to your
# To enable optimizations in debug mode for Tetra only (requires Rust 1.41): [profile.dev.package.tetra] opt-level = 3 # To enable optimizations in debug mode for all dependencies (requires Rust 1.41): [profile.dev.package."*"] opt-level = 3 # To enable optimizations in debug mode for the entire project (works with all Rust versions): [profile.dev] opt-level = 3
Choosing one of the first two options is preferred, as they will not slow down rebuilds of your game's code.
You should also make sure to build with
--release when distributing your game, so that the final binary is as fast as possible.
The impact of compiler optimizations can be observed by running the
bunnymark example both with and without the
--release flag. This example adds 100 new sprites to the screen every time the user clicks, until rendering conistently drops below 60fps.
These were the results when I ran it against Tetra 0.2.9 on my local machine:
For reference, my system specs are:
- CPU: AMD Ryzen 5 1600 3.2GHz
- GPU: NVidia GeForce GTX 1050 Ti
- RAM: 8GB DDR4
# Why is it called Tetra?
I'm terrible at naming projects, and this happened to be playing when I was typing
cargo new. I wish there was a better origin story than that 😄