dragonruby-game-toolkit-contrib
stb
dragonruby-game-toolkit-contrib | stb | |
---|---|---|
15 | 164 | |
190 | 25,314 | |
0.5% | - | |
6.0 | 6.4 | |
8 days ago | 9 days ago | |
Ruby | C | |
MIT License | GNU General Public License v3.0 or later |
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.
dragonruby-game-toolkit-contrib
-
DragonRuby Game Toolkit - Tech demo showing what Ruby is capable of: lighting, camera movement/parallax, physics and collision, all at 60 fps.
It’s a combination of the following sample apps: 1. Axis align bounding box collision 2. Simple camera 3. Lighting
-
DragonRuby Game Toolkit - Game development gives such a different realm of problems to solve that you just don't see with app dev. I'd encourage y'all to give it a try (it's extremely rewarding). Here's an example.
The Indie and Pro version of DR let you create your own C Extensions. These sample apps guide you through the process step by step.
-
I notice that there aren't many gaming engines that support Ruby script. I'm considering working on a more manageable project that will incorporate MRuby into the Love engine.
What we can safely open source is here (we try to expand this repo as much as we can): https://github.com/DragonRuby/dragonruby-game-toolkit-contrib
-
With RubyConf 2022 around the corner, I added a bit more polish to DragonRuby's tech demo. Hope y'all can make it out to my talk where I'll be showing this off :-)
DragonRuby is awesome to work with. They’ve put together tons of super useful samples: https://github.com/DragonRuby/dragonruby-game-toolkit-contrib/tree/master/samples
-
To celebrate the 3-year anniversary of DragonRuby Game Toolkit (and 8 years as an Indie game dev), I'm making the game engine free for the next 3 days. Tips for succeeding as an Indie in the comments too.
There are some sample apps that show how to make buttons, so most guis would be a combination of using sprites and testing for click events. The tricky part is gonna be a fully functional text box. The dragonruby heads up display has one and the machinery to get that to work is here. A few people on the Discord server have actually pulled this off and have created toy IDEs with it ha.
-
With RubyKaigi 2022 kicking off, I've made DragonRuby Game Toolkit free. Hope you enjoy and feel free to AMA about the engine.
We have a bullet hell sample app :-) https://github.com/DragonRuby/dragonruby-game-toolkit-contrib/tree/master/samples/99_genre_arcade/bullet_hell
-
Ruby rendering 4K scenes with physics at 60fps - DragonRuby Game Toolkit (link to source code in the comments)
The full implementation is ~350 lines of code. Here's the source.
-
Soft body physics in Ruby (DragonRuby Game Toolkit) :-)
It might help to start with a simpler example. This is Pong written with the same structure. The general theme is to start simply and introduce abstraction at the “last responsible moment” as opposed to upfront: https://github.com/DragonRuby/dragonruby-game-toolkit-contrib/blob/master/samples/99_genre_arcade/pong/app/main.rb
-
Ruby is good for the soul. Have fun with it. That's the most important thing. Build a game. Here's one I'm working on (source code + playable link in the comments).
There are a ton of sample apps you can go through here: https://github.com/DragonRuby/dragonruby-game-toolkit-contrib/tree/master/samples
-
Flappy Bird clone written in 360 lines of Ruby (DragonRuby Game Toolkit). Link to playable game + source in the comments.
Working src link: https://github.com/DragonRuby/dragonruby-game-toolkit-contrib/blob/master/samples/99_genre_arcade/flappy_dragon/app/main.rb
stb
- Lessons learned about how to make a header-file library (2013)
-
Nebula is an open-source and free-to-use modern C++ game engine
Have you considered not using an engine at all, in favor of libraries? There are many amazing libraries I've used for game development - all in C/C++ - that you can piece together:
* General: [stb](https://github.com/nothings/stb)
- STB: Single-file public domain libraries for C/C++
-
Writing a TrueType font renderer
Great to see more accessible references on font internals. I have dabbled on this a bit last year and managed to have a parser and render the points of a glyph's contour (I stopped before Bezier and shape filling stuff). I still have not considered hinting, so it's nice that it's covered. What helped me was an article from the Handmade Network [1] and the source of stb_truetype [2] (also used in Dear ImGUI).
[1] https://handmade.network/forums/articles/t/7330-implementing....
[2] https://github.com/nothings/stb/blob/master/stb_truetype.h
-
Capturing the WebGPU Ecosystem
So I read through the materials on mesh shaders and work graphs and looked at sample code. These won't really work (see below). As I implied previously, it's best to research/discuss these sort of matters with professional graphics programmers who have experience actually using the technologies under consideration.
So for the sake of future web searchers who discover this thread: there are only two proven ways to efficiently draw thousands of unique textures of different sizes with a single draw call that are actually used by experienced graphics programmers in production code as of 2023.
Proven method #1: Pack these thousands of textures into a texture atlas.
Proven method #2: Use bindless resources, which is still fairly bleeding edge, and will require fallback to atlases if targeting the PC instead of only high end console (Xbox Series S|X...).
Mesh shaders by themselves won't work: These have similar texture access limitations to the old geometry/tessellation stage they improve upon. A limited, fixed number of textures still must be bound before each draw call (say, 16 or 32 textures, not 1000s), unless bindless resources are used. So mesh shaders must be used with an atlas or with bindless resources.
Work graphs by themselves won't work: This feature is bleeding edge shader model 6.8 whereas bindless resources are SM 6.6. (Xbox Series X|S might top out at SM 6.7, I can't find an authoritative answer.) It looks like work graphs might only work well on nVidia GPUs and won't work well on Intel GPUs anytime soon (but, again, I'm not knowledgeable enough to say this authoritatively). Furthermore, this feature may have a hard dependency on using bindless to begin with. That is, I can't tell if one is allowed to execute a work graph that binds and unbinds individual texture resources. And if one could do such a thing, it would certainly be slower than using bindless. The cost of bindless is paid "up front" when the textures are uploaded.
Some programmers use Texture2DArray/GL_TEXTURE_2D_ARRAY as an alternative to atlases but two limitations are (1) the max array length (e.g. GL_MAX_ARRAY_TEXTURE_LAYERS) might only be 256 (e.g. for OpenGL 3.0), (2) all textures must be the same size.
Finally, for the sake of any web searcher who lands on this thread in the years to come, to pack an atlas well a good packing algorithm is needed. It's harder to pack triangles than rectangles but triangles use atlas memory more efficiently and a good triangle packing will outperform the fancy new bindless rendering. Some open source starting points for packing:
https://github.com/nothings/stb/blob/master/stb_rect_pack.h
https://github.com/ands/trianglepacker
-
Www Which WASM Works
The STB headers are mostly built like that: https://github.com/nothings/stb
You could also add an optional 'convenience API' over the lower-level flexible-but-inconvenient core API, as long as core library can be compiled on its own.
In essence it's just a way to decouple the actually important library code from runtime environment details which might be better implemented outside the C/C++ stdlib.
It's already as simple as the stdlib IO functions not being asynchrononous while many operating systems provide more modern alternatives. For a specific type of library (such an image decoder) it's often better to delegate such details to the library user instead of circumventing the stdlib and talking directly to OS APIs.
-
File for Divorce from LLVM
My stuff for instance:
https://github.com/floooh/sokol
...inspired by:
https://github.com/nothings/stb
But it's not so much about the build system, but requiring a separate C/C++ compiler toolchain (Rust needs this, Zig currently does not - unless the proposal is implemented).
-
What C libraries do you use the most?
STB Libraries: https://github.com/nothings/stb
-
[Noob Question] How do C programmers get around not having hash maps?
stb_ds is also very popular.
- Is there an existing multidimensional hash table implementation in C?
What are some alternatives?
MacRuby - MacRuby is an implementation of Ruby 1.9 directly on top of Mac OS X core technologies such as the Objective-C runtime and garbage collector, the LLVM compiler infrastructure and the Foundation and ICU frameworks.
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
dragon-game - Dragon Vs Dragon Game
imgui-node-editor - Node Editor built using Dear ImGui
minigl - A minimal Game Library built on top of the Gosu gem.
ZXing - ZXing ("Zebra Crossing") barcode scanning library for Java, Android
dragonruby-zif - Zif: A Drop-in Framework for DragonRuby GTK
freetype-gl - OpenGL text using one vertex buffer, one texture and FreeType
android.cr - Create Android applications using Crystal and the NDK
ImageMagick - 🧙♂️ ImageMagick 7
mrbweb-v - A test project that uses mruby to improve the processing of binary code.
Cppcheck - static analysis of C/C++ code