The DAZ importer is a tool for importing files for DAZ Studio (DAZ User File *.duf, DAZ System File *.dsf) into Blender. It also contains some tools to make the assets more animation friendly.
I’ve followed your instructions but I can’t seem to get this to work. Here is the errors from the console:
Traceback (most recent call last):
File “C:\Users\Administrator\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\import-daz_init_.py”, line 275, in execute
getMainAsset(self.filepath, context, self)
File “C:\Users\Administrator\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\import-daz\main.py”, line 57, in getMainAsset
main = parseAssetFile(struct, toplevel=True)
File “C:\Users\Administrator\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\import-daz\file.py”, line 250, in parseAssetFile
return asset.parse(struct)
File “C:\Users\Administrator\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\import-daz\file.py”, line 122, in parse
asset = self.parseUrlAsset(mstruct)
File “C:\Users\Administrator\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\import-daz\asset.py”, line 144, in parseUrlAsset
asset.update(struct)
File “C:\Users\Administrator\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\import-daz\modifier.py”, line 351, in update
ref = list(parent.instances.keys())[0]
IndexError: list index out of range
Clearly there are differences in our DS setups, because I haven’t run across this problem. Should be fixed in the development version, with the caveat that I could not really test since I could not provoke the error. The updated file can be downloaded from
The panels are arranged a little differently in the development version, but the docs are still more or less valid. If you still encounter problems, perhaps you could start with something simple, like a nude genesis/genesis 3 character. For more debug info, you could also change the Verbosity slider in the Advanced setup panel. Verbosity = 3 is a good value (I Think I will change the default to that).
Since the previous stable version was released half a year ago there has been several improvements and additions.
A DAZ Studio plug-in for exporting the final world space coordinates for vertices and bones.
Limits on the number of facial expressions overcome, using handlers for bone drivers.
Material improvements, in particular for Cycles.
Posing improvements.
Many small bugfixes and additional features.
The most signicant improvement is the DAZ Studio plug-in. In previous versions Wavefront or Collada files could be used to find the final meshes with all morphs included, but this did not always work correctly. In version 1.1 I also attempted to deduce the final locations directly from the DAZ Studio files. While this in theory must be possible (after all, DAZ Studio does it), I never got it to work right, especially not fitting clothes to arbitrary morphed meshes. After I started to use the DAZ Studio plug-in to export the final world-space coordinates, meshes have always looked the same in Blender as in DAZ Studio.
The script has mainly been tested with DAZ Studio 4.9 and Blender 2.78c on Windows 7.
Okay, so I tried following the instructions, but for some reason the .zip file won’t show when I press the “Install add-ons” button and look in the directory.
EDIT: Never mind, found out I didn’t move it to the folder in question like a fool.
EDIT: Now I have learnt something new. I have some old Poser files that I could import into DS and then save as DAZ files. When I tried to import the .duf files into Blender, there were indeed some errors, but they were straightforward to fix. So at least the Poser files that I tried can now be imported into Blender.
However, there are some problems with rigging. Poser does mesh deformation with envelopes, but the importer only handles vertex groups. So you need to skin the model in Blender.
It is an importer for general Daz scenes, so it can import props, environments and figures, e.g. Genesis 1, 2, 3, 8, or the Daz horse. There might be problems if it encounters something that has not been tried before, like the converted Poser files that I learned about a few days ago, but it is usually not diffifult to fix such bugs.
Whereas the importer can import scenes with multiple characters, it is not something that I would recommend. Better to import each character into separate blend files and link or append them to the scene file.
I learned that you can import Poser files into DAZ studio and save them as DAZ files, which can then be imported into Blender. However, these files are slightly different from the native DAZ files, and they caused some errors in the import scripts. These bugs should now be ironed out.
The Rigify add-on was changed in Blender 2.79, which caused Rigify conversion of DAZ armatures to stop working. The new RC should work with both old and new Rigify.
Hi ThomasL,
I get the following error whenever i try to import a duf file into Blender and the Blender viewport obviously remains blank. I also tried loading the file from the DAZ library directly and still get the same error. I have followed your instructions from your blog to a T and followed every possible error handling and i still get the following error.
I am also attaching the DAZ imported error log file for your reference.
OK, clearly there is something strange going on in the file /data/meipex/headlights/headlights_geometry shell/headlights geometry shell.dsf in your DAZ directory. It is difficult to tell exactly what caused the problem without seeing this file, so maybe you could send it to me. Zippyshare worked fine. In the meantime, try to remove the head-lights in Daz Studio and export the model again.
Your problem is almost certainly the same that vida_vida has - your assets are located on F:, his on D: . I have tried to reproduce the problem, but I think I’m doing it in the wrong way. I put some assets on an external hard drive and then added the location as a new base directory (cf figure), but in that case I don’t get the full absolute path to the asset file.
EDIT: Saw your edit. What did you change to proceed?
