PoserFusion and Lightwave 2018
I've just upgraded from Lightwave 2015 to Lightwave 2018. Unfortunately the PoserFusion plugin is not working with Lightwave 2018.
Is there an update on the way or some work around so that I can still use Poser?
You are not the only one! I thought I saw a poser fusion for LW2018 already to go
Okay for now, this will work! But you will have to use LW2015 to prepare your animation.
I brought the poser scene file into LW2015
Then highlight each obj and click on property
go to add MDD Baker under deformation and save MDD and OBJ and LWO, then it will give you a choice of LW5 or LW6, I choose LW6!
Then open up LW2018 and import the LW file and then add MDD reader to your OBJ and load back in the MDD file. All the texture setting from poser will be perfect.
I haven't made the jup to LW 2018 just yet, but of curiosity have you tried importing Poser into DAZ first, then export that out to an FBX file? I seem to have better luck with that than exporting to FBX dierctly from Poser.
I tested the Fusion route from PoserPro 11.1 to LW 2015.3, and it sort of worked but with not as smoothly as before the Poser update.
With LW going pretty much all nodal and PBR, I imagine it'll be some before a number of apps are up to speed.
I sent in the bug report to NewTek and I will wait to see what they can do! Meanwhile I need to send one to the poser team.
@ma3rk So far my method is the best. No success with exporting FBX from Daz to LW2018, but it does work with LW2015, but not as well as it does with Poser fusion to LW2015 and then to LW2018.
It does take more time to get it ready this way, however the time save in rendering is worth it. LW2018 is blazing fast, even faster then LW2015. As for Daz to lightwave, I do have that Ryan Roy Daz3d to Lightwave plugin for Daz Genesis2 figure. I have not tried that out yet, which I cant until I can get LW2018 to import FBX correctly.
I was not able to make Ryan Roye "Daz3d 2 LW" plug in to work in LW2018, but I was able to export LW scene file from LW2015 with the Ryan's plugin to LW2015. I can make rigging adjustment in LW2018 with it and the setup from LW2015 is intact. The response time in LW2018 is much easier to animate then in LW2015.
I wasn't using any plug-in, just the native DAZ menu item to export to FBX. There are some vids on the option specifics in the panel that comes up, but pretty straight forward. There's another vid on what to adjust with a characters skeleton once in Layout, but again pretty easy.
But that's good to hear regarding render speed improvements; everyone seems to be reporting the same thing. I've had little minor issues since day 1 with 2015.x both Layout & Modeler & hope they've all been addressed. Haven't heard/seen a peep about that on the LW forums, just learning curve related so hope that's good news all around.
@ma3rk I understand, and it works in LW2015 just fine, but not in LW2018
I can import Daz FBX into LW2018 but not able to add the BVH file with Ryan plugins.
As for using poser file to Daz then to LW2018, it is much cleaner looking file and animation to do the route by way of using LW2015 with poser fusion and then save the scene file to be reopen in LW2018
Ah. OK. Good to know as a work around until it all gets sorted out.
I've never had any luck with BVH files for some reason. I'll take a relook once things settle in.
It seem to work for me. After installing the Fusion plugin into lightwave 2018 i then add PzrForlw2016. Everything but the path seems to work correctly
Ryan Roye discover that the FBX import was creating another bone deformation under the object property, and the work around is to remove the second bone.
Take a look at this:
I know this is for DAZ but as I mentioned, I've had much better luck bring Poser into DAZ first so the info still applies.
Think I found one of my problems. Lightwave had the PzrForLw10 plug installed rather than the PzrForLw2016 which I have but didn't get updated.
In LW 2015.3, if I try to import a Poser 2014 PZ3 file and use the PzrForLw2016.p plug, I initially get the usual mesh options message, but then get an error message that the scene needs need a newer version of Lightwave. If I switch back to the PzrForLw10.p version, it imports fine w/o errors.
Layout won't allow me to have both plugs installed at the same time.
If I try to import a Poser 11.1 pz3 file, it eventually requests the file Construct.obz which exists in \Poser 11 Content\Runtime\Geometries\Primitives\Construct.obz but I have to go looking for it.
But, then after browsing & selecting that, it then asks for areaLite.obj which can't be found anywhere on the system, so I click Cancel and it proceeds.
It then asks for Construct.pmd which I find in \Poser 11 Content\Runtime\Libraries\Props\Primitives\Construct.pmd and again have to go find it. I use a search tool though so can just copy & paste the path into LW requestor.
It then tells me again that I need a newer version of Lightwave.
Switching back to the PzrForLw10.p version, and try a Poser 11.1 pz3 file, "D:\Poser 11 Content" and loading EmotiOne.pz3, it again asks for the Construct.obz, areaLite.obj then Construct.pmd and make the same selection choices, but does open the scene.
I reinstall Poser fusion and remap the path to LW2018 and poser fusion works very nicely to Lightwave, with Vic4.2, however Genesis2 model had issues.
Where/when do you set that, or is that simply when you export out to Lightwave from the File menu? Been a long time since doing that so can't remember.
@ma3rk You import the poser files into load scene, but change the file type selected to all files, and you should now be able to see the poser file and click on it.
Other than that to enable it when you download using the SmithMicro DLM you would relocate Lightwave file to the LW2018 from LW2015 and the DLM will load it to your new LW program file. Then when you go into layout, add plugin in edit menu and you click on PZR for LW2015, and it should be able to find 3 plugins. Dont really need to add it to your menu. it just need to be enable and allow you to see a poser file in the load scene tab.
@ruscular OK. That's what I've did long ago but wanted to confirm I didn't miss something is all. Not going to worry about it for now.