Darl
@darl.cat
Furry | Dev / IT | Administrator / staff for a few things | https://am.darl.cat/ | Adult
It's not actually loading them as theorized; see my response here on how to test for yourself bsky.app/profile/darl...
This only happens "instantly" when you swap to blinn-phong because you have the item selected which causes all textures on it (incl. fallbacks) to load. If you watch yourself removing a material from an object on a 2nd viewer with an empty cache you will see it have to load the non-shared fallbacks.
May 9, 2025 at 4:01 PM
It's not actually loading them as theorized; see my response here on how to test for yourself bsky.app/profile/darl...
Selecting an object, even one you do not have modification rights for, will cause all textures on it to load. For my test to work, you will need to not select the item or view the textures that make up the fallbacks prior to the test.
May 9, 2025 at 3:43 PM
Selecting an object, even one you do not have modification rights for, will cause all textures on it to load. For my test to work, you will need to not select the item or view the textures that make up the fallbacks prior to the test.
This only happens "instantly" when you swap to blinn-phong because you have the item selected which causes all textures on it (incl. fallbacks) to load. If you watch yourself removing a material from an object on a 2nd viewer with an empty cache you will see it have to load the non-shared fallbacks.
May 9, 2025 at 3:42 PM
This only happens "instantly" when you swap to blinn-phong because you have the item selected which causes all textures on it (incl. fallbacks) to load. If you watch yourself removing a material from an object on a 2nd viewer with an empty cache you will see it have to load the non-shared fallbacks.