Remove Sprite#shader and Mesh#shader properties
See original GitHub issueAccording to https://github.com/pixijs/pixi.js/issues/2290#issuecomment-252630058, Sprite#shader doesn’t do anything, even though it exists and is documented to work.
My testing suggests that the same is true for Mesh#shader.
Should these properties just be removed, including their documentation?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Custom shader for sprite · Issue #2290 · pixijs/pixijs - GitHub
If you assign a filter to the .shader property of the sprite, the shader for that ... Remove Sprite#shader and Mesh#shader properties #3086....
Read more >Changing the Sprite Renderer's Color property has no effect in ...
I have a material with custom surface shader of which I want to change the "Color" in the Sprite Renderer. However, changing the...
Read more >Mesh Shader | DirectX-Specs - Microsoft Open Source
This document describes a next-generation replacement for Vertex and Geometry shaders in a D3D12 pipeline called “Mesh shader”. Mesh shader support in D3D12 ......
Read more >Coming to DirectX 12— Mesh Shaders and Amplification ...
D3D12 is adding two new shader stages: the Mesh Shader and the ... and a single index value applies to all the vertex...
Read more >Using Mesh Shaders for Professional Graphics
In this post, I offer a detailed look over mesh shader… ... Mesh and task shaders have some new unique properties compared to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@GoodBoyDigital is working on great PR that supports them.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.