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
Currently, textures are encoded to the model file itself. This makes sense, as packaging everything into one model file is favorable.
However, textures often need to be opened in other programs, so to bypass this, blockbench prompts users to make a copy of every texture in a file externally. This isn't inherently problematic, but there are cases where only working with external files is favorable.
For example, I would like to keep track of my models in version control, as they are just json files, while also tracking my binary image files in something like git LFS. Currently I am essentially forced to keep a copy of each texture file in my version history for every commit I make.
An option (saved in the model file itself) to only load textures from files would make collaboration much simpler, especially when combined with using relative paths (#906).
Additionally, the ability to turn this option on or off by default for new files would also be very appreciated.
The text was updated successfully, but these errors were encountered:
0ffz
changed the title
[Suggeston] Option to not encode images to .bbmodel files
[Suggeston] Option to not encode textures to .bbmodel files
May 29, 2021
Currently, textures are encoded to the model file itself. This makes sense, as packaging everything into one model file is favorable.
However, textures often need to be opened in other programs, so to bypass this, blockbench prompts users to make a copy of every texture in a file externally. This isn't inherently problematic, but there are cases where only working with external files is favorable.
For example, I would like to keep track of my models in version control, as they are just json files, while also tracking my binary image files in something like git LFS. Currently I am essentially forced to keep a copy of each texture file in my version history for every commit I make.
An option (saved in the model file itself) to only load textures from files would make collaboration much simpler, especially when combined with using relative paths (#906).
Additionally, the ability to turn this option on or off by default for new files would also be very appreciated.
The text was updated successfully, but these errors were encountered: