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

Investigate generating materials at editor time, rather than using an uber-shader #866

Open
kring opened this issue May 31, 2022 · 0 comments
Labels
performance Improvements to performance, including reductions in memory usage research Explore an idea or prototype a concept and share the results

Comments

@kring
Copy link
Member

kring commented May 31, 2022

Our default material for rendering tilesets does a lot of stuff. It has nodes that support:

  1. every glTF material feature
  2. three raster overlays
  3. a clipping layer

And there's a separate material that adds:

  1. water

This all makes it quite a heavy material, even when the tileset we're rendering doesn't use most of these features.

Creating materials at runtime is probably hard/impossible, but we still might see significant advantages from generating a material for a tileset at editor time. Much like Nithin did for metadata styling in #698.

Related to #287.

@kring kring added research Explore an idea or prototype a concept and share the results performance Improvements to performance, including reductions in memory usage labels May 31, 2022
@kring kring mentioned this issue May 31, 2022
30 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Improvements to performance, including reductions in memory usage research Explore an idea or prototype a concept and share the results
Projects
None yet
Development

No branches or pull requests

1 participant