Graphics

I think you'd probably want a different render layer with different post effect settings so your weapons can have post-processing as well. I think you can do this in the editor with gui configs instead of changing code. I'm pretty sure all of SRP is in C# and is "open source" as in source available and editable. https://github.com/Unity-Technologies/Graphics/tree/master/P...

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

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: https://github.com/Unity-Technologies/UnityCsReference The code that interfaces directly with the platform API at the C++ level is restricted (you can get access but it's not really a viable option for a beginning graphics programmer :)). For many platforms the APIs themselves are proprietary and therefore that code cannot be shared easily. There's pretty good tooling support around graphics debugging: https://docs.unity3d.com/Manual/RenderDocIntegration.html https://docs.unity3d.com/Manual/FrameDebugger.html