DAZ Studio 4.6.1.39 Pro crashes on load of 4.5 saved scenes
naql
Posts: 25
So, I downloaded the latest version, OSX 64 bit version, and it crashes on trying to load any of my files previously saved with 4.5.
I looked at the plugins installed, and the only one I see that has an error is libdzpropertyeditor. The only error I see in the log file related to that is this:
Error: dlopen(/Applications/DAZ 3D/DAZStudio4 64-bit/plugins/libdzpropertyeditor.dylib, 2): Symbol not found: __ZN11DzComboEditC1EP7QWidgetb
Referenced from: /Applications/DAZ 3D/DAZStudio4 64-bit/plugins/libdzpropertyeditor.dylib
Expected in: /Applications/DAZ 3D/DAZStudio4 64-bit/DAZStudio.app/Contents/MacOS/../../../Frameworks/libdzcore.dylib
Not that I have any idea whether that is related to the scene loading issue.
Any suggestions? I'm on OSX 10.8.5.
Thanks.
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
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
Do you have a crash log (would be very helpful). And do you have any plugins not from the DAZ site installed, but the crashlog usually will cast light on things,
OK, hitting limits on the post size… I did clip out the other thread states that didn't seem relevant… let me know if you want to see any of the section on "Binary Images" listing dynamic libraries. My macbook has 16g of RAM.
--------------------
Process: DAZStudio [14972]
Path: /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
Identifier: com.DAZ.DAZStudio
Version: 4.6.1.39 (4.6.1.39)
Code Type: X86-64 (Native)
Parent Process: launchd [261]
User ID: 501
Date/Time: 2013-12-16 16:12:20.707 -0600
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Sleep/Wake UUID: 539C1AE8-9600-4457-B77E-F0323B9C350B
Interval Since Last Report: 3047701 sec
Crashes Since Last Report: 77
Per-App Interval Since Last Report: 6062 sec
Per-App Crashes Since Last Report: 10
Anonymous UUID: 337ED84F-4AF8-108D-E1C7-8D60DD746238
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100002000 [ 8K] r-x/rwx SM=COW /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libdzcore.dylib 0x000000010054a38d DzFacetShape::getModifiableGeom(bool, DzVertexMesh*) const + 187
1 libdzcore.dylib 0x00000001005b054e DzFigureFollowHelper::initGenerator() + 158
2 libdzcore.dylib 0x00000001005b0d2a DzFigureFollowHelper::startMorphGeneration(DzMorph*) + 56
3 libdzcore.dylib 0x00000001005b0de8 DzFigureFollowHelper::connectToBaseFigureMorph(DzMorph*) + 128
4 libdzcore.dylib 0x00000001005b0ef9 DzFigureFollowHelper::connectToBaseFigureMorphs() + 123
5 libdzcore.dylib 0x00000001005b0f66 DzFigureFollowHelper::setupMorphFollow() + 34
6 libdzcore.dylib 0x00000001005a9a48 DzFollowHelper::processDelayedFollow() + 40
7 libdzcore.dylib 0x0000000100a0c92e DzSkeleton::postLoadFile(DzInFile const*) + 548
8 libdzcore.dylib 0x00000001006368d2 DzInFile::read(DzBase*, bool) + 1762
9 libdzcore.dylib 0x00000001008fe72a DzScene::readSceneFile(QString const&, DzInFile&, bool) + 202
10 libdzcore.dylib 0x0000000100903def DzScene::loadScene(QString const&, DzScene::DzOpenMethod) + 2439
11 libdzcore.dylib 0x000000010036f567 DzContentMgr::openNativeFile(QString const&, bool) + 1235
12 libdzcore.dylib 0x00000001003710cf DzContentMgr::openFile(QString const&, bool) + 609
13 libdzcore.dylib 0x00000001006dcc25 DzMainWindow::doFileOpen(QWidget*) + 765
14 libdzcore.dylib 0x0000000100176ae2 DzAction::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 184
15 QtCore 0x000000010329fc11 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2001
16 QtGui 0x0000000103532e82 QAction::activate(QAction::ActionEvent) + 194
17 QtGui 0x00000001034ea557 -[QCocoaMenuLoader qtDispatcherToQAction:] + 71
18 com.apple.AppKit 0x00007fff94edf959 -[NSApplication sendAction:to:from:] + 342
19 com.apple.AppKit 0x00007fff9501536c -[NSMenuItem _corePerformAction] + 406
20 com.apple.AppKit 0x00007fff9501505a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
21 com.apple.AppKit 0x00007fff94d0220f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
22 com.apple.AppKit 0x00007fff94d02097 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
23 com.apple.AppKit 0x00007fff9500e165 NSSLMMenuEventHandler + 342
24 com.apple.HIToolbox 0x00007fff9245dd1a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206
25 com.apple.HIToolbox 0x00007fff9245d1e9 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 410
26 com.apple.HIToolbox 0x00007fff92472fc9 SendEventToEventTarget + 40
27 com.apple.HIToolbox 0x00007fff924a9ca9 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 443
28 com.apple.HIToolbox 0x00007fff9244ea21 SendMenuCommandWithContextAndModifiers + 59
29 com.apple.HIToolbox 0x00007fff9244e9d3 SendMenuItemSelectedEvent + 254
30 com.apple.HIToolbox 0x00007fff9244e85f FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 94
31 com.apple.HIToolbox 0x00007fff9242a8bb MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 605
32 com.apple.HIToolbox 0x00007fff92429ec8 _HandleMenuSelection2 + 565
33 com.apple.AppKit 0x00007fff94ecd8c6 _NSHandleCarbonMenuEvent + 245
34 com.apple.AppKit 0x00007fff94defa9f _DPSNextEvent + 2073
35 com.apple.AppKit 0x00007fff94deedf2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
36 com.apple.AppKit 0x00007fff94de61a3 -[NSApplication run] + 517
37 QtGui 0x00000001034f4280 QEventDispatcherMac::processEvents(QFlags) + 840
38 QtCore 0x00000001032878f8 QEventLoop::exec(QFlags) + 394
39 QtCore 0x000000010328ac23 QCoreApplication::exec() + 175
40 libdzcore.dylib 0x00000001001b6884 DzApp::doExec() + 100
41 libdzcore.dylib 0x00000001001c1528 DzApp::run(DzApp::GraphicsMode) + 334
42 com.DAZ.DAZStudio 0x00000001000015f6 main + 496
43 com.DAZ.DAZStudio 0x00000001000013e4 start + 52
[… trimmed out the other threads here… ]
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000123692350 rbx: 0x000000013b00ade0 rcx: 0x0000000111c301c0 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x000000013b00ade0 rbp: 0x00007fff5fbfd940 rsp: 0x00007fff5fbfd8f0
r8: 0x0000000000000003 r9: 0x0000000000000010 r10: 0x0000000000000000 r11: 0x0000000000000003
r12: 0x000000013b000170 r13: 0x000000013b00ade0 r14: 0x0000000123691760 r15: 0x0000000000000000
rip: 0x000000010054a38d rfl: 0x0000000000010246 cr2: 0x0000000000000000
Logical CPU: 2
OK, crashes when parsing morphs. Is there any special character morph you have in those scenes or do every scene crash?
Another question, were those saved as .duf or .daz scene files?
And, here is a listing of the contents of my plugins folder. I looked at each individually in the "Help" menu. libaniMate2.dylib is not authored by DAZ. And the aforementioned libdzpropertyeditor which failed to load (red plug icon) had no author information. What is the correct process to uninstall a plug-in? I moved the libdzpropertyeditor out of that folder to the desktop, which removed it from the "installed plug-ins" list, but had no effect on the issue. I then did the same with the libaniMate2.dylib file, but again, no change.
dzdrawstyles
install_dynamic_clothing_basic.sh
libaniMate2.dylib
libdazscriptide.dylib
libdzalignace.dylib
libdzassetiofilters.dylib
libdzautofit.dylib
libdzautoriggerbasic.dylib
libdzautoshaderbakeractions.dylib
libdzbrycebridge.dylib
libdzbvh.dylib
libdzcolladax.dylib
libdzcomponents.dylib
libdzcontentdbeditor.dylib
libdzcontentlibrarypane.dylib
libdzcr2exporter.dylib
libdzcustomizedlg.dylib
libdzdelightrenderer.dylib
libdzdformeditor.dylib
libdzeasyloader.dylib
libdzexpexporter.dylib
libdzfbxexporter.dylib
libdzfbximporter.dylib
libdzfiguresetup.dylib
libdzgoz.dylib
libdzhexagonbridge.dylib
libdzimageio.dylib
libdzjointeditor.dylib
libdzlayerededitor.dylib
libdzlayerfilter.dylib
libdzmacvideo.dylib
libdzmanualshaderbaker.dylib
libdzmaptransfer.dylib
libdzmorphfollower.dylib
libdzmorphloader.dylib
libdzmorphloaderpro.dylib
libdzobjexporter.dylib
libdzoptitexclothbasic.dylib
libdzpolygongroupeditortool.dylib
libdzprimitives.dylib
libdzpropertyeditor.dylib
libdzpropertyhierarchyeditor.dylib
libdzpuppeteer.dylib
libdzpz3importer.dylib
libdzrenderedit.dylib
libdzrenderlibrary.dylib
libdzrslshadercompiler.dylib
libdzsavefilters.dylib
libdzscriptedrenderer.dylib
libdzscriptedsteps.dylib
libdzshaderbaker.dylib
libdzshaderbuilder.dylib
libdzshadereditor.dylib
libdzshadermixerbase.dylib
libdzshadermixergui.dylib
libdzsmartcontentpane.dylib
libdzspotrendertool.dylib
libdztextureatlas.dylib
libdztransferutility.dylib
libdzu3dexporter.dylib
libdzweightmapbrush.dylib
PowerPose
SDK_SceneInfoPane.dylib
uninstall_dynamic_clothing_basic.sh
They are saved as .DAZ files. Can't really say about the morphs. It's possible. How would I go about identifying the problem morph and/or snipping it out?
And, wow, thanks for the super-fast reply. I appreciate your help very much.
Using DIM. That said, some plugins are included in DAZ Studio itself, and won't be listed separately.
DAZ format scene files, that could be the cause. If you create a new scene, save it (.DUF format), and reopen the new scene file, does it still crash?
No, last night I loaded in a Genesis 2 figure, added a couple of props, saved it and was able to load it, although I did get "Duplicate ID warnings". It was in DUF format although I didn't explicitly select that. I suppose it's the new default?
I found one existing DAZ file (temple scene with no characters) that I was able to load just fine with no warnings.
And then, I have another .DUF file (med lab with "Riley" Genesis 1 character) that I was able to load up, again with duplicate ID warnings, but otherwise seemed fine.
So, firstly, I dragged those two plugin files back whence they came to the plugins folder. The libdzpropertyeditor.dylib file troubles me because it has a different date (Oct 9, 2012) than all the rest.
Also, I started up DIM and noted that I had a crapload of updates to install that I hadn't noticed last night. Should I go ahead and load those, or is there a chance that I might compound my problems?
I would install the updates, as they tend to fix issues.
Totte (or any other Mac user) will have to check their plugins folder for the libdzpropertyeditor.dylib file, as I don't have it on mine (Windows).
.duf is the new default format, replacing the older .daz format.
I have been told that the duplicate IDs message is harmless. There is a way to get rid of it (search forums or ask), but since it is harmess, I have just been ignoring it.
Thanks for that info…
So, I installed all of the updates. Then, I restarted my computer, did a repair of disk permissions. Uninstalled DAZ Studio and then reinstalled it, all via the install manager.
No joy. On the same files (which is almost all of them), I get exactly the same crash log and it stops in the same place.
So, I'd rather not completely lose all of these. What are some other options open to me? Can/should I downgrade back to 4.5, see if I can open them and then save or export them in a different format?
I found another thread which sounds very similar and my impression is that I'm screwed. I've submitted a bug report with the crash log and the file that caused it. We'll see what happens. It's very frustrating… take a break from this stuff for a few months, come back and, as usual, I feel like I'm starting over from square 1; can't remember how to do things, my content is obsolescent or broken, and my library is a tangled mess.
I appreciate all the help.
To conclude this, the reply from customer "support" was: the .daz format is bad, had many problems so they've dropped it. Studio didn't crash for them on loading the file I sent, even though they didn't have the content files and could not view anything, therefore problem resolved. No information on downgrading, no alternative solutions to salvage anything.
So, I'm left with about a hundred files or so which are just toast.
You say that you've been away for a while (same here, btw) so these scenes are probably using Victoria 4, right?
I'm wondering if since it is bombing on the morphs if the issue isn't actually in the scene file, but in Victoria herself. As I recall, back in the early days of Victoria 4, we had these updator / initializer scripts we had to run every time we installed new morph packages, etc. I wonder if you could get the install files for Victoria 4 (and her morph packs) again and re-install, re-initialize her and see if that cleans up the issue for you?
No, they were "Genesis" figures and were created earlier this year. I wondered if it was because of some weird prop or sky dome I had in there, but it occurs on other files that I know were simpler tests. Strangely enough, I do have one .daz file that I *can* open, although it does not have any character objects (and probably no morphs) in it.
I think at this point, I'm going to just uninstall everything; wipe my content db, reinstall everything from scratch. Once I get everything squared away, I'll try again.
thx
This is a practice I started when DAZ Studio started all the Updates to new versions. So far each new version has been able to load scene files from the last version but maybe not from earlier versions, so Each update I load my scene files and Scene subsets and any Custom files for that matter, and re-save them in the new version. That keeps them up to date on my PC.