This is a template Scriptable Render Pipeline (SRP) package for Unity. It contains boiler plate code to be used as starting point when creating custom render pipelines. It also already creates base files to distribute and install this custom SRP as a package for Unity.
- Create a Github repository from this template by clicking on the
Use this templatebutton at the top. - Edit
package.jsonfile to configure the package manifest.- Note: If you change package name, be sure to all change shader includes.
- Update
README.md,CHANGELOG.mdandLICENSE.mdfiles to reflect the contents of your package.
- In Unity, click at the top bar on
Window -> Package Manager. - Follow these instructions to install it as a local package.
- Create a render pipeline asset by clicking on
Assets -> Create -> Custom Render Pipeline Asset. - In Graphics Settings, assign the newly created render pipeline asset in the
Scriptable Render Pipeline Settingsfield.
The package follows the Unity's Package Manager recommended layout
package.jsondescribes the package metadata required by Package Manager.README.mdcontains project description used by Github.CHANGELOG.mdcontains changelog entries. This is used by Package Manager to display changelog information in the Editor.LICENSE.mdcontaints package license information. This is used by Package Manager to display license information in the Editor.- Editor
Unity.com.render-pipelines.Editor.asmdefthe assembly definition file for editor scripts.
- Runtime
CustomRenderPipeline.cs- Contains rendering related code. Edit this file to add the desired rendering logic.CustomRenderPipelineAsset.cs- Creates render pipeline instance. Can hold render pipeline resources.Unity.com.render-pipelines.asmdef- the assembly definition file for editor scripts.
- ShaderLibrary
Core.hlsl- Includes all basic shader necessary files.UnityInput.hlsl- Contains declaration of all built-in Unity shader constants.
- Shaders
Unlit.shader- Unlit shader example.
- Tests
- Contains Editor and Runtime test folders. To be used with UnityTestRunner to write automated package tests.
- Documentation~
index.md- Contains index page for documentation. This is used by Package Manager to display package docs.
- Samples~
- Add any sample scenes to your package here. This will be displayed by Package Manager.