in order to import at the very least, a custom model we must follow what we know from turok 1 when it comes to most everything other then whats in the pipeline, creating and formatting the 3d models and groups in a model, how the .obj's usemtl param needs to line up with the .mtl's newmtl and the materials and how the params are declared by name will instate and present input for the name of the kmat materials file path. this is not working here.


convertobj can not reach a .kmat file
this all may just be a product of creating a testmodelA.objtestmodelB.mtl, or a mis-understanding becuse this is how it has had to of been done for wile now in turok 1. i noticed doing the same here allows for the scanning of the .obj to happen.... perhaps modelname.mtlmodelname.obj trick is a reflection of a core issue at hand, idk. question is how to get pass the issue


the "convertobj" command is unable to match the mtlib with the material path.

exsample:
inside testmodelA.obj:
usemtl materials/mat_testmodel/surf_01
inside testmodelA.mtl
newmtl materials/mat_testmodel/surf_01
map_Kd textures/turoktest_1/6a94e5e4.png
and inside materials/mat_modeltest.kmat:
material surftest_01

as you can tell i didnt include all the code from each file just what highlights the issue at hand.