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
After doing some tests with ./preview ProfilePic it's pretty clear that loading textures individually is simply too slow to render them all at once, which we may want to do for notedeck_viz
We can create a giant texture with all of the profile pictures and use that as a texture atlas. For everything else we can load it dynamically as we need it.
I found some example code that uses the same underlying texture handles in different TextureIds:
After doing some tests with
./preview ProfilePic
it's pretty clear that loading textures individually is simply too slow to render them all at once, which we may want to do fornotedeck_viz
We can create a giant texture with all of the profile pictures and use that as a texture atlas. For everything else we can load it dynamically as we need it.
I found some example code that uses the same underlying texture handles in different TextureIds:
On closing of the application we could write this atlas to disk, and then load it again on next startup?
The text was updated successfully, but these errors were encountered: