If you want to protect your model against ripping software or attachment edits, this option may be beneficial. Although the intended purpose of the wide string data is to allow for an extended character set when naming materials or textures, it can also serve as a means of protection against software that isn't fully conformant with the.

im format often fail to parse (or crash) when encountering wide strings. im/.kin files (the only notable example being the PB15 fireman), tools dealing with the. As this type of string data is rarely used within exported. kin files, and automatic texture.txt metadata generation for any of the mesh's dependent texture files.Īn export option is provided to force the usage of wide strings within the exported.

The exporter currently supports the serialization of vertex and index data of triangle meshes (meshes will be automatically triangulated on export), texture coordinates, both per-vertex and per-face normals, vertex tangents (optional), bounding box export (optional), material data from the Principled BSDF node (see below, both solid RGB colors and texture slots supported), animated scenes (for either armature or dummy object hierarchies) through the generation of separate. This results in a much tidier and easily maintained codebase, faster exports for content creators, and fine-tuned control over what versions of the JET/E2 game engines the file will work in and what data the file will contain (tangents, skinning, texture slots, etc).

Rather than relying on the old and frustratingly slow importer executable the pre-2.8 exporter used (TrainzMeshImporter.exe, created by N3V Games), the 2.8 exporter writes to the indexed mesh file directly instead of using XML as a middleman. This exporter is designed to be a replacement for the well-used legacy exporter written by USCHI0815 (Torsten), which became unusable after the Python API changes made in Blender 2.8. A WIP, modern, post-2.8 indexed mesh exporter for Trainz and the Auran JET engine.

Blender to export vray mesh