2010-10-18, 05:53 AM
Your untextured.x file works for me, as does Todd's book.x file. You're probably doing something wrong or think you're seeing an error that isn't there.
You'll need to describe what you're seeing either way. Again if necessary. It's possible (though very unlikely) there is some dependency which is not installed on your computer. If so we need to know about that. Any message box which mentions a file is very important. And if you can click on "details" and get to the dump of the error message / post that, that would be helpful.
I will ask Todd to give it a try. He generally is better at that sort of thing / helps iron things out / encourages others to not give up. If nothing else I recommend trying different things to see what works, the same way you would with From's x2mdo app (which also requires some know-how) instead of just giving up.
Again we have to communicate better as a community if we want results.
PS: I don't think I ever intentionally addressed what would happen where a input includes external image files which are not there. I just tested that and it does produce a bad .mdl file... I will look into that asap, however in the meantime, if your file/textures load into the viewer app, things should work with x2mdl.
UPDATE: I've not yet uploaded a new release/download, but I've added some code to keep the file from being flushed (written) whenever there is an abnormal exit status (something I didn't think about when slipping in all the error points) and improved the message for missing texture files. I think a missing texture is going to remain an abort condition because it's not really appropriate to make that material untextured because Som's texture coordinates depend upon the dimensions of the texture. So not only would you be tossing out the texture, but the texture coordinates would not be appropriate either.
If you're seeing a real generic popup box and all error though this probably won't help you. You might want to make sure you're using the new download, and not an old one you had on your computer. The new download might be named something like x2mdl_2 or something if you downloaded to a folder with an x2mdl exe already in it. Also if you're typing things into a command prompt, sometimes (bugger all) Windows will use an older exe / dll file it has cached in memory, even when you overwrite the files.
You'll need to describe what you're seeing either way. Again if necessary. It's possible (though very unlikely) there is some dependency which is not installed on your computer. If so we need to know about that. Any message box which mentions a file is very important. And if you can click on "details" and get to the dump of the error message / post that, that would be helpful.
I will ask Todd to give it a try. He generally is better at that sort of thing / helps iron things out / encourages others to not give up. If nothing else I recommend trying different things to see what works, the same way you would with From's x2mdo app (which also requires some know-how) instead of just giving up.
Again we have to communicate better as a community if we want results.
PS: I don't think I ever intentionally addressed what would happen where a input includes external image files which are not there. I just tested that and it does produce a bad .mdl file... I will look into that asap, however in the meantime, if your file/textures load into the viewer app, things should work with x2mdl.
UPDATE: I've not yet uploaded a new release/download, but I've added some code to keep the file from being flushed (written) whenever there is an abnormal exit status (something I didn't think about when slipping in all the error points) and improved the message for missing texture files. I think a missing texture is going to remain an abort condition because it's not really appropriate to make that material untextured because Som's texture coordinates depend upon the dimensions of the texture. So not only would you be tossing out the texture, but the texture coordinates would not be appropriate either.
If you're seeing a real generic popup box and all error though this probably won't help you. You might want to make sure you're using the new download, and not an old one you had on your computer. The new download might be named something like x2mdl_2 or something if you downloaded to a folder with an x2mdl exe already in it. Also if you're typing things into a command prompt, sometimes (bugger all) Windows will use an older exe / dll file it has cached in memory, even when you overwrite the files.