tinyrenderer VS learn-wgpu

C++: How OpenGL works: software rendering in 500 lines of code

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.

the tinyrenderer[1] project has been on my todos forever now. glad to see the author is writing more self-paced programming projects.

[1]: https://github.com/ssloy/tinyrenderer

- 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/

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:

https://www.youtube.com/watch?v=ih20l3pJoeU

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

I was in a similar position to you, and I first did this https://github.com/ssloy/tinyrenderer/wiki

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.

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).

Nice.

Speaking of Snake game, if you want to go even deeper, you can try to use the wgpu crate to combine Rust and WebGPU to write everything from scratch. Here is the tutorial:

https://sotrh.github.io/learn-wgpu/#what-is-wgpu

I once wrote a code editor with wgpu, from font rendering to char/line state management (very rough) for music live coding:

https://github.com/glicol/glicol-wgpu

It runs in browsers, even including Safari!

https://sotrh.github.io/learn-wgpu/ This is probably the best resource out there for learning wgpu specifically. If you're unfamiliar with graphics, the learnopengl one is good. If you've got experience though, jumping right into that one is a shout or looking at some vulkan ones as they're pretty similar in terms of architecture.

- https://sotrh.github.io/learn-wgpu

Most of The WGPU I learnt is from https://sotrh.github.io/learn-wgpu/ but it doesn't really talk about designing n stuff, I thought of checking out the source code for Bevy or even games like veloren. But well, their codebases are pretty big to get started in the first place.

So I was wondering if opting for option 1 would be better to begin with. OpenGL has a much bigger community and wgpu only has its documentation which I hear is not quite up there yet. There is this excellent tutorial for wgpu that I read through, but it seems like wgpu can be a lot more complicated than starting with OpenGL.

I started with wgpu tutorial (https://sotrh.github.io/learn-wgpu/) since I like the idea of portability and it's a Rust-first library, but it seems I'm missing some foundations of how CG works in general: the code is given, a little of explanation like it assumes I already know something, maybe I'm wrong, but I wish there was a longer explicit version.

If you haven't seen it: https://sotrh.github.io/learn-wgpu/ is a good introduction that will explain most of what you asked, then can refer to rend3d or bevys renderer to see how a render graph works.