Face Texture are ignored on export.

[SinsOfSeven]

Face Textures, and other texture only objects are ignored on export because they are not part of the scene, and not added to the mod_file data sent to the templates. The template can still generate the sections by using hash_data instead inside the template, but not all the export flags are sent to the template engine.

from: Satan1c

Related Pull Request
#62

• Face extracted w/o model, only texture
• cuz they're w/o model, they're not on scene
• xxmi tools ignore anything that is not in scene, when creating mod_file

Technically everything works w/o any xxmi tools editing
But I've exposed some variables like copy_texture, to skip face placing if textures are not copied

Problem number 2
In ZZZ chars in char menu may be drawn from Face/Hair, so handling = skip may have unstable bug to skip draw of everything but face/hair

To fix that, just index_count filter is enough
So I've added that property to Part class, to expose it to template, and also edited gui_collect extract, to contain index_count in hash.json, for reading from hash_data, or easier manual editing of mods

//...
        "object_indexes": [
            0,
            12120,
            15951
        ],
        "object_index_counts": [
            12120,
            3831,
            60
        ],
        "object_classifications": [
            "A",
            "B",
            "C"
        ],
//...

[SinsOfSeven]

We've known for awhile that we needed to rework how data is sent to the templates.

First, I want to clarify something I'm not sure about. I don't know if hash_data is an unmodified copy of the hash.json but if it isn't, it should be. And it should be able to represent data that is not part of the standard format if it isn't already able to. For example, if I add "Clown_Motels_Near_Me" = [] to a hash.json I want it sent to the template unmodified.

Second, if we are going to send the export flags to the template, they should be their own data object export_settings, which should just be the information filled out from the export panel.

Export Settings

• Ignore hidden objects
• Only export selected
• Apply modifiers and shapekeys
• Normalize weights to format
• etc
• Credit string

export_settings.ignore_hidden_objects
export_settings.modifiers_and_shapekeys
export_settings.normalize_weights
export_settings.credit

Additionally, we should probably provide information inside mod_file about objects that are texture only, or provide a second object for them. We can basically just have a list of "unhandled" objects, which are in the hash.json, but not part of the mod export. I don't know the best way to deal with this.

And Finally, we need to formalize the way we pass data in mod_file to make it easier to access. I had a thought about only accessing the data from hash.json through hash_data, by giving the objects inside mod_file the data member names to retrieve values instead of providing them for comfort.

match_first_index = {{ hash_data[ COMPONENT_IDX ].object_indexes[ OBJECT_IDX ] }}

If we do end up making big changes to the Template data, we'll need to make a simple migration guide for people who have already used them to customize their mods. This also leads into adding jinja plugins for things like Regex. Maybe we can consider opening a different issue, or a discussion for what to add and what format to use.

[leotorrez]

fixed as of 1.6.3