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.

Sign up for GitHub

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

Jump to bottom

greedy meshing? #404

Closed
suprohub opened this issue Oct 13, 2024 · 6 comments
Closed

greedy meshing? #404

suprohub opened this issue Oct 13, 2024 · 6 comments
Labels
question Usability question

Comments

@suprohub
Copy link

No description provided.

@parasyte parasyte added the question Usability question label Oct 13, 2024
@parasyte
Copy link
Owner

Is there a question, here?

@suprohub
Copy link
Author

Yes

@suprohub
Copy link
Author

suprohub commented Oct 14, 2024 •
edited
Loading

And what about winit 0.30? I created fork where winit 0.30.5 and wgpu 22.1.0.
But all examples are broken

@parasyte
Copy link
Owner

What's the question wrt greedy meshing?

winit 0.30 was discussed recently in #403. wgpu 22 has an open PR in #402.

@suprohub
Copy link
Author

What's the question wrt greedy meshing?

winit 0.30 was discussed recently in #403. wgpu 22 has an open PR in #402.

Can we implement greedy meshung?

@parasyte
Copy link
Owner

pixels.context() and pixels.adapter() give you access to all of the wgpu internal state. You can use it to implement any graphics technique you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Usability question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@parasyte @suprohub