Exporting obj file bug?

#1

It seems that when exporting from lwo to obj, modo drops the native lwo file and replaces it with the exported obj file in the mesh list. This means that any work done in the same session is saved to the exported file rather than the original lwo file. That isn’t so bad, except that for me, in quite a number of cases now, modo crashes when it tries to open the obj file in another session. Of course, after exporting, I could quit the obj file in the mesh list and then reopen the original lwo file, but wouldn’t it be much quicker and easier for modo to simply stay with lwo file?
Thanks,
Graeme

#2

modo doesnt have a native file format…really…

If its saving as an obj…then just change the file extension to .obj in the save window…

#3

I agree, when exporting, modo should keep the existing .lwo file, not the file you exported to.
Say for example, I subdivide, freeze and export as obj, then I’m left with that file after exporting. If I wanted to make a couple of different [subdivided] versions for export, that means I have to re-open the original .lwo file before exporting again.

Bert

#4

i think that its just a pipeline thing…lwo isnt supported by all appz…so it keeps the origional file format that was imported…its really no biggy

#5

Sorry, I should have said “default file format”. My bad! .lwo is of course Lightwave’s native format.

Any one else had problems opening modo created .obj files in modo?

Thanks,
Graeme

#6

Unfortunatly i dont have any problems…allthough i did with silo exported objs

#7

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.