NFS-CarToolkit model export problem

[modding]

I have imported many NFS models with NFS-CarToolkit and everithing looks good, specialy all textures are there, but after exporting the model to fbx and reopening the fbx file all textures are mising. The same problem if I expot to z3d. Looks like obj export has the same problem. So is there a vay to export the model with worcking textures?

[Aftrmrket Exotics]

I have imported many NFS models with NFS-CarToolkit and everithing looks good, specialy all textures are there, but after exporting the model to fbx and reopening the fbx file all textures are mising. The same problem if I expot to z3d. Looks like obj export has the same problem. So is there a vay to export the model with worcking textures?

The texture exporting is done separately. But it can still be done nonetheless.

On the top left corner go to Textures > Export All. You will be prompted to select a folder to store the textures in, so create a separate folder for the textures but make sure both the texture folder and the model are under the same folder. After that, depending on the game, you may have to modify some texture formats to make them work (such as Most Wanted where only DXT1 and DXT3 formats work)

[modding]

I know, this is how I do it:

Import the model


The folder with exported model and textures


Import the model back from that folder


As you see all textures mising.

[UndercoverBoy833]

that's because it was in OBJ format and textures are not compiled as well. It's normal to have textures missing

[modding]

No, it´s fbx. I also tried z3d and when importing to ZModeler exact the same problem with textures. The advantage of ZModeler is that it gives errormesages and it looks like the developer of the too not knowing diference between material and textures.

[AJ_Lethal]

Toolkit only loads textures to BIN file models because the path for textures in BIN files is static (it's always in the same location as the GEOMETRY.BIN file). Other formats don't abide to that because

a) CarToolkit only loads (and exports) mesh and basic material data from fbx/obj/z3d
b) you load the geometry file first then load the textures separately; hence cartoolkit cannot tell what textures should load and apply to the mesh

CarToolkit is not meant to be a fbx/obj/z3d viewer; it's purpose is to convert from and to Black Box BIN file mesh formats.

[modding]

Toolkit only loads textures to BIN file models because the path for textures in BIN files is static (it's always in the same location as the GEOMETRY.BIN file). Other formats don't abide to that because

a) CarToolkit only loads (and exports) mesh and basic material data from fbx/obj/z3d
b) you load the geometry file first then load the textures separately; hence cartoolkit cannot tell what textures should load and apply to the mesh

CarToolkit is not meant to be a fbx/obj/z3d viewer; it's purpose is to convert from and to Black Box BIN file mesh formats.

But CarToolkit aplies right textures when I load the model from bin file. So why the f*** the exported model has no textures? In ZModeler or 3 ds Max the model has also no textures, wich makes the model useles.

[WiLL]

Yes that to bad... As I read.
Just like my Deleted Compliment was , an is 🙄🙄. 😋😋 Remembered..

[AJ_Lethal]

Toolkit only loads textures to BIN file models because the path for textures in BIN files is static (it's always in the same location as the GEOMETRY.BIN file). Other formats don't abide to that because

a) CarToolkit only loads (and exports) mesh and basic material data from fbx/obj/z3d
b) you load the geometry file first then load the textures separately; hence cartoolkit cannot tell what textures should load and apply to the mesh

CarToolkit is not meant to be a fbx/obj/z3d viewer; it's purpose is to convert from and to Black Box BIN file mesh formats.

But CarToolkit aplies right textures when I load the model from bin file.

I already told you why CarToolkit doesn't load textures from fbx/obj/z3d files: it simply does not handle that data directly because texture data on those files have no fixed location at all. All it can do is to assign the material/texture data (which is defined in the .txt file you load) on compilation; you'll see that if you compile a z3d/obj/fbx to a geometry.bin, then compile a textures.bin file and open said geometry.bin file.

So why the f*** the exported model has no textures? In ZModeler or 3 ds Max the model has also no textures, wich makes the model useles.

You have to export the textures separately, then load them manually for each material in the 3D editor.

[modding]

You have to export the textures separately, then load them manually for each material in the 3D editor.

I have exported the textures separatly. Why the f*** should I do all texture stuf manually? I mean it should not be so hard to export the models to fbx/obj/z3d files with corect texture names. I mean should I gues which texture belongs to which material?
Also wanted to make 1 thing clear, never said that CarToolkit should be a viewer for fbx/obj/z3d files.

[AJ_Lethal]

I have exported the textures separatly. Why the f*** should I do all texture stuf manually? I mean it should not be so hard to export the models to fbx/obj/z3d files with corect texture names.

Because the textures a) can be anywhere and the program can't magically guess where you're exporting the textures to embed the path data in order to load them automatically b) at least in z3d export case you'll have to convert the textures to bmp/tga since it handles the ZModeler 1 format (which doesn't have DDS support)

I mean should I gues which texture belongs to which material?

Not really, BIN meshes exported with cartookit have the texture name appended to the materials they use so you can know what texture originally came with it (so for example a part with a RUBBER material and TIRE texture will be exported with a material named RUBBER_TIRE)

[modding]

I have exported the textures separatly. Why the f*** should I do all texture stuf manually? I mean it should not be so hard to export the models to fbx/obj/z3d files with corect texture names.

Because the textures a) can be anywhere and the program can't magically guess where you're exporting the textures to embed the path data in order to load them automatically b) at least in z3d export case you'll have to convert the textures to bmp/tga since it handles the ZModeler 1 format (which doesn't have DDS support)

I mean should I gues which texture belongs to which material?

Not really, BIN meshes exported with cartookit have the texture name appended to the materials they use so you can know what texture originally came with it (so for example a part with a RUBBER material and TIRE texture will be exported with a material named RUBBER_TIRE)

The textures should be in the same folder as the model. I am using ZModeler 2 so no problems with dds format.
To show again what I mean here the example avaible with the tool:





As you can see no material or texture name coresponds to the real textures avaible in the folder.

[AJ_Lethal]

The textures should be in the same folder as the model. I am using ZModeler 2 so no problems with dds format.
To show again what I mean here the example avaible with the tool:





As you can see no material or texture name coresponds to the real textures avaible in the folder.

Some textures (like CARBOTTOM) are what are known as global/generic textures; which are found in places like GLOBAL\GLOBALB.LZC or CARS\TEXTURES.BIN. You have to manually extract those to use them in your 3D editor.

Some other textures like CARSKIN or BRAKELIGHT_RIGHT, for example, aren't textures per se but "slots" of sorts for dynamically changing textures (such as body paint or brakelights, respectively). You still might have to load a placeholder texture for those in your 3D editor for stuff like UV mapping.

[modding]

Some textures (like CARBOTTOM) are what are known as global/generic textures; which are found in places like GLOBAL\GLOBALB.LZC or CARS\TEXTURES.BIN. You have to manually extract those to use them in your 3D editor.

Some other textures like CARSKIN or BRAKELIGHT_RIGHT, for example, aren't textures per se but "slots" of sorts for dynamically changing textures (such as body paint or brakelights, respectively). You still might have to load a placeholder texture for those in your 3D editor for stuff like UV mapping.

I see your point, but at least texture names from textures.bin which were corectly imported could also be exported corectly.

So nobody know how to fix that texture bug? Unfortunately the tool contain no reedmee file, which contains a way to contact the developer.

[AJ_Lethal]

So nobody know how to fix that texture bug? Unfortunately the tool contain no reedmee file, which contains a way to contact the developer.

It's not a bug; it's a missing feature at worst.

Here's the author's website, try leaving a message in the replies or sth: https://nfs-tools.blogspot.com/