Greetings,
I resolved to convert all my old .daz files to .duf files, and hopefully Iray-ify them, and stuff like that, and see if any of the old scenes had redeemable qualities that I could use to kick-start my recently-dead creativity.
Unfortunately...
DAZ Studio 4.9 (4.9.4.122) doesn't load my .daz files containing characters anymore. I'm not sure exactly what the limitation is; the one .daz file I have with just a book in it loads okay. But nothing else that I've tried loads.
On the Mac it crashes. Hard. Program disappears and an Apple crash window shows up. Something about...
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
.
.
.
0 libdzcore.dylib 0x00000001007e5b8b DzFaceVertexIslandCategorizer::Data::buildCategorizedIslands(DzFacetMesh const*, DzFaceVertexIslandBuilder const&) + 11109
1 libdzcore.dylib 0x00000001007b9e62 DzExpression::Data::~Data() + 104718
On Windows, it just gives a dialog error, 'Error opening file' with the text 'An error occurred while reading the file, see the log file for more details.'
The log file has...a lot of things going on in it. Here's a snippet.
2017-09-17 21:45:17.520 Opening file Lost in a Good Book.daz...
2017-09-17 21:45:21.946 Error setting pointers while reading file E:/Dropbox/Refried Scenes/Old/Scenes/Lost in a Good Book.daz : C Exception: Memory Access Violation - Attempted to read memory at address 0x00000000
2017-09-17 21:45:21.950 File read time: 0 min 4.3 sec.
2017-09-17 21:45:21.959 Building Scene...
2017-09-17 21:45:22.193 WARNING: Object::disconnect: No such signal QObject::currentValueChanged() in properties\controllers\dzerclink.cpp:1487
2017-09-17 21:45:22.193 WARNING: Object::disconnect: (sender name: 'ZRotate')
2017-09-17 21:45:22.193 WARNING: Object::disconnect: No such signal QObject::currentValueChanged() in properties\controllers\dzerclink.cpp:1487
2017-09-17 21:45:22.193 WARNING: Object::disconnect: (sender name: 'ZRotate')
...
The last lines repeat a bunch, with a WHOLE lot of different values for the 'sender name'. Obviously I think the memory access violation is a bit more important...
On a scale of 1 (Just Do This One Weird Trick & You'll Be Fine!) to 10 (Bwahahaha, you're never opening those files again!), just how b0rk'd am I?
-- Morgan