Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Hi everyone, I'm experiencing a problem with the Sagan script/plugin in DAZ Studio, and I can't save my files or set the export directory properly. Here are the details:
When I try to use Choose Base Directory or Current Export Directory, the buttons don’t work, and I’m unable to select or input anything.
I occasionally get the error message: "Unknown File Format - No importer for the file format can be found" during certain operations.
I’ve already tried the following:
Running DAZ Studio as an administrator.
Resetting the layout and preferences in DAZ Studio.
Clearing temporary files and reinstalling the Sagan script.
I’m using DAZ Studio version [insert version] on Windows 11, and the plugin has been installed in the correct directory.
I’m wondering if the issue could be related to:
A misconfiguration of the script/plugin.
Missing or corrupted files.
An incompatibility with my version of DAZ Studio.
Has anyone encountered a similar issue? Is there a way to completely fix this or reinstall Sagan properly? Any advice would be greatly appreciated!
Thank you in advance for your help.
Hi @francescogenovesi78
Wow. I found that the Qt slot for the Choose Base Directory button was missing in Qt Designer. I must have messed that up somehow, and I'm not enough of a Windows programmer to have automated tests set up. I'll fix it and make an update tonight.
But how could we go 18 days with no one reporting that pretty serious bug?
As for the "Unknown File Format..." error, can you provide more details? That is not a Sagan error message; it doesn't occur in the code, and "importer" in the text is kind of suspicious...
OK, 3.6.1.0 is up at the link to the latest version. Sorry about the regression.
The only user-facing change is the fix for the Base Directorty button.
I'm guessing many of us periodic users hadn't gotten to it yet... Downloaded, but waiting for a free time-slice...
For me it's the kind of tool that isn't touched until it's the most important capability in my pipeline, lol, and if it ain't broken, I'm apt to "get to it someday soon" (yeah, DAZ soon).
I've downloaded the newest update with appreciation, and will install it 'soon'! The appreciation really happens when it 'just does it'... again... Easy to take it for granted - the lack of feedback is likely the curse of your good work, I suppose.
heh,
--ms
As usual, thanks, MS.
Ha ha "my good work" until I disable a button by accident :)
BTW, if there are any competent Win32 guys out there who know how to set up a good GUI unit test framework, please, let me know :)
yeah, I only use the obj series export and it works on the rather old build I have
is very much appreciated
but I am always doing so many different things at once every day, trying new things all the time not using D|S or even 3D
tend to go off on tangents with my hobbies a lot
From the breadth of your posts alone, one can see how many pies you've got your fingers in, Wendy :)
Oh, what I would do to osmose the wisdom and lessons-learned across this domain from a few of you folks - both inspiring and humbling. Of course, this would also require a serious personal SSD expansion, lol.
Not enough hours in a minute... Glad y'all are here to compare notes with.
--ms
Permission to use that :)
I apologize for the delayed response; I've been busy reconfiguring my PC and juggling work, leaving me little time to reply earlier. I want to express my heartfelt gratitude to the creator of Sagan for their outstanding work. As a developer, I frequently use their product and deeply appreciate the quality and dedication that shines through every aspect of it. Thank you from the bottom of my heart!
@francescogenovesi78
An equally heartfelt "You're welcome"... The feeling of "Community", of a group of people all trying to do the same thing and facing the same obstacles, is what keeps me going in the face of all the challenges in developing for DAZ Studio, both technical and social.
I have sagan-3.6.1.0 installed and there is a checkmark in my About Installed Plugins. But when I go to Edit there is no option for export. I'm using Daz 4.23.0.1
Read the first post of this topic. You have to configure the environment and put the option where you want it.
Thank you very much and thank you for a great plugin :)
You are very welcome. I hope it meets your needs.
I'm a good ways into supporting Strand Based Hair. If I don't encounter any DSBS, I should have Sagan generate a script that will create a HairCurves object at a given frame, presumably the rest pose, soon.
Then I'll work on support across and animation range.
Frankenstein's monster is breathing...
Very nice thanks for the update.
mindsong raises eyebrows, smiles, and does a thumbs up...
--ms
Hello,
I would like to report an issue that has occurred after the latest updates. Currently, the GoldenPalace_Shell model no longer imports correctly into Maya. Previously, the import included the full model along with the genitals, with the genital UVs properly assigned to UDIM tile 1008, allowing for correct texturing.
Now, however, only the genital mesh is imported, and the rest of the model is missing. This breaks the texturing workflow and makes it impossible to work as before.
Could you please look into this and help restore the correct import behavior?
Thank you very much in advance for your assistance.
In the image, I’m showing how the shell was imported before and after the recent updates.
@francescogenovesi78
UDIMs is something I am yet to figure out.
But first, about the geometry not being exported, Sagan's geoshell code won't export a facet if it is hidden by material group, or by facet group. Can you check to make sure the geoshell in its entirety is visible by both of those methods? That would be the simplest reason why the geometry isn't showing up, so let's hope for the silly, simple thing first :)
Let me know.
Hi, very nice updates!
I am having an issue with config persistence. The sagan settings reset every time I close the sagan panel, no combination of saving, loading or scene saving actually saves the sagan setting so every time you export a scene you have to browse for output folder and for files. You can load the sagan settings file manually, but again you have to browse every time. I am using 3.7.0.0 as downloaded from the website, not sure if this is relevant but inside the Daz Studio in About Plugins it says version 3.6.1.0
Looks like the sagan config file has to be named exactly the same as the scene .duf and has to be in the same folder as scene's .duf file for it to auto load.
Anyways, SBH hair works amazing, really great stuff!
Could you provide the C++ library file for Sagan? I would like to integrate or call it in my own plugin.
@starslinger
Thanks for the feedback. It's rare and appreciated.
Yes, maybe there's a better way. Again, I'm not a very good Win32 programmer, ev and don't know how the problem of config files is handled there. When that code was written, I couldn't just ask an LLM :) I'll revist it, but I'm trying to get the hitchens stuff out the door.
I think you will appreciate the new Blender addon that's coming that automatically updates the SBH if it is animated in DS, as well as integrates some other tools I wrote but were previously just scripts.
And yes, I need to write something that keeps the version numbers synced. God, I hate Win32... did I mention that? :)
Hi @qwq123qa
Is your plugin open sourced?
may be open-sourced or publicly shared depending on development progress.
If you decide to open source it, like Sagan/Hitchens already is, I'd be happy to refactor it to expose an API.
Thank you for the suggestion! I agree that following the Sagan/Hitchens open source model would be beneficial. I’d welcome your help in refactoring the codebase to expose the API.
I'm sorry, my sentence was kind of klunky... I meant that I would refactor my own code to expose an API, which Sagan currently does not do. Because I've had to figure out how to do certain things over a period of years, the "iterative" nature really shows in the (lack of) design. To expose a clean API would require significant time. Time which I don't have much of to work on Sagan, and time which I'd prefer to spend getting Hitchens up and running again. But if you were working on another open source tool to contribute something cool to DAZ, I'd feel like I had to somehow "make" time to do it.