kbdm257 opened this issue on Apr 05, 2023 ยท 8 posts
kbdm257 posted Thu, 13 April 2023 at 9:06 AM
I have the latest version of lightwave and it saves objects as .lwo files. I don't know the difference in the 2 file structures, i.e *.lwo and *.obj. I wanted to know how come Poser won't import a *.lwo file, but will import a Wavefront obj file. Lightwave 3D is the only other 3D program I use, aside from Poser. I use Poser for rendering. Superfly does a better and faster job than Lightwave Layout. Layout is too time consuming for me. With Poser I can set the camera, lights, objects and characters in the scene in mere minutes. Render it in about 5 minutes and get a photo-realistic image. I can tweak it Photoshop and have a great presentation.Are there different versions of LWO ??
Also, OBJ (+MTL) is un-rigged. Upside, as both are text files, paths etc may be hand-edited.
FBX may be rigged. It may even have 'relative' texture calls, rather than hard-coded into depths of author's G: drive's folder tree...
But, due to differences between 3rd Party / Open Source FBX plug-ins, eg for Blender, and the proprietary Adobe SDK, import results vary.
I half-joke about three types of outcome:
'Okay', either due Adobe SDK --'Rigged by Maya' ?-- or a temporary 'happy alignment' of eg Blender and plug-in sub-versions' quirks.
'So-So', anywhere between a few and many sub-rigs. Position / pose using first, parent others to this ASAP to off-load Poser hierarchy base...
'Splat', think Star-Trek Transporter Accident. Call janitor to mop mess, close and re-start Poser...