Perhaps one of you gurus could suggest a script or workflow suggestion for these scenarios?

If I create a scene in Poser Pro 11, is there a way to duplicate/match the camera settings in Daz Studio 4.x? In other words, same width, distance from camera, and so forth. I'm not looking for (or expecting) 100% fidelity between the scenes, but having them be close would be very nice.

And is it possible to do the inverse? Create a scene in Daz Studio and then move it over to Poser Pro 11 and transfer the general camera positions and view?

I've not done anything for the Poser to DS route, but I did experiment with a .duf/.dsf parser to import props into Poser without resorting to the DSON importer in any way. It shouldn't be too difficult to extract camera information from a DS scene, though I have not tried that at all. Let me have a look.

I would also suggest looking on the DAZ forums for help with the DS to Poser route, since I'm pretty sure that many things can be exported in Poser format from DS, but not all, and I don't use DS often enough to be confident guiding your quest.

My DSON parser currently tells me it's read a "preset_camera" asset, when I select a .duf camera preset, but doesn't know what to do with it, yet. I'll see about adding some appropriate assignment of node_library values to the currently selected camera. I can see all the necessary information in the file, so it shouldn't take too long...

an0malaus posted at 9:06AM Wed, 14 August 2019 - #4359344

My DSON parser currently tells me it's read a "preset_camera" asset, when I select a .duf camera preset, but doesn't know what to do with it, yet. I'll see about adding some appropriate assignment of node_library values to the currently selected camera. I can see all the necessary information in the file, so it shouldn't take too long...

WOW. You are simply amazing! And I'll follow your advice and ask over at the Daz forums for the DS to Poser route.

I have progress to report: DSON parser can now set the rotations, translations and scale parameters of a camera in the Poser scene which matches the name of a camera referred to by a .duf camera preset file. I haven't added the remaining camera parameters yet, as the script was initially designed for props only, then exploded in size when I decided to use it to convert poses for Genesis figures to match V4. I didn't ever get around to adding the perspective and other parameters for cameras, so there's a little bit left to do, but all of the parsing is sorted.

I abandoned the attempt to try and natively support Genesis figures in Poser without the DSON importer, since trying to convert different weight mapping and subdivision schemes was never going to be possible. I got to the stage where I could load, convert and apply .duf/.dsf props and figure poses to native Poser figures, though.

an0malaus posted at 7:56AM Thu, 15 August 2019 - #4359359

I have progress to report: DSON parser can now set the rotations, translations and scale parameters of a camera in the Poser scene which matches the name of a camera referred to by a .duf camera preset file. I haven't added the remaining camera parameters yet, as the script was initially designed for props only, then exploded in size when I decided to use it to convert poses for Genesis figures to match V4. I didn't ever get around to adding the perspective and other parameters for cameras, so there's a little bit left to do, but all of the parsing is sorted.

I abandoned the attempt to try and natively support Genesis figures in Poser without the DSON importer, since trying to convert different weight mapping and subdivision schemes was never going to be possible. I got to the stage where I could load, convert and apply .duf/.dsf props and figure poses to native Poser figures, though.

This is GREAT news. I'm excited to see what you can accomplish with this!

So, did you ever finish the Pose conversion? Or make it work with M4?

Having the ability move even Genesis poses over to V4/M4 would help expand my library. Lately, I've been feeling VERY left out of the current trends because of the inability to access all the new Genesis content in Poser. Even being able to get Genesis poses would be something of a help.

(And yes, I'm aware of the great script for working with G3 figures: I tried it and, frankly, it's a lot of trouble and the results are not always usable. Poses seem to be hit or miss, as are clothing conversions. Right now, it's too unpredictable and too much work to use as part of a serious workflow.)

I was certainly able to make the pose conversions, but, as with all such transfers, even Poser's much hyped universal poses cannot ever exactly replicate poses between figures with different limb/torso proportions. There are too many variables in how you want poses to transfer. Should the limb actors all have exactly the same rotations, or should the endpoints of the limbs be located in the same place relative to some other actor. Nothing will ever be perfect without human intervention to tweak poses to personal requirements.

That said, the goal of the script was to be able to make use of Mechasar's Slime Attack props and Genesis 3 poses on V4 in Poser, without using the DSON importer at all, or needing to export anything from Studio. That was achieved, although determining pose conversion factors was quite tedious.

The structures to allow other figure conversions are in place, but nothing except V4 as destination has been implemented. The script was also the starting point for trying to import Genesis figures natively into Poser, but that seems a dead end, unless much changes on the Poser side. Until then, I will probably try to remove the figure creation code from a copy of the script, and just leave the pose conversion/application part in place, as that will be simpler to maintain/support.

Might take a few days...

an0malaus posted at 4:31PM Sat, 17 August 2019 - #4359461

I was certainly able to make the pose conversions, but, as with all such transfers, even Poser's much hyped universal poses cannot ever exactly replicate poses between figures with different limb/torso proportions. There are too many variables in how you want poses to transfer. Should the limb actors all have exactly the same rotations, or should the endpoints of the limbs be located in the same place relative to some other actor. Nothing will ever be perfect without human intervention to tweak poses to personal requirements.

That said, the goal of the script was to be able to make use of Mechasar's Slime Attack props and Genesis 3 poses on V4 in Poser, without using the DSON importer at all, or needing to export anything from Studio. That was achieved, although determining pose conversion factors was quite tedious.

The structures to allow other figure conversions are in place, but nothing except V4 as destination has been implemented. The script was also the starting point for trying to import Genesis figures natively into Poser, but that seems a dead end, unless much changes on the Poser side. Until then, I will probably try to remove the figure creation code from a copy of the script, and just leave the pose conversion/application part in place, as that will be simpler to maintain/support.

Might take a few days... It's really unfortunate that it isn't easier to share figures, poses and resources from Daz to Poser. DS is a good program, but it doesn't have all of the features I want when it comes to creating line art illustrations. In that one category, it just isn't even a player.

Let me know how things go with the Camera transfer.

Thanks.

Will do.