I have no explanation as to why I couldn't get those files to show up yesterday and bone minion. Today they do show up, but once I click execute, DAZStudio immediately crashes.
As I expected, the log shows Not a Number errors and then crashes:
2025-12-11 10:34:32.939 [DEBUG] :: ERROR: NaN has been detected for l_toes Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.940 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.941 [DEBUG] :: ERROR: NaN has been detected for l_bigtoe1 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.941 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.942 [DEBUG] :: ERROR: NaN has been detected for l_bigtoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.942 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.943 [DEBUG] :: ERROR: NaN has been detected for l_indextoe1 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.944 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.945 [DEBUG] :: ERROR: NaN has been detected for l_indextoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.945 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.946 [DEBUG] :: ERROR: NaN has been detected for l_midtoe1 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.946 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.947 [DEBUG] :: ERROR: NaN has been detected for l_midtoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.947 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.948 [DEBUG] :: ERROR: NaN has been detected for l_ringtoe1 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.948 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.949 [DEBUG] :: ERROR: NaN has been detected for l_ringtoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.949 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.950 [DEBUG] :: ERROR: NaN has been detected for l_pinkytoe1 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.950 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.950 [DEBUG] :: ERROR: NaN has been detected for l_pinkytoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.950 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.951 [DEBUG] :: ERROR: NaN has been detected for l_metatarsal Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.951 [DEBUG] :: [8.86436e-10,3.46585e-11,-1.51037e-10,1]
2025-12-11 10:34:32.960 [DEBUG] :: ERROR: NaN has been detected for r_bigtoe1 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.960 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.963 [DEBUG] :: ERROR: NaN has been detected for r_indextoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.963 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.964 [DEBUG] :: ERROR: NaN has been detected for r_midtoe2 Local Rotation! [nan,nan,nan,nan]
2025-12-11 10:34:32.964 [DEBUG] :: [0,0,0,1]
2025-12-11 10:34:32.966 [DEBUG] :: ERROR: NaN has been detected for r_ringtoe2 Local Rotation! [nan,nan,nan,nan]
You need to remove the offending pose from the list (or uncheck it).
I do not understand what this kind of error is. Is there a way for me to correct it so that I would then be able to convert these files? I'm not very computer savvy, but I would still like to know if there's any way to do this.
OK, I did some research on what these NaN Errors are, and I ran a terminal command to correct them. It looks like it worked. I am now converting those files from G8 to G9.
Hi, I spent yesterday trying to convert part of my pose library (productive procrastination, yay), and everything went well until the conversion itself happened. I have a list of about 7.5k poses added to the queue, but each pose takes between five and ten minutes to be processed and saved. Daz spends most of that time in a non-responsive state. Is this a known issue? Any workarounds? I can't spend the next month just converting poses.
Hi, I spent yesterday trying to convert part of my pose library (productive procrastination, yay), and everything went well until the conversion itself happened. I have a list of about 7.5k poses added to the queue, but each pose takes between five and ten minutes to be processed and saved. Daz spends most of that time in a non-responsive state. Is this a known issue? Any workarounds? I can't spend the next month just converting poses.
Unfortunately, that is a known issue with Daz Studio. When your database gets very full, it can take a long time to save files (the file saving itself is fast - it is updating the database). This is an atomic call to Daz studio, i.e., the script is just calling a Daz Studio function - it cannot make it faster. I haven't figured out how to get around the issue. If you have access to an entirely different machine with an empty database (you haven't been saving there), you could run there and it will go very fast.
Thank you for the prompt response, and for the possible workaround. I have just a couple of further questions: if I do use another machine to do the conversion, how would I then transfer the metadata back to my main computer? The way that the batch converter makes new G9 pose products is great and I would like to keep that benefit.
The other question is more of a tangent: I have experienced a lot of lagging when posing G9, and now I'm wondering if there's anything that a huge library may contribute to that. Would using turbo loader be recommended?
Also, just a side note: there are a few complaints about how the PA ATrillionGames makes posing products that rely on scripts rather than pose files. Batch converter has been perfect to get the actual pose files out of these products.
Comments
As I expected, the log shows Not a Number errors and then crashes:
You need to remove the offending pose from the list (or uncheck it).
I do not understand what this kind of error is. Is there a way for me to correct it so that I would then be able to convert these files? I'm not very computer savvy, but I would still like to know if there's any way to do this.
OK, I did some research on what these NaN Errors are, and I ran a terminal command to correct them. It looks like it worked. I am now converting those files from G8 to G9.
Well, maybe I spoke too soon. DAZStudio crashed again. I'm going to include another log file. So, is there another problem?
There was one crash on 12/14 with NaN:
After that, there were no messages that could tell me what happened. Could it be a disk corruption issue? Have you scanned your disk?
Hi, I spent yesterday trying to convert part of my pose library (productive procrastination, yay), and everything went well until the conversion itself happened. I have a list of about 7.5k poses added to the queue, but each pose takes between five and ten minutes to be processed and saved. Daz spends most of that time in a non-responsive state. Is this a known issue? Any workarounds? I can't spend the next month just converting poses.
Unfortunately, that is a known issue with Daz Studio. When your database gets very full, it can take a long time to save files (the file saving itself is fast - it is updating the database). This is an atomic call to Daz studio, i.e., the script is just calling a Daz Studio function - it cannot make it faster. I haven't figured out how to get around the issue. If you have access to an entirely different machine with an empty database (you haven't been saving there), you could run there and it will go very fast.