Hi, I picked this up some time ago and am just getting to try to render with it. My problem is the DSON conversion doesn't seem to be working right. I've got other items that are D/S that convert fine, but on this item there seem to be multiple problems. I've tried to reach the vendor through the site mail but haven't gotten a response. One problem is the shirt seems to have tail (kind of tuxedo like) as if the mess has two points pulled from the very bottom down. The other is the pants take forever in loading and seem to be searching for a file.

i13ES-Pants{17ccfe37-d6fe-b0fd-44b8-f345f7c0b237}.pmd

and gives this error

"The file was not found. Do you want to continue to look for missing files?"

I did look at the DUF files via notepad ++ but am not sure where to look for these errors as I'm not that familiar with the DUF format. Any help would be greatly appreciated. By the way is there a page that shows the proper design for creating a D/S item to properly convert to poser? I'm asking to try to understand what's needed so if I have to I can debug something I've purchased that isn't converting right. Kind of like pages that show CR2 format. Thanks again!

I don't see the pmd file listed in the readme and that is usually found in the same folder as the CR2.  I will need to dig around my bookmarked tutorials for the conversion to Poser CF.

That file should live in your default Poser Content runtime in a directory.... that I CAN'T PASTE INTO THE POST! :(

It is runtime/DSON/auto-adapted/data... I presume there is an i13 folder there where ii is looking.

Make sure this runtime is in a writable location; not anywhere in the c:/Program Files hierarchy if using Windows

If it is in a writable location, I would try deleting  the cached DSON files and let it make new ones by reloading the item. To do so, delete the i13 directories from the two cache directories, the location of which can be found in Poser under Scripts>DSON Support>Importer Preferences.  I'd restart Poser before reloading the item...

First, thank you both for your help. I noticed that in the data folder that one of the folders is i13 Estate Agent and the other just 13 Estate Agent. I was thinking that might be one of the problems but not the reason for the stretching of the mesh.  And in the readme there is no mention of the pmd, just this file belonging in the data file

RE_Pants_11796.dsf

I don't see any mention of the pmd file when looking through the duf file in notepad++. I have redownloaded DSON (was thinking I might have needed a version update). Will post after I've updated it.

First, thank you both for your help. I noticed that in the data folder that one of the folders is i13 Estate Agent and the other just 13 Estate Agent. I was thinking that might be one of the problems but not the reason for the stretching of the mesh.  And in the readme there is no mention of the pmd, just this file belonging in the data file

RE_Pants_11796.dsf

I don't see any mention of the pmd file when looking through the duf file in notepad++. I have redownloaded DSON (was thinking I might have needed a version update). Will post after I've updated it.

Okay, it's not DSON. I've tested loading other D/S items by other vendors with no issues. So I'm thinking there's something wrong in the file reference. Is there a guide as to what I should be looking for in duf files? Comparing vendors duf files I see different layouts. If I knew what to search for in the duf file I might find it quicker. I don't suppose any other poser user that has this outfit can test if they are having any troubles using the item in poser?

Aha! The DSON update did fix the shirt mesh error. Very cool. Now if I can get the pants to load properly I'm more than halfway there! :D Thanks again for the help and any other assistance!

There has been version update to the DSON importer.  Unfortunately, for me and some others it makes a dent in the back of the left ankle of Genesis 2; YMMV...

