UnityCsReference VS tinyrenderer

I've checked their CS reference code on their Github, both here and here, but I want to dive a little deeper - specifically, I want to know what they're actually doing when determining validity of the Matrix4x4.

Yep, but beyond just decompiling it, the c# layer of code is on GitHub: https://github.com/Unity-Technologies/UnityCsReference

https://github.com/Unity-Technologies/UnityCsReference/blob/master/Runtime/Export/Scripting/UnityEngineObject.bindings.cs (after 2019.1)

The code where the method filtering for the Animation Event Inspector is done, is here (line 190). Is it possible to do something like this? That repository explicitly says:

No reason, you can look at the source of encapsulate

There isn't really a straight forward way to do this, even the QualitySettings editor uses Serialised Properties to get at the data. (Line 343 in QualitySettingsEditor)

This is awesome, thank you! I'm most curious about their Runtime

I think if you want to get into graphics programming you do want to work with OpenGL and similar things, because at the very least you need to understand it all (and decide what parts of engines to use and what to ignore when you get to whole games). It's also worth saying that while you can only publicly get the references in Unity you do get source access at the higher subscription tiers you'd use at a game studio.

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