UnityCsReference VS Graphics

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.

URP: https://github.com/Unity-Technologies/Graphics/blob/master/Packages/com.unity.render-pipelines.universal/Shaders/Lit.shader

Graphics (shaders mostly) https://github.com/Unity-Technologies/Graphics

it already is happening (kinda), they are modularizing their engine, and all the new parts are made open source

biggest part what their graphics stack https://github.com/Unity-Technologies/Graphics (only the scripting part)

competition is growing, unreal is fully open source, and more and more people have been asking for the source, there was even some drama few years ago when unity DMCA'd (if i remember correctly) a reference source code of unity engine (decompiled) on github, then unity made it officially available on their github: https://github.com/Unity-Technologies/UnityCsReference after users complained about it

wich already proved effective and caused them to fix a huge performance issue shortly after: https://github.com/Unity-Technologies/UnityCsReference/pull/...

https://github.com/Unity-Technologies/Graphics/blob/cfd0466579c654441290c0c1645b1f083c4de886/com.unity.render-pipelines.core/ShaderLibrary/BSDF.hlsl https://github.com/CJT-Jackton/URP-Iridescence-ExampleThis is what i used

It also depends on what you want to learn, theres many topics that in a AAA production are made by completely different people - sub topics if you so will: URP and HDRP has public source code for all the shaders, but theres alot of internal Unity Macros that are not well documented: https://github.com/Unity-Technologies/Graphics

The light intensity falloff is still something I'm working on. The implementation utilizes structs and functions from the Unity URP library, more specifically the RealtimeLights.hlsl file (https://github.com/Unity-Technologies/Graphics/blob/master/com.unity.render-pipelines.universal/ShaderLibrary/RealtimeLights.hlsl). Within the light struct there exists variables for both distance attenuation and shadow attenuation, in short this library calculates how much the light intensity should decrease/increase based on distance, and then it's up to the cel shader to properly threshold this value in a correct way.

Unity render pipeline source is available here: https://github.com/Unity-Technologies/Graphics

All the C# code running in the editor and runtimes is here: