Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebGPURenderer: Fix render pipeline selection. #24373

Merged
merged 1 commit into from
Jul 20, 2022
Merged

Conversation

Mugen87
Copy link
Collaborator

@Mugen87 Mugen87 commented Jul 20, 2022

Fixed #24371.

Description

This PR ensures lines and line segments with the same geometry and material do not share the same render pipeline.

@Mugen87 Mugen87 merged commit b15c181 into mrdoob:dev Jul 20, 2022
@Mugen87 Mugen87 added this to the r143 milestone Jul 20, 2022
@mrdoob
Copy link
Owner

mrdoob commented Jul 21, 2022

Nice!

Although... not sure about all these methods we have added to the renderer.
Ideally WebGPURenderer should expose the same methods WebGLRenderer expose.

@Mugen87
Copy link
Collaborator Author

Mugen87 commented Jul 21, 2022

How about making the methods private (via the underscore syntax for now)?

Although private would not be 100% correct since private methods are normally only used by the respective class. However, methods like getCurrentEncoding() are used at different places in the WebGPU modules. So in some sense getCurrentEncoding() is "internally public".

abernier pushed a commit to abernier/three.js that referenced this pull request Sep 16, 2022
snagy pushed a commit to snagy/three.js-1 that referenced this pull request Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebGPURenderer renders only Lines or LineSegments, but not both.
2 participants