I was unaware of the left ankle dent. :( Thank you for the heads up! The pants still look for the file, and take forever to search for it. Occasionally DSON hangs and then crashes while searching for it. It's got to be a bad file reference, though I can't see it in the duf. Quick question, where (and what file type) is the material file that DSON converts to use for poser?  Is the material in the duf file? I see a UV default template for mapping. I guess I should read up on this more. A good idea for a new product would be a DSON converter file checker. Kind of a software program or script that checks if files are there and if not lists what's missing. Anyone know of anything like that anywhere? BTW, thank you again!

You can try D3D's DSONLoader, http://d3d.sesseler.de/index.php?software=poserpython&product=dson_loader, to import the pants.  You might have better luck with it.

First, thank you both for your help. I noticed that in the data folder that one of the folders is i13 Estate Agent and the other just 13 Estate Agent. I was thinking that might be one of the problems but not the reason for the stretching of the mesh.  And in the readme there is no mention of the pmd, just this file belonging in the data file

RE_Pants_11796.dsf

I don't see any mention of the pmd file when looking through the duf file in notepad++. I have redownloaded DSON (was thinking I might have needed a version update). Will post after I've updated it.

None of the PoserCF should even be referencing the PMD file. That file is auto-generated upon first load through the importer (and any subsequent time if those auto-adapted files are ever deleted). Either use the script hborre linked to above, or if you use Daz Studio at all, just create a new set of PoserCF for the pants. I wonder, if you opened the CR2 for the pants, if there's more in there than the version and runpythonscript lines, because there shouldn't be.

Here. For the pants, if you open up the *.py file, it should have these 2 lines only:

import dson.dzdsonimporter
dson.dzdsonimporter.loadCompanionDSONFile( sys.argv[0] );

The CR2 should look like this (WITHOUT the extra line between the next, these forums tend to do double carriage returns for some stupid reason):

{

version

{

number 9

}

runPythonScript "i13ES-Pants.py"

}

The DUF file next to those 2 files for the pants should be an exact duplicate of the DUF file from the Daz Studio version.

/edit

Oh hey it kept the formatting. Well that's nice.

Thank you hborre, will give the loader a go.

Thank you Vaskania. I did open the CR2 in notepad++ and saw it's exactly as you said (though I'll check again for the carriage returns). I want to say the python script may have said the same, I'll give it a check again. Much appreciated for everyone's help! Thanks again!

Aha... D3d has a file reference editor on his website. I wonder if this kind of does what I'm thinking already? *Apparently it does! Very cool!

*Edited to insert lines with * symbol before them.

None of the PoserCF should even be referencing the PMD file. That file is auto-generated upon first load through the importer (and any subsequent time if those auto-adapted files are ever deleted). Either use the script hborre linked to above, or if you use Daz Studio at all, just create a new set of PoserCF for the pants. I wonder, if you opened the CR2 for the pants, if there's more in there than the version and runpythonscript lines, because there shouldn't be.

The cr2's that actually load a DSON figure are auto generated and are in the the Writable Runtime Folder noted in the DSON Iimporter Preferences, under /Runtime/DSON/auto_adapted/content_files/ Each one of the folders there contains a. cr2, which calls the materials and morphs. The.pmds should reside in /RuntimeDSON/auto_adapted/data in the folder corresponding to the base figure or clothing item.; You can find the exact filename by looking in the cr2 with a text editor...

Yes, but I was referring to the CR2 in the user facing figure library, not in the auto_adapted folders.

Farther up the OP was asking what called the pmd and the materials; I think I quoted the wrong post....

In the CR2 (from the poser character library) I'm seeing exactly what you (Vaskania) typed in orange from what you posted at 12:01 AM Mon. The python script for the pants matches also what you typed in orange from the same post at 12:01 AM Mon. In the D/S folders I'm seeing (People, Genesis 2 Female, Clothing, I13, I13 Estate Agent) I'm seeing i13ES-Pants.duf and i13ES-Pants.png. In the data folder, I13, I13 Estate Agent, I13-Pants, I'm seeing the file RE_Pants_11796.dsf.

Looking (comparing the pants and shirt .dsf files, I'm wondering. The pants have a button. I see it under the polygon material group (count 2 then values). I'm wondering if the button is cause of the search for the material.... just thinking out loud... researching more. I've not been research continuously, more of check answers, then fiddle a bit, then do work, then fiddle a bit more, eat lunch, etc :)

Question, is it the in the .dsf or the .duf that materials are assigned to a particular item? Never mind, am looking at duf and thinking it's in the duf. Am looking if the button has materials assigned.

Okay, I'm looking at the duf in the area of materials, but am not seeing a separate set of values for the button though I swear somewhere I saw node instructions specifically for elsewhere the button. *button has current value [0,0,0]

Try this, rename the Poser DUF that's next to the CR2 and PY files (append it with .old or something) and copy the DUF from the People:Genesis 2 Female:Clothing:i13:i13 Estate Agent files to where the CR2 and PY files are. COPY don't move/cut.

Now in Poser, try loading using the CR2. If that works, then there was an issue with the original DUF on the Poser side.

Will give it a try, thank you :)

Nope, no joy :( After trying that, I tried to give the button a value. No joy with that either working. Will try more fiddling with it tomorrow. Thank you Vaskania for your help again.

Just a thought; does it load for you in Studio?

You might drop a note to i13; she is very accessible for help.

Thanks for all the help everyone. I did try many times, and finally got through directly her email. She's working on looking at the problem. :)