Missing multiple source packages.

[MegumiKasuga]

Problems

I'm trying to construct a MTB Model Importer under the guidance of your Application.
However I have found multiple package missed in your app.
These classes are significantly important for me to understanding the structure of MTB models.
The following packages are missing:

1. net.fexcraft.app.json.*
2. net.fexcraft.lib.*

Expected

Please provide packages mentioned above.

What's More

I'm now working on an multi-type model loader on NeoForge-mc1.21.1.
It would be undoubtedly helpful if I could get more help about MTB or other Flan's Model Type from you.

[Fexcraft]

Packages

Most of my projects are setup in a way that they expect other of my projects in the same parent folder.
e.g.

Github/
    FMT/
    FCL/
    FVTM/
    etc/

For FMT source you also need Fexcraft/FCL to be cloned locally, the gradle is setup to automatically include the source into the project.
(FCL has the Json as a github dependency because the Json repository does not change as often.)

side note: my code setup does not work with Eclipse IDE iirc; it's fine on IntelliJ IDE

SMP Toolbox & Flansmod

.mtb model files are originally from a software called Minecraft SMP Toolbox 2.0.
The website for it is erroring (http code 5xx) since a few years now, usually you can still find support and an installer download link on the Minecraft-SMP.de Discord Server (Community Managed).

FlansMod models used a slightly modified TMT (Turbo Model Thingy), it's a custom model rendering library.
You may be still able to find the original post and download for it on Minecraft Forums.
The main difference to original TMT is the addition of Shapeboxes.
Shapeboxes are boxes where each corner can have a custom offset away from the standard box size itself.

TMT also supports Cylinders and Spheres but that went mostly unused in Flansmod

Flansmod Model structure was usually predefined fields of TMT arrays, where each TMT object would be a box/shapebox.
e.g.

ModelRendererTurbo[] bodyModel = new ModelRendererTurbo[...]
bodyModel[2] = new ModelRendererTurbo(...);
bodyModel[2].addBox(...);
bodyModel[2].rotationPointX = 0;

There were various modelling limitations due the nature of the model code but I will not go into details here since it's a separate topic to model loading itself.

The mods (which I am aware of) that still use a TMT branch with Shapeboxes are:

• FlansMod Legacy
• FCL / Fexcraft Mods (mostly replaced to use FRL though)
• Traincraft (originally FCL based but now TC optimized iirc)

FMT & My Mods

FMT (Fex's Modelling Toolbox) in earlier versions also used TMT for rendering, but now it uses FRL.
FRL (Fex's Rendering Library) is just a simple similar library used in my mods and FMT.
There is currently an FRL Renderer implementation for FMT (standalone), MC 1.12 (static pipeline) and MC 1.20/26.1 (potentially unoptimized).
The Minecraft implementation of FRL is part of FCL.

FMT was made with FVTM style model export in mind, where insteadof predefined arrays, a model can have any amount of groups with any amount of elements and animations. Cylinders and experimental Shapes are in use.

mtb format

• .mtb are essentially a zip file that includes a texture (.png), config (likely flansmod specific) and model (txt) file
• the model txt contains the data about the boxes (the importer in FMT was originally by @EternalBlueFlame )
• the box data is used to construct a TMT object, with methods like addBox or addShapebox, it also contains rotation and translation values from origin
• the TMT methods create "Polygon" and "Vertex" objects which then get used by the renderer to pass this data to opengl

Solutions?

I do not know your definition of "import", do you want to import in the sense of converting it to another model format or import it directly into minecraft? There's various ways to handle this, for example:

• implement your own TMT fork in your library and use the TMT polygons/vertex in your render code
• make a software that turns .mtb files into a more suitable format
• just use FMT to import .mtb and export into another format

Just more Trivia

• I made my own obj-like model format that is fully byte-encoded called "Byte Encoded Object".bob/.beo , it takes far less space than .obj but holds the same data! Example on how easy to integrate it can be: Alternative Model Format Loader EternalBlueFlame/Traincraft-5#698 or BEO Model Loader in FVTM
• BOB/BEO model format can be exported from FMT.
• FMT can import uncompiled smp toolbox models in java form
• FVTM (mc vehicle mod) can load uncompiled smp toolbox models directly into it's internal model format (uses the tmt-as-converter method)

I'm sorry if my english is confusing and for this load of data.

[MegumiKasuga]

Solutions

Thank you for your guidance. I found those required software source code packages at Fexcraft-Json and FCL-Lib.
Now I could build my MTB loader smoothly.

Invitations

I am trying to completely reconstruct the Traincraft to NeoForge-mc1.21.1. The first step is to read their model format, MTB. The project I'm currently working on is kasugaLibNext.
Our library is able to load these following model types below:

1. Minecraft Bedrock Models
2. Minecraft Java Models
3. BlockBench Models[WIP]
4. Wavefont OBJ Models
5. MikuMikuDance Models[WIP]
6. MTB Models[WIP]

And there are also some types we will be able to read in the future:

1. glTF Models
2. FBX Models

If you could join our project, it would be of tremendous help to our work, and I hope you'll consider it. If you're interested, please contact me. Thank you again for your help. Have a nice day!

[MegumiKasuga]

Definitions of 'Import'

Read the specificy type into minecraft Instance and render it in games.

Links to our model loader implementations

• MC-BE
• MC-JE
• Wavefont OBJ
• MikuMikuDance
• MTB

Features

Our library has already passed cirtical performance testing. Which I used a huge MMD model as the testing example(Over 150k triangles, over 430k vertices), running under IRIS environment with Complementary Shader-Reimagined. The game performs well (over 210 fps on average) with my Ryzen9 6900HX and RTX 3070ti Laptop(8G) (Maybe my device is still not so 'critical' in performance?). Our project implements a bunch of modern optimization features into our pipeline such as GPU Skinning. I hope that would be helpful for you.

[Fexcraft]

.mtb or .java?

I think there may be some misunderstanding towards what mtb is.
.mtb are save files from SMP Toolbox, they are in the TrainCraft repository so that others that may need to update the source model, can open it up in SMP Toolbox (or software that can import it, like FMT).

In Traincraft (and Flansmod) the .java models exported from SMP Toolbox have actually been used for rendering.
Packaging .mtb into a mod/resourcepack to load the model from it... is not the intended way of things to work, especially since they are actually a .zip file.

Traincraft also includes .java models from earlier times using a different format and .java models of the FVTM format (exported from FMT).

Because I stopped using .java models in FVTM, I provided the BEO model loader for Traincraft so that it can transition away from static java models, at least those in FVTM or MTB format.

If you find .fmtb files among the TC files, those are FMT save files. Similarly they are intended for work versions of the models to be used with FMT, not as production model for rendering.

Traincraft

I advise to take contact with the current Traincraft development team because of the license terms.
Last I recall the original author is against the usage of libraries for Traincraft (they want the mod to work standalone).
This is partway why I do not really help out there directly, instead in theoretical implementation talk and model loading (like my earlier mentioned pull request).

Some of the models, especially the newer ones with a .mtb or .fmtb file may have separate license terms.
It would be really unfortunate if you put a lot of work into this project but you could not release it - at least on places which for sure check if the license or original author allow it (e.g. CurseForge).

---

Regarding the invitation, I may take a look when I have more time.
Although I generally tend to aim to work with a model system that fits my needs, is version/application neutral, and is not necessarily based on the Minecraft Structure.