I did read that some people have problems with import of wavefront files. I reported a problem i found for about a year ago and as nothing happend I reported it again. I dont have the latest path so I don't know if it has been fixed by now but I would not be tha least suprised if it has not. It happens when there is a reference to a material file inside the .obj file. For some reason Vue gets nut if the material file starts on a certain letter( or letters as i have not tested the full character set. Anyone could search for my old posts on this if you want to know something more about witch letters i have tested but in short.. If you have the same problem either. Resave your model with another name starting with another letter that hopefully aren't creating the problem (usually this fixes it as the material file also is renamed). Search the .obj file for the tag mtllib and if it looks like this mtllib mymaterialfile.mtl then change it to mtllib ./mymaterialfile.mtl or change the name on your material file and change the mtllib to point at the new name. All problems i have had with object files has to do with this. In Wings3D I even have managed to get the developer to put in a checkbox that reads 'Vue Espit fix' that adds the "./" in the material file reference on export to wavefront format. It was more easy to have that done than to get the people at Vue to fix the problem. Hope this helps.

You should take this little message you got here and send it to E-On cause maybe they'll look at it in more detail. Could be the path problem I've seen that before in different applications. Good thing you figured it out though cause there has been lots of people reporting that problem here on the forum.

on a Mac it is not so simple. The problem is there with all obj-files. But e-on promised (i have an answer now) to come up with an update soon. But i found another thing that could cause the problem. If you use an extra character (german Umlaut for example) in either a file name or the path of the file, Vue is not able to open even 3ds-files (Mac version). If you rename the path and/or the file name it works. Hope e-on will fix that as well.

Ya wierd characters could kill it for sure. Remember only the english parts of the program have been translated, the underlying code has not so pathnames must still follow the english disk rules for naming and that character is a no no.

Well MightyPete I have sent that info to E-On two times without an answer. I understand if the don't want to dive into an email exchange every time but I don't think it's to much to at least let you know that they have recived the mail. The second time I posted it I did mention posting before but still no reply at all. Well chacters I only use the English chacterset when naming files. Even if some programs support other characters you newer knows when you have to move/use the file in some other app or system wabe Nice to know that they seems to be looking into this...

Thanks very much Hellborn!!!!! I was having problems with importing of OBJ files that I'd made with another program. These files would import into Poser, Truespace, and everything else I could think of, but not Vue. Your technical information is great - allowed me to fix my stuff.

Forester I'd say one reply is probibly enough. A lot of people get mail for every reply and your single reply generated 19 e-mails. That's called spamming the forum and it's a no no.

Sorry folks. This wasn't done intentionally, and it looked like only the one message was sent. MightyPete, I appreciate your email. I'm an IT professional, so I am aware of the bad effects of spamming. So, my apologies folks, it appears to have been a network stutter.