bgfx
Box2D
Our great sponsors
bgfx | Box2D | |
---|---|---|
71 | 35 | |
14,306 | 7,280 | |
- | - | |
9.3 | 0.0 | |
2 days ago | about 1 month ago | |
C++ | C++ | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bgfx
- WebKit Switching to Skia for 2D Graphics Rendering
-
Is it possible and realistic to learn independent of an API?
Sort of, I'd recommend a modern higher level API. I'm not sure what the current recommended ones are (probably bgfx), but assuming the wrapper is "low level enough", then the concepts you learn are still going to apply.
-
Ask HN: Released games built on FOSS engines?
https://github.com/bkaradzic/bgfx for just that FOSS intermediate rendering library (includes Minecraft)
- Valve Says Counter-Strike 2 for macOS Not Happening, There Aren't Enough Players
-
The Ultimate Cross-Platform Rendering Engine?
BGFX: Pretty mature and easy to use with many backends.
- Cairo – Open-Source 2D Graphics Layer/API with Fonts and Many Back-Ends
-
Best graphics libraries for game development that are compatible with Apple Metal API?
bgfx. I have not used it, but I have heard good things about it.
-
LWJGL = SFML vs Allegro vs SDL vs Ogre vs ???
There's kind of a lack of this for C++ in 3D, I think it's often due to the necessity of a secondary scripting language in game engines with C++, which isn't necessarily needed in Java or C#. SFML is like that (but also 2D), Godot is similar (but more geared towards 2D). Ogre3D is an actual engine like I mentioned earlier, not sure how easy it is to use. Cocos2d is higher level, but is also 2D only. I'm not fond of SDL, it feels like a windowing library with slow old school immediate mode stuff attached, so it ends up not being good at the rest of the tacked on things. SDL is popular as a windowing library, and it's why you see it used everywhere (but the most notable uses of it aren't using their drawing capabilities), I often see bgfx thrown around, and for you it might be a good choice, though I have no experience with it.
-
Is it a crazy idea to create a 3D operating system?
Another route could be using an abstraction over Vulkan (faster, more efficient, more difficult): bgfx, dawn, magma, or wgpu (Rust).
-
The update we all want but will never get
now, java is actually quite a performant language and even if its not most of the performance bugs in mc are due to it being single threaded, inefficient chunk generation and optimizing, and it built ontop of opengl WHICH isn't much of a performance hit but its still ehh idk it doesn't matter that much (NOW SWITCHING THE GAME TO AN ENTIRELY DIFFERENT GRAPHICS API WOULD SUCK ASS TO DO (and vulkan is quite verbose :))) (AND also bgfx would probably be better due to it being an abstraction layer ontop of all the graphics apis so minecraft could target many depending on your platform (and also bedrock used to (or still does i dont know) use bgfx before they switched to just two (IF IM READING MC WIKI RIGHT BECAUSE IM NOT ENTIRELY SURE IF THEY USE BGFX STILL ?? SO THEY COULD STILL BE TARGETING MULTIPLE YET THEY JUST WROTE THEIR NEW SHIT BAD IDK))
Box2D
-
Blaze: A High Performance C++ Math library
For typical game physics engines... not that much. Math libraries like Eigen or Blaze use lots of template metaprogramming techniques under the hood that can help when you're doing large batched matrix multiplications (since it can remove temporary allocations at compile-time and can also fuse operations efficiently, as well as applying various SIMD optimizations), but it doesn't really help when you need lots of small operations (with mat3 / mat4 / vec3 / quat / etc.). Typical game physics engines tend to use iterative algorithms for their solvers (Gauss-Seidel, PBD, etc...) instead of batched "matrix"-oriented ones, so you'll get less benefits out of Eigen / Blaze compared to what you typically see in deep learning / scientific computing workloads.
The codebases I've seen in many game physics engines seem to all roll their own math libraries for these stuff, or even just use SIMD (SSE / AVX) intrinsics directly. Examples: PhysX (https://github.com/NVIDIA-Omniverse/PhysX), Box2D (https://github.com/erincatto/box2d), Bullet (https://github.com/bulletphysics/bullet3)...
-
Jolt Physics raylib: trying 3D C++ Game Physics Engine
Box2D: 2D engine used in Unity and also earlier versions of Godot. Open source.
-
Rust Game Physics Engines: PhysX, Rapier, XPBD & Others
Box2D GitHub repo: erincatto/box2d
- Nebula is an open-source and free-to-use modern C++ game engine
-
Linear code is more readable
Why is 600 lines too long? How are you able to make that judgment call without first knowing what the algorithm is even doing? People setting arbitrary limits like this is what leads to convoluted spaghetti, instead of just taking things on a case by case basis. Here’s a function from the Box2D code running a particularly complex algorithm for solving contact velocities https://github.com/erincatto/box2d/blob/411acc32eb6d4f2e96fc... .
It’s 310 lines long. It reads very well, and it looks very maintainable. It has very clear comments explaining the reasoning behind the harder parts of the code. Would you reject this code because it’s pretty long? I wouldn’t.
There is no such thing as too long or too short. There’s overengineered and there’s underengineered and there’s a sweet spot in the middle that has the perfect amount of engineering with the least amount of complexity (preferably no additional complexity than the original problem warranted). Sometimes, the problem at hand is inherently a large algorithm and requires many lines of code. Don’t split it up! It just makes it harder for future maintainers who now have to figure out if the additional functions are actually being used elsewhere or if they’re just there to make the code “pretty”.
-
How would you implement a simple collision system?
There is always the approach of looking at how an existing engine is implemented, such as box2d: https://github.com/erincatto/box2d
-
C++23: The Next C++ Standard
TIL Box2D must not be serious code because it doesn't use copious amounts of explicit temporaries[0].
And just for the record, I'm very glad Erin Catto decided to use operator overloading in his code. It made it much easier for me to read and understand what the code was doing as opposed to it being overly verbose and noisy.
[0]: https://github.com/erincatto/box2d/blob/main/src/collision/b...
-
Make a game engine in C++
For Physics Box2d can be used as a simple starting point.
-
Does anyone know any good open source project to optimize?
I suspect most C++ physics libraries like Box2D (https://github.com/erincatto/box2d) or Bullet3 (https://github.com/bulletphysics/bullet3) could really benefit a lot from SIMD.
-
what to start learning
for 2D physics have a look at Box2D it's amazing https://box2d.org/
What are some alternatives?
GLFW - A multi-platform library for OpenGL, OpenGL ES, Vulkan, window and input
Bullet - Bullet Physics SDK: real-time collision detection and multi-physics simulation for VR, games, visual effects, robotics, machine learning etc.
DiligentEngine - A modern cross-platform low-level graphics library and rendering framework
Chipmunk - A fast and lightweight 2D game physics library.
magnum - Lightweight and modular C++11 graphics middleware for games and data visualization
raylib - A simple and easy-to-use library to enjoy videogames programming
Ogre 3D - scene-oriented, flexible 3D engine (C++, Python, C#, Java)
LiquidFun - 2D physics engine for games
sokol - minimal cross-platform standalone C headers
PhysX - NVIDIA PhysX SDK
The-Forge - The Forge Cross-Platform Rendering Framework PC Windows, Steamdeck (native), Ray Tracing, macOS / iOS, Android, XBOX, PS4, PS5, Switch, Quest 2
box2d-lite - A small 2D physics engine