You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into a problem upgrading to the package-based version, while using my own Custom Rendering Pipeline.
The default materials from the package don't update to the custom rendering pipeline's default material and shader, causing them to be pink.
FIX: I modified the MaterialUtility::GetRenderPipelineType to return the render pipeline's name instead of an empty string to trigger updating the default materials.
The text was updated successfully, but these errors were encountered:
This is a bug. That part of the code should have actually been removed, but I missed that when refactoring. There is no longer a need for checking sub-directories for materials, as the default ones are updated to the correct shader, based on the pipeline default shader. I'll get to this as soon as I can. Thanks for the heads up!
nukeandbeans
pushed a commit
to nukeandbeans/realtime-CSG-for-unity
that referenced
this issue
Apr 14, 2022
I ran into a problem upgrading to the package-based version, while using my own Custom Rendering Pipeline.
The default materials from the package don't update to the custom rendering pipeline's default material and shader, causing them to be pink.
FIX: I modified the MaterialUtility::GetRenderPipelineType to return the render pipeline's name instead of an empty string to trigger updating the default materials.
The text was updated successfully, but these errors were encountered: