Zylann
commented
1 year ago packed_tex and packed_texarr files are not a real format. They were made up in the Godot 3 version of the plugin. The idea was to trick Godot's import system to make them behave like Texture2D and TextureArray resources, while still having some info about which images they were compsed from.
They were removed when the plugin was ported to Godot 4, mainly because Godot doesn't expose enough APIs to import custom textures. In Godot 3 the code to import them required to rewrite the Godot's entire texture importer in GDScript (cuz you can't just "inherit" something or call some helper to do what Godot does). As a result, it was flawed and bound to break as soon as Godot's internal logic changes. Porting this to Godot 4 became unbearable with all the new changes and more non-exposed logic. So instead now this workflow saves plain PNGs that get configured to import as texture arrays, therefore Godot's builtin import is directly used instead. One downside is that the importer doesn't remember the source files anymore.
That needs to be removed from the docs though...
lorddevereux
In Godot 4.1.1, it seems to be impossible to import packed_texarr files.
To reproduce:
In the Output console: "No loader found for resource: res://my_file.packed_texarr." "res://addons/zylann.hterrain/tools/texture_editor/set_editor/texture_set_editor.gd:410 - Assertion failed"
The assertion that fails is the load() call returned null.
My rudimentary understanding of Godot's plugin system leads me to suspect that it needs to be told how to handle a packed_texarr file but I can't figure out where or what I need to add to make this work. Perhaps this hasn't yet been discovered under Godot 4.
I really hope I'm not just being dumb here. Am I doing something wrong?