Interesting that others think Poser 11 worked with DSON and G2F import. I do a lot of that, and after the 11.1 update, I could no longer apply 'poses' to G2F figures with clothing conformed. As near as I could tell, (for example) a HAND pose in DUF format wondered off down the conformed clothing & did nothing (or worse). Pretty much broke my work. Eventually I uninstalled 11 and went back to PoserPro 10/2014. So 11.0 had worked fine, but 11.1 didn't. I doubt I'll go down the Poser 11.2 rabbit hole, but ..

.. my questions:

1. would I need to reinstall 11.0/11.1 to trial the 11.2? Or is this stand-alone?
2. will installing 11.2 break my PoserPro 10? I remember installing 11 changed the way my 10 worked. Maybe that was the problem - 11 & 10 mixed somehow? Shouldn't have two versions at the same time?

My DAZ Install Manager shows me "version 1.2.0.12. I also have a version 1.1.3.50 or a few 1.0.0.xx

So far, the 1.2 is working fine under Poser10/2014, with none of the posing problems.

willdial posted at 4:29PM Wed, 11 April 2018 - #4326776

I have Poser Pro 11 and I do not get this problem with G2F and DSON. What version of the DSON Importer are you using?

I have the latest from DAZ3D, which hasn't change for a long time & I use the DAZ Dl manager, so I assume I'd see if a new one was offered.

The CR/PP import is fine, it is only the DUF files being misinterpretted by the PZ/python stub (so I guess DSON import). I noticed the items in the DUF are NOT fully qualified, so for example it might be "url" : "name://@selection/chest:?rotation/x/value", "keys" : [ [ 0, 7.928934 ] ] ... but many things have a 'chest', so I am guessing the code walking the object tree gets confused now and walks down the wrong tree.

Okay - some progress. It seems P11 is very fussy about which library folder is open - some cause the "new set" pop-up ... some do not. So I can add them into some odd place I don't want ... but obviously can move via file explorer later.

Second wrinkle - despite the props being parented to V4, they save as "parent UNIVERSE" in the new pp2. So I did need to edit the new pp2, changing this to "smartparent lForeArm:1" and so on, for each item in the new bundled pp2.

(As a side, I'm still a bit fuzzy about the lForeArm:1 vs lForeArm:5 - why 1 or 2 or 5? Most of the original jewelry PP2 had a ":2" after each actor ... except one file had ":5". I just changed them all to ":1" in my bundled PP2 and P11 seemed to take it fine.)

EClark1894 posted at 3:55AM Tue, 22 November 2016 - #4290382

Now save the props to the library ...

Hmmm, at least in Poser 11, the "save to library" icon in Props seems to do nothing. If I'm in the POSE library, it works as I expect (& is how I'm saving my jewelry 'adjuster' poses) but if I'm in Characters, Props, mats, etc, it seems to do nothing at all. Is there another way to activate this? via menu or macro?

• Thanks

I'll give the save as prop method a shot - course they won't be loading back onto V4, but to G2F. I've been doing that with PZ2 for a while - am making G2F in DSON 'adjusters' for V4 jewelry.

As mentioned, I have P11 and PP2014.

As an Aiko4 fan - I love everything of RedViper's over at ShareCG: redviper2012. Unfortunately, he/she had 10 times more stuff there .. but deleted most of it (which i fortunately still have). Pity for the rest of you.

This is what my original PoserPro 2014 download looks like (but there have also been several SR/patches). If memory serves me right, when you run the 'Install Poser Pro 2014", it kind of shepherded the running of the other/content EXE.

• Directory of F:GraphicsPoserPro_201426510 Mar-2014
• 03/15/2014 03:27 PM 589,419,504 Install Poser Pro 2014 (10.0.3.26510).exe
• 03/15/2014 03:15 PM 233,346,840 PoserAnimals (10.0.3.26510).exe
• 03/15/2014 03:21 PM 394,906,040 PoserCartoons (10.0.3.26510).exe
• 03/15/2014 03:18 PM 286,537,224 PoserCasual (10.0.3.26510).exe
• 03/15/2014 03:27 PM 598,182,032 PoserClothing (10.0.3.26510).exe
• 03/15/2014 03:19 PM 318,819,696 PoserHair (10.0.3.26510).exe
• 03/15/2014 04:19 PM 1,291,961,488 PoserNudes (10.0.3.26510).exe
• 03/15/2014 04:39 PM 821,352,160 PoserProps (10.0.3.26510).exe
• 03/15/2014 03:38 PM 1,148,243,384 PoserSupport (10.0.3.26510).exe
• 9 File(s) 5,682,768,368 bytes

... a DSON installer ...

Actually, the real answer is confusion in the term DSON. DSON does not mean Poser support (or even import-ability). DSON is a DAZ term for an object format used by DS, and has nothing to do with Poser or DSON import. DSON is also not a special export format for Poser.

The key buzzword to watch for is "Poser Companion Files" or "PCF". Or if they mention files as "DUF", that is DS only. You'll need to see mention of CR2/HR2, etc if you expect build-in Poser support.

DSON import is not magic, as some things just do not map. For example, lately DAZ has been coming out with a lot of weekly-freebie scenes (like a shower or room) which is DS only. While I can use DS to create the PCF file, often the materials are, err ... unfortunate. I assume this is why artists might choice not to "just make PCF files", as they do need to spend some quality time re-doing the materials.

