When the render pipelines were introduced, I opted to keep my asset store projects on the built-in pipeline to prevent a situation where I couldn’t change back to built-in if I ever needed to.
I understand there’s an upgrade tool, and for game developers this is an awesome tool to upgrade a project just once.
But if I’m developing an asset (let’s say it’s primarily materials as there are different shaders for the pipelines) and I want to provide support for all 3 render pipelines, what does the workflow look like?
Are there tools or guides already available for this process, or do I need to have my base project in the built-in pipeline, and convert a copy of the project to HDRP and URP with separate uploads each time I want to publish (and update) a project?
You can do all of it in one project. You do have to have copies of your assets, specifically materials and shaders.
What some of the better organized assets do is to provide at least RP specific materials that can be easily replaced for all meshes.
To develop assets for multiple RPs you‘d create the necessary RP assets for urp and hdrp in your project, then under project settings assign one of the RP assets and you‘ll be using that specific RP. Set it back to None to go back to legacy RP. Pretty sure you could write a script to automate this.
1 Like