tinyrenderer
stb
Our great sponsors
tinyrenderer | stb | |
---|---|---|
60 | 164 | |
19,305 | 25,008 | |
- | - | |
0.0 | 6.7 | |
5 months ago | 3 days ago | |
C++ | C | |
GNU General Public License v3.0 or later | 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.
tinyrenderer
-
From scratch OpenGL and shaders with raw Xlib
I don’t think that exists (I sure would like for it to), but until it does you could amuse yourself with:
- A 500-line (non-OpenGL-compatible) 3D rasterizer: https://github.com/ssloy/tinyrenderer/wiki.
- A “hello Wayland” app written in C without libwayland or anything else: https://gaultier.github.io/blog/wayland_from_scratch.html.
- A “hello X11” app written in x86-64 assembly(!) without libX11, libxcb, or anything else: https://gaultier.github.io/blog/x11_x64.html.
-
Tiny Compiler – Writing a Compiler in a Weekend
the tinyrenderer[1] project has been on my todos forever now. glad to see the author is writing more self-paced programming projects.
-
Is there space in this field for extreme cases like mine ?
- Game development - Unity3D project based learning in C#: https://learn.unity.com/ - Graphics - There was another user on r/GraphicsProgramming the other day (who teaches Computer Graphics at his university) that linked their lecture series for the entry year of their course here: https://tamats.com/learn/realtime-graphics/ - Project based learning: https://github.com/ssloy/tinyrenderer/wiki - Rendering API tutorials: https://vulkan-tutorial.com/, https://learnopengl.com/
-
How do I become a graphics programmer? – A guide from AMD Game Engineering team
There are a couple of excellent resources out there for implementing 3D rendering from scratch.
On that I cannot recommend enough is this github repo:
https://github.com/ssloy/tinyrenderer/wiki/Lesson-0:-getting...
If you are more of a visual learner, this guy is also a treasure trove:
-
Ask HN: What books or courses do you know similar to "From Nand to Tetris"?
Other people have mentioned ray-tracing in one weekend
If anyone is really interested in graphics I would also recommend TinyRenderer
https://github.com/ssloy/tinyrenderer/wiki
This one is a CPU-based rasterizing renderer
Its good if you want to get a good understanding of what a GPU does underneath
-
Trying to learn wgpu
I was in a similar position to you, and I first did this https://github.com/ssloy/tinyrenderer/wiki
- Where do I start learning graphics programming?
-
Recommendation for graphics experimentation project
Yes, my thoughts exactly, shader!=program on GPU. It's just a code which calculates pixel color or pixel position. See for example this: https://github.com/ssloy/tinyrenderer/blob/master/main.cpp. It's not GLSL or anything uploadable to GPU yet it's still a shader.
-
I have a few months to prepare for an interview. Is there a project that would get me at least part of the way there for the interview?
In terms of a project which would be worthwhile, I think building a software rasterizer from scratch is a useful first step. TinyRenderer is a great place to start. Looking at the high level overview of many graphics subjects, ScratchAPixel is a valuable resource. Theres also just great information in some of the rote graphics programming textbooks (Michael Abrash's Black Book fully available online from Jason Gregory, and this book is really interesting). The "RayTracer in a weekend" series is also (seemingly) very illuminating (no pun intended).
-
3D game shaders for beginners: step-by-step guide to SSAO, lighting, and more
been on my 3D todo list for a while. you might also like these:
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:
-
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?
sokol - minimal cross-platform standalone C headers
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
raylib - A simple and easy-to-use library to enjoy videogames programming
imgui-node-editor - Node Editor built using Dear ImGui
BodySlide-and-Outfit-Studio - BodySlide and Outfit Studio, a tool to convert, create, and customize outfits and bodies for Bethesda games.
ZXing - ZXing ("Zebra Crossing") barcode scanning library for Java, Android
deko3d - Homebrew low level graphics API for Nintendo Switch (Nvidia Tegra X1)
freetype-gl - OpenGL text using one vertex buffer, one texture and FreeType
Pangolin - Pangolin is a lightweight portable rapid development library for managing OpenGL display / interaction and abstracting video input.
ImageMagick - 🧙♂️ ImageMagick 7
3d-game-shaders-for-beginners - 🎮 A step-by-step guide to implementing SSAO, depth of field, lighting, normal mapping, and more for your 3D game.
Cppcheck - static analysis of C/C++ code