What i did (& tend to always do) is buy a new cheap HD (or move to SSD?), make a 100% duplicate of your old drive, then let the upgrade happen on 1 of the 2 drives.

Worse case, you just swap back the old drive & life returns to normal. Plus if something breaks, you can always mount the old drive as "D" or whatever & access all files. That is also how i rebuild my drive "C" once a year, except I do a fresh install on the new/other/reformatted drive, saving the old working drive as backup. Worstcase, put the old drive back in as C and I'm back to where I was last week.

A related but different question - (minor hijack of this thread) - does DSON work in Poser 11 PRO "as well as" it works in Poser 2014 PRO? (I'm not asking folks opinions of DSON! Some love; some hate - different topic.)

I so far haven't upgraded from 2014 to 11, in part because i didn't see any new features I wanted, and also because I feared SM may have hampered DSON by accident (or carelessness, or even on purpose). However, if G3F can work in PP11 DSON, then I'd have a reason to consider upgrading. Still might not. With V4/Aiko4 and G2F/Callie6, I have far too much content to honestly want to buy more ... ha ha - famous/foolish words!

On topic, I'd probably delete my PP2014 is PP11 was working, so hopefully less cross-talk. Anytime I want 'legacy', I still have Poser7 installed for checking PZ files, etc.

I suspect this could be a resource issue - smaller HW will suffer more.

My Poser 2014 PRO has been running Windows 10 since last summer - no problems, plus I like the fact it can actually use ALL 24GB of RAM I have (plus I also have an AMD 8-core). Win 7 still has 2GB memory limits per thread - some signed 32-bit handle issue EVEN in 64-bit Win 7. Also, I reformat & rebuild my drive C about once a year, so I don't have a lot of old baggage. All of my data (& my Document, Video, Poser Content, etc) are on a secondary Drive "F" which is 2TB. Literally, there is nothing on "C" which I can't replace with a little install-elbow-grease.

I also have an Atom-processor netbook, which I moved to Win 10 & found it always runs at 50% CPU. I even rolled that back to Win7 (actually, I swapped in the old drive back in), but then discovered that it hadn't been much better (30-40%). So I went back to Win 10 & disabled a lot of things.

One thing I discovered - disabling OneDrive had a huge impact on the netbook - allowed it to drop from 50% to 11-20% CPU in one step. I do my backup/sharing on a 3TB NAS, so the OneDrive is NOT very attractive. I also disabled on the 8-core, but that didn't seem to notice & idles at 2-4% only.

Hmm - I think Win7 limits all threads to 2Gb RAM. Am I wrong? The way Poser has used memory has changed over the years.

For example, if I understood what I was seeing, my old Poser8 would have 3 'partial-scene' threads running on a quad-core, and the last core was the manager. So while the total load might be 100% at first, usually 1/2 way through the render the CPU load had dropped to 50% or less, as 1 or 2 of the partial-scene threads had completed their section and stopped. No increase in "memory" would fix that! Also, some older version of Poser (non-PRO) limit all threads to 2GB RAM regardless of the Windows version ... so adding more RAM is pointless.

Newer Poser does a better job of keeping all working. For example, at least with PoserPRO2014, all cores keep working, as each is doing small portions of the scene. In fact, I splurged to buy PP2014 (& move to Windows 8) after P8 to gain the larger 64-bit support which allows (as example) any 1 thread to use ALL available RAM. So if you are using an older Poser under Win7 64-bit, you are going to be limited to a few threads max'd at 2GB each, and adding RAM won't help. This was a W7 thing - as even in Windows 7 64-bit, all threads were limited to 32-bit RAM space.

My system is AMD FX-8350 8-core with 16GB RAM. I find the shaders used have the max impact, so for example any scene with glass or glossy-surfaces designed for DAZ renders horribly in Poser - so as example, I select any glass and apply a Poser-friendly 'glass' MC6, and that can EASILY cut 90% of the render time off a stupid scene with a few water glasses on a table!?!?!

I'll add that the DSON import action of the G2F creates the large object saved in the PZ3/PZZ, and it will include all the G2F morphs you have in your data directory ... so be aware that various 'new' characters (or once were new) like G6 or N6 or TJ6 can add up to 1/4 MB of morph dials each EVEN if the morph is not active. So for example, I create a Caille6, and low and behold, she comes with all of the G6, A6, V6 dials (& would have B6, TJ6, O6, N6 had I not removed).

I guess this makes sense if I want to create a C6, then turn c6 off and dial her to be a TJ6 auto-magically ... but I'd thought one applies pose files to add such bulk ... but, that's not the case. Oh well. it is what it is. Last time I cleaned up my data file, I ejected most of the misc x6 forms I don't use. For example A6 with 'growing up' can be a TJ6 or B6, so those have no value. As a 'reduced %' C6 can be a G6.

So the relevance to this thread is adding new items to the data directory after the fact does NOT update the base character in your PZ3/PZZ.

Hmm, as I've just finally (after 2 years) become good at using G2F in Poser, I agree there is a lot of things TO AVOID. For example (sorry DAZ) avoid adding new figures you don't plan to use. For example, I installed Ninive 6 (a skinny gal) and found she adds about 250 KB to every Pz3 I create (all the morph dial, FPM, PBM, etc).If you don't use, why allow such waste?

So now I am building a new runtime of G2F things just for Poser. I am not really seeing anything crippling about 2 DSON figures with clothes. Yah, PP2014 is a little sluggish, but it is not debilitating.