Do I have to load daz studio to use this dson importer or can i just make a folder and load gen charters from that ???

You don’t have to open DS to use DSON, but The DS native side of DSON products needs a DAZ library in which to reside. The DSON icons that show up in Poser call on the duf files over yonder in Dazland?

You need the DSON core (the native Daz Studio files, and the textures) and the PoserCF (the Poser library files with the script to launch the importer) installed for each product - they can be in the same location, your regular Poser library (the Data folder for the DSON core should sit alongside the Runtime folder).

I have the texture files for an architectural model made originally for Daz-only copied into my Poser Runtime/Textures library. The DSON User files for this model are currently in an Environments folder over in my Daz Content library. Where should I copy the contents of the Environments folder so that my Poser's DSON importer can find them, and can the Environments folder reside within my Poser Runtime library?

Thanks.

You don't need the user-facing files from the DSON Core installer, if you are doing things manually you just need the /Runtime/Textures folder and the /Data folder (the /Data folder goes in the folder that holds the /Runtime folder). So you have C:/Users/Public/Documents/Poser # Content/Runtime and C:/Users/Public/Documents/Poser # Content/Data if your Poser library folder is C:/Users/Public/Documents/Poser # Content, for example.

Okay I've copied the Data folder, this of course after I had performed the scene export within Daz. Not sure what I'm doing next or whether I've still missed a step somewhere along the way.

I'm not sure what you are showing here. Is this cntent that came with PoserCFs, or are you creating your own from DS?

RHaseltine posted at 3:22PM Sat, 02 February 2019 - #4345030

I'm not sure what you are showing here. Is this cntent that came with PoserCFs, or are you creating your own from DS?

This is based on an architectural model and scene that originally created for Daz-only and I am trying to get this architectural model into my Poser stage. In essence, make this scene work in Poser as it should.

The screen capture I provided is showing my Poser 11 open and me looking to find what the next step is in making the DSON importer work to bring the scene and its elements into my Poser stage.

