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
{{ message }}
This repository was archived by the owner on Jun 30, 2022. It is now read-only.
Hello, we have an issue with the Wireframe shader for iOS. We tried using the shader from Assets/Shaders/Wireframe/ShaderGraph with the material from Assets/Shaders/Wireframe/Materials that we put in our project in Unity 2020.3.30.f1.
When we try using it as the material on our Mesh Prefab for our ARMeshManager, the shader does not display a wireframe and the material appears entirely white.
Tested on iPad Pro (11 inch) 3rd generation, iOS 15.4.1.
Is there anything that we're missing?
The text was updated successfully, but these errors were encountered:
When I checked out the project, the shader graph is essentially created using the older version and not been updated to the latest shadergraph version and broken. Unity never updates their sample/example projects along with the plugin... which is sad...
Once the shader graph is updated to the new version, the Albedo and WireColor needs to be adjusted. I opened the demo project in another unity editor and let unity do it's thing updating. I created a brand new shader graph in my project and copied the nodes to my new shader and adjusted the properties.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, we have an issue with the Wireframe shader for iOS. We tried using the shader from Assets/Shaders/Wireframe/ShaderGraph with the material from Assets/Shaders/Wireframe/Materials that we put in our project in Unity 2020.3.30.f1.

When we try using it as the material on our Mesh Prefab for our ARMeshManager, the shader does not display a wireframe and the material appears entirely white.
Tested on iPad Pro (11 inch) 3rd generation, iOS 15.4.1.
Is there anything that we're missing?
The text was updated successfully, but these errors were encountered: