I have been tinkering with G2F import into Poser for some months (PP2104 with SR5.2 and latest DSON), and I find one oddity is things which work when first applied, but if you SAVE the scene into a PZZ, then reload, the morphs just don't function anymore. A simple example is Belle 6, who (after reload) is just a scaled G2F - none of her morphs function. The dials are still there; still set to 1.0 (or as expected), but the dials have no impact. The DAZ 3D "G2F Body Morphs" also stop working on a reloaded figure.

But I have an odder example - below is a hybrid Aiko6 and Callie 6, but on the left is the gal AFTER a reload, and to the right is a fresh built G2F with SOME of the same morphs and the exact same pose (this is i13's Playful Callie6 #23 pose). Notice anytime odd about the arms on the left? The left/right collar settings were left as zero during reload - worse, they remain zero even if I reapply the i13 pose file. I can set them manually, and they work fine & remain set for the duration of my Poser session. But applying a different pose will not effect (nor reset) the 'rCollar' or 'lCollar' value - it is as if they no longer exist in the figure tree.

I rather suspect that they do exist (as I can find them manually), but somehow the DSON addin for Poser is finding the wrong item to apply the values to. For example, if we look into the DUF file, the item is just called 'rCollar'. While I'd not expect a G2F figure to have many collar objects, the PZ DUF file just applies things to an 'aiko6' (or 'aiko%206') dial, and I know there may be a dozen or more with that name! How does DSON find the correct one? This would also explain the Belle 6 total failure - if somehow during reload her entire 'tree' of objects is moved/renamed in such a way the DUF files don't find the objects anymore.
{

    "url" : "name://@selection/rCollar:?rotation/x/value",

    "keys" : [ [ 0, 5.35 ] ]

},

Any comments? Anyone else see this? Or is my install somehow non-standard? Note that so far, I have ONLY noticed the rCollar/lCollar issue with an Aiko 6 reload - there may be other objects affected, but they are not as obvious.

Actually - I just had a thought. I wonder if some other content installed a 'shoulder fix', which might be confusing the DSON task search algorithm? In my early days of DAZ and G2F I installed everything I found ... assuming like V4/A4 in Poser, that a new 'pose' had no impact unless applied.

Yet DSON builds a CR2/PMD (it seems) with EVERYTHING in the /data directory, so in effect every fix/change gets padded into the scene, even if the dial is 0.0 always. Given the vague names in the DUF, this could lead to name-space issues (something I am familiar with in Python, where HOW you import a modules means the same code be in RAM multiple times as different namespaces).

I have not been able to duplicate the dials not working or the shoulders not working.

Here are the steps I tried.

1. Loaded G2F.
2. Set the Belle 6 morph to 1
3. Saved the scene as a PZ3.
4. Closed Poser.
5. Opened Poser and the saved file.
6. Tested the Belle 6, Kieko 6, Girl 6, Aiko 6, and Aiko 5 morphs. They all worked just. The heads morphed to a proper shape.

I repeated the test with file compression and PMD saving and everything worked. I am I missing a step?

For the shoulder issue,

1. I loaded a G2F applied the i13's Playful Callie6 #23 pose and saved.
2. Then I closed and reopened Poser.
3. Loaded the saved file.
4. Added a new G2F to the scene and applied the i13's Playful Callie6 #23 pose to it.

I noticed the arms did look like your image. But, the saved figure was at a X-Trans of -1 and the new figure was at a X-Trans of 1. When I set the X-Trans of both to 0, the arms were identical. So I am not able to duplicate that issue as well.

DSON Importer does have a cache location. You can see where it is in the Poser menu: Scripts->DSON Support->Import Preferences...

You could try emptying it's cache, but I don't know how it will effect your saved files.

DSON sucks

That is not a helpful opinion and is very unnecessary.  The OP is looking for a solution, not a debate.

DSON Importer does have a cache location. You can see where it is in the Poser menu: Scripts->DSON Support->Import Preferences... You could try emptying it's cache, but I don't know how it will effect your saved files.

Thanks for a second test & opinion - gives me a reason to struggle on. I did have the 'runtine' set wrong at first, as I assumed DSON meant where is the Poser runtime, not the DAZ G2F runtime - that caused LOTS of trouble.  While I tried to clean up any old work files, I did not do a big search & destroy.
I'm not worried about 'saved' files ... as they don't really work well. So I'd much rather delete ALL old work as well as the cache - if it make life go better going forward :)

DSON sucks

Actually, if you figure out what DSON is good at, and what it is not good at ... that bypasses whatever reason you say it sucks. The right tool for the right job. For example, adding a Poser-based V4 jewelry prop to a DSON-based A6/V6 as a typical parented prop works pretty darn good - some simple XYZ adjust, maybe some scaling and it looks perfect - however trying to use DSON to add a G2F jewelry item to a V4/A4 (in Poser) is a disaster! There seems to be no way to 'parent' the DSON object to a non-DSON object in a way which allows it to follow bends properly (like earrings on an ear as the head moves).

Also, an Aiko6 in DSON must be worked with differently than a Aiko4 - that kept me away from DSON for over a year - for example, I am used to finding face & mouth pose control in the head ... yet DSON puts it in the body under 'pose control' under head, mouth, or expressions. That was unexpected, so I thought "how crazy - no face controls?" until I understood the new paradigm.

I am too old for paradigm shifts that threaten the fifteen years of Poser on my Runtime.

For those who haven't experienced Poser 5 won't know what sucking really means. DSON actually sucks way less.

That's G2F with some V4 props, V4 Dynamic Cloth, and V4 Hair.  Only the skin shader and the shoes are G2F's
I really don't think DSON sucked that bad.

Poser 5. :shudders: Well, it did get me started in 3D, that's maybe the best I can say about that version. Nice render, I only wish my DSON sucked like that. ;-)  

I started with Poser 3 well more than 15 years ago. I have seen a lot of new things come and go. I not the biggest fan of new. Whenever something new comes up (ie dynamic clothing, indirect lighting, ambient occlusion, and ton of others), I test to see if it will work for what I want. I size it up on it's own merits. Some are good and some are not so good. I fail often but I learn and go on. I feel I have become a better artist by trying new things. At the end of the day, that's all we can do.

I have only one primary runtime, that's probably why I was not able to reproduce the issues. Before Poser 8, I would copy my old runtime into the new one. Now, I just point Poser at the old Poser 8 runtime and keep filling that one. I install all my DAZ Studio/DSON to that runtime as well. That probably explains why my runtime is over 490GBs.

I hope clearing the cache and setting the runtime helps.

It works fine for smaller scenes

With large multiple figure scenes it gets slow and will eventually completely lock the UI and force you to kill Poser and lose your work

Yeah, I seem to be able to get one G2 in fine. It's when I add another or start putting on a full outfit that things slow down. With original Genesis it's even worse and I spend more time poking at the darn thing just to get it working than actually putting a scene together and setting up for a render. In the time it takes me to load, dress and pose that lone Genesis, I could have three or four pimped-to-the-max M4s and V4s, not to mention sets and props, in my scene. And as for lighting Genesis ...

Let's just say I suck even worse at that than I do regular Poser lighting. :-(

DSON is definitely SLOWER - dial spinning stutters and i find myself often manually tweaking the digits, or ticking the up/down on each side of the dial. I've only been working at this since Poser 7, but I remember when most renders took 20 to 30 minutes on an old AMD X - now I have an AMD octo-core with 16GB and Win8.1 with PPro2014 maximizes all cores & the full RAM. test renders (without IDL or SSS) take seconds.

For fun, below is a quick DSON in PP2014 image with 3 G2F Callie - and the CPU fan (normally off) ran a steady hum as long as the scene was open.

I might just delete my DS and 'My DAZ' library and start over, as I have discovered that any & all People you install consume about 1/4 MB of space in the Pz3. So for example, I installed Ninive 6, but didn't really like her form ... but now forever, every Poser scene I creates includes a 1/4 MB of valueParam, tagetGeom, and deltaAddDelta for her - add in V6, A6, Belle 6, Girl 6 and that means several MB of flotsam in each & every PZ3 file (DAZ might want to reconsider that design). If I start over, I can stop installing stuff I have but don't plan to use.

I wrapped a little story around it: http://www.renderosity.com/mod/gallery/index.php?image_id=2625142

How is your library window configured?  If you have it undocked as per General Preferences, DSON response improves.

Mine is undocked. I just upgraded to Daz 4.8 and installed the latest plugins. Haven't tried anything in Poser yet but just a single naked G2Male practically out of the box takes around three minutes to render in DS 4.8 with this new iRay thingy. Same scene in 3Delight is under a minute. iRay looks better but no way am I buying a new video card just for that when I prefer to use Poser and iRay of course does not work with Poser. Not to mention learning a whole new render system and buying new stuff properly set up for iRay. 

:sigh: This is getting to be a very expensive hobby. Er, more expensive than usual, I mean. And with more products being Daz Studio only -- no Poser Companion Files added or a way to make it work in Poser even with additional tinkering -- I'm finding it less and less appealing. Every time there's a new release I keep hoping it's something I can use. But the odds are almost always against me. Maybe I ought to just call it a day. :-(

Byrdie

Rendering with equivalent lights produces, on average, equal render times between Iray and 3Delight on CPU only renders. What you are looking at and comparing, though, is not equivalent lighting.Unfortunately Iray, for comparison purposes, does not have a disable Global Illumination setting. LOL. 

Want to get really silly? Load Uber Environment2 with an HDRI on it and with the 4x setting and with bounce turned on. Load Olympia HD, Lillith HD or similar. Render. 

Same lighting in Iray is accomplished by loading the HDRI in the Render Settings under Environment. Load Olympia HD Lillith HD, or similar, set the Render Sub-D to 3 under parameters and apply the Iray preset. Render. 

The two images, when the render is done, should be pretty close, the lighting is as close as 3Delight can get. What is the render time difference? 

Not too familiar with this UberEnvironment. Managed to find it and load an HDRI and SebastianHD -- do not have many HD figures either. No hair or clothes and he's not even posed. Also no bits added. Now how do I do this Bounce thingy and where's the 4x setting?

You can tell I'm pretty clueless about a lot of this stuff. Not into the Ultra Realism craze or whatever it's called. If I wanted my art to look like photography all the time I'd be using a camera and shooting live models. But I guess it'd be good to know about for the odd time I might want highly realistic renders.

The quality settings, including the 4x option, are presets in the Light Presets>OmniFreaker>uber Environment 2 folder (approximately, DS is rendering so I can't check). The bounce mode is a parameter setting for mode - it will currently say Occlusion with Directional Shadows.

Thanks. I think I may have set the thing up wrong. I'll try it again tomorrow, right now I'm working on my next AU adventure of Sherlock Holmes. He's having a fashion crisis and won't let me play with any of those other "boring" programs until I help him solve it. 

I have managed to import the Genesis MFD using DSON without any issues so far. Will see how many I can load into this scene to use as draped props (I grabbed the Make A Mess addition for it while they had a build your own flash sale) before Poser goes tits up on me again like it usually does when faced with too much Genesis.

Well, I have started a NEW DSON runtime, so instead of trying to share DAZ 4.8 library with Poser, I have begun a new runtime, where I delete the "people" (etc). So far, the result is great. An A6 saved with some G2F body morphs applied reloads exactly as expected.

So instead of deleting the old DS 4.8 library, I am starting a new /poser/gen2 runtime with only the data & runtime directories. So far, it is working well.

Never thought of that. But won't having two data directories confuse Studio if you're keeping it? I want to keep mine for the conversions and making my own Poser Companion files when stuff I buy comes without. Will try it if that's not going to be a problem.

So far, I got 3 MFDs for Genesis -- without the Genesis -- into Poser. The scene loads about the same speed as before except for a bit of weirdness whereby DSON decides to take M4's clothes off and put it back on while arranging Dress #2 where I have put it on a chair. That's the original M4 and non-weight mapped clothing I'm talking about, there is no Genesis figure at all in the scene. Everything is Poser except the Morphing Fantasy Dress which I'm using as a prop. So what the heck is the DSON importer doing that it needs to make a non-Genesis figure naked before folding a dress on a chair?! 

Oh, and it didn't do that until I loaded in a third fantasy dress. Which is also not on or even parented to M4. 

My DS library is in the default location, on a different drive to my Poser runtimes. If I can be bothered importing a figure using DSON I save it to a different (Genesis) runtime for Poser. Seems to work fine.

You can also create Poser CF files inside Studio for any content that doesn't come with one. At least in theory you can... I've seen how to do it, but haven't had a need to try it yet.

My Poser runtimes are on the same drive as Daz Studio. They each know where to find the other's content, however. Most times. Supposedly it is easier if one is only setting up to use the Genesis Content in Poser without Studio. But I want to use my older V4, M4 and Genesis Original things on the new Genesis 2 figures and for that I need Studio to convert them. Otherwise, I don't think I'd use it much at all now it's going iRay and I don't have the sort of rig to handle that. Not to mention the big learning curve involved, Daz Studio drives me round the bend as it is just trying to figure out the standard 3Delight settings and shaders, let alone the extra hassle of iRay.

I finally took the jump ... learned DS4.8 and installed DSON in Poser. I'm enjoying both ... noting some things work better in one venue than the other.but It all balances out ..it's fun to expand my toolbox. 

Boni

Yeah, I keep adding tools, the more the merrier. But some things I sit on the fence about, like Genesis & DSON. Just when I think I got it figured, along comes something else to throw me for a loop. Wish I could make up my mind once and for all with it, this much fence sitting's gonna give me splinters. 

My problem is that the bulk of my poser runtime doesn't have the DS mats (or support). Even if DAZ supplied the Meta-data, I didn't install.

I do love the way the DSON and G2F gals fit their clothing. Add a pose, and the clothing adjusts. Does A4 do that? No. With A4 I'm forever tweaking hips or thighs or boobs ... or even doing post-work to paint over the exposed flesh. Yah, in Poser there are cloth room & magnet tools, but the postwork in Gimp is far faster.

My problem is that the bulk of my poser runtime doesn't have the DS mats (or support). Even if DAZ supplied the Meta-data, I didn't install.

I do love the way the DSON and G2F gals fit their clothing. Add a pose, and the clothing adjusts. Does A4 do that? No. With A4 I'm forever tweaking hips or thighs or boobs ... or even doing post-work to paint over the exposed flesh. Yah, in Poser there are cloth room & magnet tools, but the postwork in Gimp is far faster.

I have you tried Poser Copy morphs? A4 is a morph for Victoria 4. I use the Copy Morph for Aiko4, Girl4 and the She Freak body morphs.

In PoserPro 2014 there is the Fitting Room -- which I have yet to figure out -- and the ability to copy morphs from a figure into clothing. Even custom morphs, which for me alone was worth the price of an upgrade. But there are still oddities now and then, especially when I want to use a piece of female clothing on a male and vice versa. That works best with Genesis and autofit, which (in addition to all the really cool aliens & fantasy characters) is the main reason I'm determined to not give up on the thing.

I have you tried Poser Copy morphs? A4 is a morph for Victoria 4. I use the Copy Morph for Aiko4, Girl4 and the She Freak body morphs.

Yup - use it all the time! Best thing since sliced bread, as it allows an A4 to wear (most) V4-only items. But that doesn't solve the flexing hips or thigh problem. The clothing doesn't follow the pose as accurately as G2F. (I did try the fitting room a few times back in PP2012, but it was generally more work that just the post-work: first render, allow poke-thru, second partial render with A4 invisible, to get the clothing item complete. I'm sure they spent a lot of time on the fitting room, but still, what is fastest? Most predictable?

I think you still have to magnetize Vicky 4 clothes when you put it on Aiko for better fit when you pose her. That's one of the things I often forget, makes a fair bit of difference when I remember.

DSON works okay with one figure, two maybe. More might be a big problem. Also too many vendors put DSON file data in the wrong places so Poser will do the "looking for file and not tell you until after 4 to 5 minutes" followed by "do you still want to look for this missing file" or even better "point Poser to the location of the missing file" which vendor don't say in readmes "file may be in wrong place". I got an outfit here that has that problem. Had much more help from the forum members than the vendor who only (after many attempts to contact them) contacted me after I left them one star for not supporting their product. Big thank you to the forum members here. A lot of people complain about toxic responses on the forums here, but there are a lot of good people actually help you super quick.

I've managed to get 4 G2F figures into Poser only by working on them individually and loading them already posed and clothed.  It took quite a dance of hiding the other figures or working in wireframe mode to get them positioned.  Posing using dials is very frustrating as others have mentioned.

I've managed to get 4 G2F figures into Poser only by working on them individually and loading them already posed and clothed.  It took quite a dance of hiding the other figures or working in wireframe mode to get them positioned.  Posing using dials is very frustrating as others have mentioned.

That's really impressive. Usually I have some G2 clothing or prop error crash my scene past two figures. If I use less G2 props and clothes it's better. Lots of saving the scene as I do anything.

DSON works okay with one figure, two maybe. More might be a big problem. Also too many vendors put DSON file data in the wrong places so Poser will do the "looking for file and not tell you until after 4 to 5 minutes" followed by "do you still want to look for this missing file" or even better "point Poser to the location of the missing file" which vendor don't say in readmes "file may be in wrong place". I got an outfit here that has that problem. Had much more help from the forum members than the vendor who only (after many attempts to contact them) contacted me after I left them one star for not supporting their product. Big thank you to the forum members here. A lot of people complain about toxic responses on the forums here, but there are a lot of good people actually help you super quick.

I don't think most of the vendors making content for DS actually understand how the Poser file structure hierarchy actually works.  While working on my tutorials for converting DSON files into Poser-native formats, this has been shown repeatedly.  I suspect it is due to DAZ's historical unwillingness to support any feature beyond Poser 4.
When they make PCFs, for the most part they just stuff everything into the Pose subfolder.  I have found literally every Poser file type in there - camera files, light files, pose files, material files, hand pose files, etc.

I've been poking around with Studio 4.8 over the last few weeks and I've noticed that in the 'My Library' folder I can rearrange the contents of the 'people' folder to make more sense (for one, not having to remember which vendor made what for whom). I suspect DAZ is trying to get around this with the readable metadata (smart content) so the auto-install feature is actually useful.

When accessing the 'My Library' file as a runtime in Poser the character lists are good... just as I set up. The other folders are not. I have been unwilling to rearrange the CF files because I understood that DSON was linked to a python script that kept everything connected. Is that not true?

BTW, I've had the devil's own time trying to import hair. Figures are fine, hair not.

I also have to say that some of the G2 products are no better textured than the old generation 3 stuff. Lots of effort in the figure with little comparable change in the clothing.

A bit sad, really.

There shouldn't be any issues with rearranging the Poser CFs as they contain no path information.  The actual cr2s and .objs for figures are in the Auto-adapted folder, whose location can be seen in the Importer Preferences.

Poser CFs for materials are just .mc6 files....

OK, I might poke harder ;-)

I've been poking around with Studio 4.8 over the last few weeks and I've noticed that in the 'My Library' folder I can rearrange the contents of the 'people' folder to make more sense (for one, not having to remember which vendor made what for whom). I suspect DAZ is trying to get around this with the readable metadata (smart content) so the auto-install feature is actually useful.

When accessing the 'My Library' file as a runtime in Poser the character lists are good... just as I set up. The other folders are not. I have been unwilling to rearrange the CF files because I understood that DSON was linked to a python script that kept everything connected. Is that not true?

BTW, I've had the devil's own time trying to import hair. Figures are fine, hair not.

I also have to say that some of the G2 products are no better textured than the old generation 3 stuff. Lots of effort in the figure with little comparable change in the clothing.

A bit sad, really.

Actually, you can rearrange almost everything.  There are vendors that stuff all of their DS files into 1 folder & DS doesn't care. That python script is universal.  The way the CFs work is as follows:

The fake Poser files calls the python file (this 2 line .py file is the same for every CF) which then calls the DSON subsystem which then fires up the .duf file.

This is why DSON performance is so piss-poor in Poser.  And is why you want to convert everything from DSON to Poser native files.  It isn't difficult, it is however, quite tedious.  I am currently working on a set of tutorials on how to get your DS4.5+ content out of DS formats & into Poser native files.  It is slow going, but I am getting there.

I haven't had any major issues with the Poser DSON importer.  I've even been fortunate to either export props out of DAZ Studio as scenes (CR2) then import into Poser, or clothes that don't come with Poser Companion Files.  However, I find Ralf Sesseler's DSON Loader Python script does a much better job than DS.

Since these are the only options for Poser users to import Genesis models, I can't complain.  I don't really care about Victoria 7 anyway.  I just started using Genesis about a month ago and will grab everything I can until the G2 models run out of clothes because it seems they probably won't be supported much longer.

I just tried D3D's DSON script... OMG!!! it is SOOOO much better than the DS rubbish! Genius!

I just tried D3D's DSON script... OMG!!! it is SOOOO much better than the DS rubbish! Genius!

hnmmm... tried using that too. still get get Poser looking for an non existent .pmd file. extremely annoyin. my opninion daz  just threw that dson importer together satisfy psoer users. but they really want us to move into daz studio. won't say anything more though :P

There is a reason why I stick with M4 and V4 content and refuse to buy anything Genesis, and that's because they don't need a DSON importer that never works. Program files is where Poser keeps it's runtime directories, so either way it doesn't work.

whbos posted at 12:34AM Fri, 25 November 2016 - #4210288

I haven't had any major issues with the Poser DSON importer.  I've even been fortunate to either export props out of DAZ Studio as scenes (CR2) then import into Poser, or clothes that don't come with Poser Companion Files.  However, I find Ralf Sesseler's DSON Loader Python script does a much better job than DS.

Since these are the only options for Poser users to import Genesis models, I can't complain.  I don't really care about Victoria 7 anyway.  I just started using Genesis about a month ago and will grab everything I can until the G2 models run out of clothes because it seems they probably won't be supported much longer.

But there's a never ending supply of V4 clothes.

I haven't tried for a long time but I used to find difficulties with slow downs if I used too many genesis in a scene whereas I can get 12 fully dressed and textured M4s in a poser scene.

I refuse to use dson ,if I use genesis I use it in the app it was made for

I have some DS scenes that work pretty well in poser. it's the figures that I don't use.

Load your content once using DSON (or export cr2 from DS) and then save it as a native Poser file in your library. Clean up with Netherwork's Creator's Toybox (comes with clear instructions and presets to do the job, which takes a few minutes). No DSON drag ever again. Poses and materials work quickly using DSON so you can leave those alone.

I will have a look at that. thanks RobZhena

I was having problems with some Genesis 2 morphs not working in Poser 11 when it first came out. I hunted around my Library and found multiple DSON auto_adapted folders. While PP 2014 apparently didn't mind, (the Library Search is set to Deep on both) it caused problems in Poser 11 Pro. Getting rid of the surplus ones by moving them to an unmapped folder solved the problem (I saved them in case I have a saved scene that might need something) The correct one is of course in the Writable Runtime in Scripts>DSON Support> Importer Preferences. If you have multiple versions of Poser, consolidate them to one location...

That's weird, I've been using DSON with G2F for a long time and never had problem, at least not significant enough that I can remember. Never had any problem with morph or anything. The DSON version that I use is 1.1.3.49. It's the older version because according to rumors, the newer version has problems.