It doesn't really become a Biped file. That's just Windows seeing a like extension and declaring it as such. It certainly will not work with Biped in any sense of the word. It's no different than .txt or .log file; each can be opened by any number of text editors, but only one will be "assigned" to the extension. If someone is trying to bring in a STEP file as a Biped file it will absolutely fail, if not crash Max, assuming that is what they are using.
However, if they use Max they should be able to import native Inventor files already.
Anyway, for them or anyone else here are a few tips:
- As a general principle, imports of complex assemblies is sometimes more art than science. I import .STP files all the time from customers and most come in relatively clean, some not so much; about 5% fail altogether for no obvious reason.
- Translation: The process happens all at once, meaning it can't bring in a section at a time and thus it also takes up a lot of RAM. So a .STP file over 200MB can take up to 10 minutes to import, even though a native Max over 600MB might only take 45 seconds.
- Use File/Import for the operation, not the Drag n Drop into the viewport method with the setting below for best results.

Doug Bowker
www.douglasbowker-motiongraphics.com