When the OBJ and MTL says there are perhaps 7 in the original !! I see what you mean as typically only 1 texture comes in - the first one ! They are so 'heavy' that one or two can kill you model - avoid shadows etc !! Over 53 million lines of code in the largest OBJ in that zip !!!
These are relatively large objects with complex texturing and take a while to load.
If an MTL file needs a subfolder for the texture image files' paths then if it doesn't exist you simply make a new folder to match, next to the OBJ file, and move the texture image files into it. You will find that Xfrog OBJ texture image files usually stay in the same folder with the OBJ, as there is not a subfolder specified by the MTL file. Open the MTL file in Notepad and read it. The texture image files need to be in the same relationship to the OBJ file, as set in the MTL file. I appreciate that this is the first version but if it is to be taken seriously I recommend that you address these issues with some urgency. It does not follow the associated MTL file's settings, and although it makes all of the required materials by name it does not assign RGBA values or textures to them - instead it makes all materials look the same with a 'checker' texture. It therefore needs manual rotation after import. It has no option to flip the object's YZ axes - many OBJ are made with these flipped. It therefore needs manual scaling after the import.
It makes no attempt to make the object the correct size - i.e.
I have tested yours against mine and I can now comment as follows. Thanks for this free compiled OBJ importer it is potentially a welcome advance on my own free OBJimporter Ruby script, that can be slow and not always successful.
0 kommentar(er)
