I've had similar problems with freeware .OBJ files under windows in the past - odd/unexpected combinations of r and n or just one of either. It's a pain in the extreme as it means it's harder to write reliable .OBJ file readers/importers etc. etc. to cope with these variations (assuming one takes the extra effort to do so). My only halfway-helpful suggestion is that someone needs to write a byte-level "filter" or "converter" program for the Mac, if one doesn't exist already, that looks at ALL possible variations of "start a new line now" in the file it is reading and writes out the platform-specific "new line now" sequence in the file it writes. These kinds of programs are generally not hard to write, but annoying :( It's this kind of effort that Jaqui's suggested DOS to *nix converter would have put in :)