OK, so I now deduce that you are trying to import a scene for which you did not create a Poser companion file. I recommend you install D3D DSON Loader (http://d3d.sesseler.de/index.php?software=poserpython&product=dson_loader), which will let you manually import your duf file from DS. There is no need to copy any of your data or textures to the Poser runtime. It will use the information in your DS data and runtime.

RobZhena posted at 5:15PM Sat, 02 February 2019 - #4345065

OK, so I now deduce that you are trying to import a scene for which you did not create a Poser companion file. I recommend you install D3D DSON Loader (http://d3d.sesseler.de/index.php?software=poserpython&product=dson_loader), which will let you manually import your duf file from DS. There is no need to copy any of your data or textures to the Poser runtime. It will use the information in your DS data and runtime.

As long as that is selected as an external library in Poser - though having the files in a secondary or later location will, or has in the pst, have an impact on performance.

RobZhena posted at 7:24PM Sat, 02 February 2019 - #4345065

OK, so I now deduce that you are trying to import a scene for which you did not create a Poser companion file. I recommend you install D3D DSON Loader (http://d3d.sesseler.de/index.php?software=poserpython&product=dson_loader), which will let you manually import your duf file from DS. There is no need to copy any of your data or textures to the Poser runtime. It will use the information in your DS data and runtime.

The screenshot you see in the previous post is my Poser 11 with my Scripts menu open to show the DSON Support and its Subdivision menus.I'm not sure this is the right place for finding and using the DSON Importer in Poser. If this is not the right area I am currently in in the Scripts Menu, where should I be within Poser to start the DSON Importer into action?

Thanks.

You need to download the script from the link I provided. Once installed properly in your Poser 11 Application (on a Mac), it will appear on the scripts menu under D3D.

I actually already do have that Python script installed into my Poser Python Scripts library. Nevertheless I did download and install the DSON Loader script again, this time from the link you provided.

So now what would be my next step for actually bringing this architectural model into my Poser stage?

Launch DSON Loader. In the finder/whatever in Windows box that opens, find your scene file wherever you saved it (possibly in in your My DAZ 3D Library). e.g, My Buildings.duf, and select it. The loader may churn for a while, but eventually your stuff will appear in Poser. At that point, you can save it in your Poser library and think about whether you want to convert the elements to Poser native format using a tool like Netherwork's Creator's Toybox.

RobZhena posted at 8:26AM Sun, 03 February 2019 - #4345102

Launch DSON Loader. In the finder/whatever in Windows box that opens, find your scene file wherever you saved it (possibly in in your My DAZ 3D Library). e.g, My Buildings.duf, and select it. The loader may churn for a while, but eventually your stuff will appear in Poser. At that point, you can save it in your Poser library and think about whether you want to convert the elements to Poser native format using a tool like Netherwork's Creator's Toybox.

I'm not sure where to find the DSON Loader in my Poser although I have literally been looking everywhere for it. This has been the part where I have been stuck for, literally, weeks now.

You do not have DSON Loader properly installed. It is different from DSON Importer. It would be on your scripts menu in a line item for D3D. Again, I use a Mac and don’t know the precise Windows equivalent. You have to have the script in the script menus folder associated with the Poser program itself, which on the Mac resides in Applications, not the Shared folder where your content goes. Maybe someone who speaks Microsoft can weigh in.

RobZhena posted at 6:52PM Sun, 03 February 2019 - #4345117

You do not have DSON Loader properly installed. It is different from DSON Importer. It would be on your scripts menu in a line item for D3D. Again, I use a Mac and don’t know the precise Windows equivalent. You have to have the script in the script menus folder associated with the Poser program itself, which on the Mac resides in Applications, not the Shared folder where your content goes. Maybe someone who speaks Microsoft can weigh in.

I have both installed.

Windows 8-64 bit 26 Gb RAM nVidia 1060 graphics card

You did not install the DSONLoader script correctly otherwise there would be a menu entry called ’D3D’ in your scripts menu. The script has to be installed into the application runtime. Don’t know where that is on Win as i am on Mac.

Nagra_00_ posted at 10:15PM Tue, 05 February 2019 - #4345215

You did not install the DSONLoader script correctly otherwise there would be a menu entry called ’D3D’ in your scripts menu. The script has to be installed into the application runtime. Don’t know where that is on Win as i am on Mac.

The drilldown for my current location of the DSONLoader.py is E:Poser ContentPoser 11 ContentRuntimePythonposerScriptsScriptsMenuDSON SupportD3D That's my main Poser Runtime where all my Poser content resides.

The Poser content directory resides in both your Documents folder and again in Program Files;.or possibly Program Files(x86) if the 32 bit version is installed as well. I am only running the 64 bit version. It's the Program Files runtime where the changes take place IIRC

The path for Python scripts always have to be within the Runtime! The Runtime has to be in Program Files->Smith Micro->Poser (whatever version)

Runtime->Python->addons->dson (the DSON importer by DAZ) or:

Runtime->Python->poserScripts->ScriptsMenu->Dimension3D->DSONLoader.py (the DSON loader by D3D)

mackis3D posted at 7:10PM Fri, 08 February 2019 - #4345515

The path for Python scripts always have to be within the Runtime! The Runtime has to be in Program Files->Smith Micro->Poser (whatever version)

Runtime->Python->addons->dson (the DSON importer by DAZ) or:

Runtime->Python->poserScripts->ScriptsMenu->Dimension3D->DSONLoader.py (the DSON loader by D3D)

I tried copying those 2 files into the first directory you specified, then when that didn't seem to work I moved the two files over to the other directory you specified. Still no DSON Loader shows up anywhere in my poser, that is unless I'm just simply lookin' in all the wrong places for it. What else could be wrong?

Would someone be willing to join me in a desktop share session sometime, take a few moments and help me troubleshoot this DSON thing? It's been a month now since I have been chasing this all around.

What was the full path you placed the files in, starting from the C: drive?

I mentioned earlier. Poser has a runtime in your protected programs files or program files (x86) or both; depending upon the version(s) installed. Make the changes there. Not the runtime in your doc files. Mackis3D has told you the same thing. Have you done the additions to the protected programs runtime or are you still playing in the wrong place in your document folder.?

parkdalegardener posted at 7:43AM Sun, 10 February 2019 - #4345743

I mentioned earlier. Poser has a runtime in your protected programs files or program files (x86) or both; depending upon the version(s) installed. Make the changes there. Not the runtime in your doc files. Mackis3D has told you the same thing. Have you done the additions to the protected programs runtime or are you still playing in the wrong place in your document folder.?

As Mackie3d instructed me, C:Program FilesSmith MicroPoser 11RuntimePythonaddonsdson

RHaseltine posted at 7:45AM Sun, 10 February 2019 - #4345687

What was the full path you placed the files in, starting from the C: drive?

C:Program FilesSmith MicroPoser 11RuntimePythonaddonsdson

Thats the wrong one for the D3D script. It has to be placed in:

C:Program Files/Smith Micro/Poser 11/Runtime/Python/poserScripts/ScriptsMenu/

As the path name suggests. All scripts that should appear in the ’Scripts Menu’ have to be copied into the ScriptsMenu folder or a sub folder of it.

Nagra_00_ posted at 7:54PM Mon, 11 February 2019 - #4345750

Thats the wrong one for the D3D script. It has to be placed in:

C:Program Files/Smith Micro/Poser 11/Runtime/Python/poserScripts/ScriptsMenu/

As the path name suggests. All scripts that should appear in the ’Scripts Menu’ have to be copied into the ScriptsMenu folder or a sub folder of it.

I moved the three files there, DSONLoader.py, DSONLoader (the text document and dzdsonimporter.pyd into the directory you specified and when I fired up my Poser 11 I got popup mainWacros error message,

'An errror occurred importing addon dson : ERROR: No module named dzdsonimporter'

and

'An errror occurred importing addon dson : ERROR: No module named dzdsonimporter'

Why did you move ’dzdsonimporter.pyd’? That file is part of DSON by DAZ. DSONLoader is a script by D3D. Don’t mix them.

Nagra_00_ posted at 5:11AM Tue, 12 February 2019 - #4345916

Why did you move ’dzdsonimporter.pyd’? That file is part of DSON by DAZ. DSONLoader is a script by D3D. Don’t mix them.

OK where should I move the dsonimporter.pyd back to?

Don’t know, i am on Mac and there is no ’dzdsonimporter.pyd’. The only file i found is ’dzdsonimporter.so’ which is a dynamic library that is installed in ’Python/addons/dson’. You may just reinstall the DAZ DSON thing. That one worked before, didn’t it.

Nagra_00_ posted at 6:27PM Tue, 12 February 2019 - #4345925

...You may just reinstall the DAZ DSON thing. That one worked before, didn’t it.

Nope, never has worked.

From your screen shots at least all the related menus had been there and no error on Poser start.

mackis3D posted at 10:54AM Wed, 13 February 2019 - #4345515

The path for Python scripts always have to be within the Runtime! The Runtime has to be in Program Files->Smith Micro->Poser (whatever version)

Runtime->Python->poserScripts->ScriptsMenu->Dimension3D->DSONLoader.py (the DSON loader by D3D)

Not in Windows; User Account Control prevents writing to the C:/Program files hierarchy by the user.

If you install the D3D DSON Loader into your default Poser 11 Content location, it should show up in the Scripts menu after you restart Poser.

To find that default location, in the Poser Library, select 'All' from the Dropdown near the top left, right click Poser 11 Content, and click on 'Show in Explorer'.

When you install the DAZ DSON importer, the installer is given permission to write into the Poser program folder, so it is installed there However, you can't manually copy stuff there; the program is not permitted to access it......

I've re-installed the DSON importer and that appears to have remedied the problem with the popup message I was getting.

So now I'm back to the point I was awhile ago in looking for the DSON importer so I can put it to work but, as it would appear, I'm still obviously looking for it in all the wrong places.

The DSON importer works transparently with items that have Poser Companion files; one just loads them through the Poser library. However, the Companion file is simply a Python script that calls the DSON Importer. They can be created in Studio, but with the D3D DSON Loader Script, the Importer is called directly without the need for the Companion File.

Looking at your screenshot, it appears that you have the DSON Loader script installed in the Poser program directory; unless you have Windows' User Account Control turned off, you might be able to see it in Explorer, but Poser wont find it to put it on the Scripts menu, because it's really someplace else. However, since it appears you have browsed there via File>Run Python Script, try running it (DSONLoader.py) from there, browse to your saved scene and see if it loads up....

WandW posted at 9:39PM Thu, 14 February 2019 - #4346115

The DSON importer works transparently with items that have Poser Companion files; one just loads them through the Poser library. However, the Companion file is simply a Python script that calls the DSON Importer. They can be created in Studio, but with the D3D DSON Loader Script, the Importer is called directly without the need for the Companion File.

Looking at your screenshot, it appears that you have the DSON Loader script installed in the Poser program directory; unless you have Windows' User Account Control turned off, you might be able to see it in Explorer, but Poser wont find it to put it on the Scripts menu, because it's really someplace else. However, since it appears you have browsed there via File>Run Python Script, try running it (DSONLoader.py) from there, browse to your saved scene and see if it loads up....

Well after picking up the DSON Loader from the script from the Poser Scripts menu and then navigating over to my Daz Library/Scenes folder and choosing a DSON User file from there and after a few seconds of seeing a little popup that says 'Parsing Scene' I then get this little popup.

Have you added your DAZ Library to Poser as an external runtime folder? If you haven't, here is a how-to; the section at the bottom for Poser8-10 applies to11 too...

https://support.smithmicro.com/customer/portal/articles/1982178-installing-poser-content-from-previous-poser-versions?b_id=8847

@WandW

Not in Windows; User Account Control prevents writing to the C:/Program files hierarchy by the user.

I'm working with Windows 7. UAC does not prevent writing to the C:/Program. At least not in the Professional edition. And of course that can be manually changed for the Poser folder too. Which is easier than to splatter Poser files around the C: drive. But I use only one Runtime anyway...

So @generation2235 my way works for me and it should for you too. But @WandW's way is also working - if your UAC is on and you don't want to change that.

My folder structure looks like this:

In the 'DSON' folder you see a folder named 'auto_adapted' - that is created by Poser after you've loaded a figure that needs DSON into Poser. I moved the 'Data' folder from DAZ Studio into that DSON folder because somehow that works better. The 'Runtime' folder in the 'DSON' folder is created by DAZ Studio after you link the 'DSON' folder in DAZ Studio! It's an empty Runtime dummy.

Don't forget to link the 'DSON' folder (I named it DSON) to the libraries in DAZ Studio (if you use DS for converting general weight items to Triax) and Poser!

You can use your Poser Runtime in DAZ Studio too. You just have to link that additionally if you use DS.

The paths for the two different DSON importers into Python I've already described.

I have time to help you. Just PM me.

Thanks for this information. I am going to have to set aside at least a couple of hours or so, so I can map this out and be sure I'm following everything correctly, tedious as it has been over the course of this past month.

Not sure what UAC is, can someone please tell me what that stands for?

generation2235 posted at 8:03AM Fri, 15 February 2019 - #4346207

Thanks for this information. I am going to have to set aside at least a couple of hours or so, so I can map this out and be sure I'm following everything correctly, tedious as it has been over the course of this past month.

Not sure what UAC is, can someone please tell me what that stands for?

User Account Control, which is a security feature of Windows since Windows Vista...

https://www.digitalcitizen.life/uac-why-you-should-never-turn-it-off

A more technical description here...

https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works

mackis3D posted at 8:25PM Tue, 05 March 2019 - #4346202

@WandW

Not in Windows; User Account Control prevents writing to the C:/Program files hierarchy by the user.

I'm working with Windows 7. UAC does not prevent writing to the C:/Program. At least not in the Professional edition. And of course that can be manually changed for the Poser folder too. Which is easier than to splatter Poser files around the C: drive. But I use only one Runtime anyway...

So @generation2235 my way works for me and it should for you too. But @WandW's way is also working - if your UAC is on and you don't want to change that.

My folder structure looks like this:

In the 'DSON' folder you see a folder named 'auto_adapted' - that is created by Poser after you've loaded a figure that needs DSON into Poser. I moved the 'Data' folder from DAZ Studio into that DSON folder because somehow that works better. The 'Runtime' folder in the 'DSON' folder is created by DAZ Studio after you link the 'DSON' folder in DAZ Studio! It's an empty Runtime dummy.

Don't forget to link the 'DSON' folder (I named it DSON) to the libraries in DAZ Studio (if you use DS for converting general weight items to Triax) and Poser!

You can use your Poser Runtime in DAZ Studio too. You just have to link that additionally if you use DS.

The paths for the two different DSON importers into Python I've already described.

I have time to help you. Just PM me.

As happens occasionally... Yours is different from mine. Where did you find that little window with the DSON folder in it and where did you find the other stuff down at the bottom?

The little folder is a screenshot from DAZ Studio. You have to manually locate that folder in DAZ Studio.

Even though these articles are a bit outdated by now they give an introduction to install and use DSON:

http://docs.daz3d.com/doku.php/public/software/dson_importer/poser/userguide/dson_installation_requirements/tutorials/dson_installation/start

http://docs.daz3d.com/doku.php/public/software/dson_importer/poser/userguide/dson_importer_usage/tutorials/using_dson_importer/start