Export errors
mogaremolby
Posts: 86
Good evening every may I request some asssistence. I have been exporting daz models for a project I'm doing in FBX format. Occasly I be getting some Export errors. Is there a way I can solved this problem.
Daz Fbx exsport Error.png
1360 x 768 - 535K
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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Good evening every may I request some asssistence. I have been exporting daz models for a project I'm doing in FBX format. Occasly I be getting some Export errors. Is there a way I can solved this problem.
Does the log (Help>Troubleshooting>View Log) give any more information?
Merged duplicate threads. Please don't post multiple threads on the same issue.
How do I get access to the log? This is new to me. Oh and sorry about Multiple threads.
No wait I see the log file. Can I sent it to you tonight around 8pm Mr.Richard? I'm at work right now. The computer I'm exporting is at my home.
Next time you get the error go straight to the log and scroll to the very end - any further and better particulars should be there, if there is anything copy-and-paste that section here.
Ok here the logs and info.
It's in the middle of running TDLMake, creating the Mip-mapped versions of the textures. It might be worth waiting until there's no disc activity (or just for a few minutes after applying the last texture set) to give that process time to complete - if that then helps I would make it the subject of a bug report. (Switching the render Engine to Iray would stop DS from running TDLMake at all, as another approach.)
One of the reason for this type of error is something is trying to call/work with data that doesn't exist...yet.
So it could happen if the TDLMake process is taking to long. What Richard is suggesting is a way to make sure TDLMake will complete as quickly as possible.
Another cause is running out/running short on memory, so something that should have been in memory isn't (like it was dumped to 'virtual' memory on the hard drive) and it 'got lost in the shuffle'. So if you are on a low memory (8 GB or less) system, make sure you have the most available you can for studio...no extras running while trying to do the export, etc (in addition to what Richard suggested). When converting things memory usage can spike to double or more of the amount the scene would normally consume.
A third cause is that it was written to a location (or not written) that doesn't have adequate/proper read/write permissions. (in this case, it's not very likely, because you are writing to your desktop and user profile).