Update - Pro version
- Added all features from update v2.7
- Unpacking Zlib data Video. Zlib is often used to compress models. Usually the beginning of such data is byte 0x78.

AMDFreak2006
Yes, the program does not take into account the position of the texture when saving the model. I will try to fix it in the new version.
Thanks for reporting the issue.

Please tell me how to do this calculation, this is an example: Float ------> Short_signed Vertices in float: X = 34 80 45 C2 ---- short_signed ----> xx xx Y = C1 F9 65 42 ---- short_signed ----> xx xx Z = 94 F6 76 41 ---- short_signed ----> xx xx It depends on the program that uses this data format...

To convert shor_signed to float, the program seems to divide the number by 256 or 0xffff.

Segal, learn the basics of Python and create this converter. The fact is that all models have a different format, and it is impossible to create a converter for all formats.

MadTucker
Write to me in the PM. The message may be in the spam folder.

micro777 wrote: ↑

Sun Mar 29, 2020 7:09 pm

Все верно.
Вот эти модели и не получается открыть. Пробовал через программу ModelResearcher, но с моим нулевыми познаниями у меня ничего не получилось.

А есть пример модели?

Such a problem. The skeleton is displayed correctly during animation. But the model is distorted - very elongated. What could be the problem? In the transformation matrices?

Big Update v2.7 - Added support Quads! - The output of data in text form has been changed: texture coordinate indices and normal indices are now displayed in separate blocks with the literals "fvt" and "fvn", 1 is not added to the indices. The old output can be enabled in the menu "View" -> "Print ...

I have a different result:

Sharppy
Can you send an example file from the screenshot and the program?

Sharppy This will seem strange, but I have not studied hundreds of files. I am not very good at researching and unpacking resources. Most 3D formats are very simple, so the data from them can be read using programs such as Hex2Obj. As for texture coordinates, I don’t know how this program reads dat...

Thanks, Aterbust!
I updated the program.

Most likely, the problem is in negative coordinates. If the coordinate is less than 0, then the program converts by subtracting the coordinate from 1.
--
if u < 0: u = 1 - abs(u)
Perhaps this is the wrong approach.

The program has been updated. Update v2.6 - Added support for normal vectors! - Template format is now compatible with the Pro version. - The algorithm for calculating normal vectors has been changed. Now the model looks better. - Added TStrip, TStripFF formats for texture coordinate indices and nor...