Daz Studio 4.21 and Mac OS Sonoma
lloyf
Posts: 30
Like fool installed Sonoma on an M1 Mini. Daz Studio 4.21 now silently crashes on load. From Library/Application\ Support/DAZ\ 3D/Studio4/log.txt:
1st error:
2023-09-26 14:49:09.672 [INFO] :: Creating Authentication Manager...
2023-09-26 14:49:09.676 [INFO] :: Json Parser (1,1): Syntax error - expected '{' or '[
(This may be a long standing error)
2nd error:
Some plugins disabled, not sure if this is an error or not.
3rd error (maybe only a warning):
missing libavutil.56.dylib, libswscale.5.dylib,libavutil.56.dylib, libavcodec.58.dylib, libavformat.58.dylib, libavcodec.58.dylib, ffmpeg_video_decoder.so, libnvindex_application_layer_application_layer.so,libnvindex_plugin_openvdb_integration.so
4th error:
2023-09-26 14:49:21.127 [WARNING] :: QFile::flush: No file engine. Is IODevice open?
2023-09-26 14:49:21.282 [WARNING] :: QLayout: Cannot add null widget to QGridLayout/
2023-09-26 14:49:23.020 [WARNING] :: /src/sdksource/cloud/dzcloudtasknotifier.cpp(178): curl_easy_perform(https://hpclscruffy.daz3d.com/Customer/authenticate) failed: HTTP response code said error
2023-09-26 14:49:23.024 [WARNING] :: /src/sdksource/cloud/dzcloudtasknotifier.cpp(178): Communication to server failed.
Last message in the log file:
2023-09-26 14:49:26.389 [INFO] :: Loading ToolBars: /Users/lloyd/Library/Application Support/DAZ 3D/Studio4/toolbars.dsx
Looks like the next line should be something like "Executing startup script..."
Too old to be this trusting things will just work. :(
Anyone successfully running Studio on Sonoma?
Lloyd
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
Some good news, the latest beta loads. Still checking if there are other than rhe normal beta issues.
Lloyd
Hi
like you i have installed Sonoma on the same machine (mini M1). Daz Studio loads (either normal 4.21.0.5 or beta version) but I can't access to my content librairy which is on an external disk. The directory is still there with all the content but i can't load anything once in Daz Studio. It works yesterday with Ventura and i didn't change anything apart from installing the new OS. Tried to change authorizations for Daz Studio to access to the disks, but hasn't solved the issue. Seems there is a bug somewhere
Vincent
I guess it is back to the crash dump to see why the release version is failing, a plugin or library most likely. Or maybe a permission problem... It seems the more Apple trys to protect us from outselves the less useful the systems become. Early in my career I heard a quote which has stuck with me. Create a fool proof machine and only a fool will want to use it. Paraphrased a bit do to the passage of time. :)
Lloyd
Yikes, just wonder what else Mac OS Sonoma breaks.
Hopefully updates to it will come at some point...
I started to dig into the crash dumps and found something strange. It was not crashing in the same place every time. I restarted the system and tried running Studio with nothing else running. It started successfully. Normally I run Mail, Safari, and DIM. Then start Studio. It crashes every time with this configuration, albeit different threads are crashing. Playing around with various combinations of applications I found that any combination of Mail and DIM running causes Studio to crash on load. The beta version mostly loaded, but would crash if DIM was running (not reliably though).
Given how the crashes are happening on seemingly random threads maybe it is a memory allocation issue. It definitely was not an issue with Ventura. For now care with which applications are running at the same time as Studio is probably wise.
Lloyd
My biggest problems with DAZ (latest Public Beta Release) on Sonoma are:
No textures are loaded when using umlauts (üöä) in directory names
and a few system crashes when using big data files.
My Machine: Mac Mini M1 8GB RAM
Hi,
Just adding to the "dogpile," a little later. (Anecdotal evidence of something between Sonoma OS, M1, and Daz Studio)
Obviously I have not been using Daz Studio recently. Install Manager seems to work okay though.
I was thinking of digging in deep with Daz Studio for some projects and well... not likely now. Once things sort out, I'll be back.
It seems to work ok during first use after a cold boot, but once it crashes, it crashes hard (won't load).
After a cold boot, I have been able to do a quick test render on one occasion, and go as far as starting a brand new scene prior to a crash. Other times, just poking around in the menus on a fresh scene can cause a crash.
Machine: M1 Mac, upgraded to Sonoma immediately as it became available. (I will not do so recklessly in the future).
Daz Studio still qualifying as Intel-based programing for the Apple side, and seeing the posts above, I immediately started chasing the Rosetta rabbit.
Manually installed Rosetta (2) just to make sure it was there. No dice, still crashing.
Note: Time Machine users, do NOT keep using Time Machine under a new OS until you are sure you do not need to fall back to the old OS. Either that, or just swap out drives temporarily. It being directly tied to the OS is a curse in this situation. Rolling back means you have to do a data migration, because Time Machine cannot go back that way once it does the first back-up under the new OS.
Moral of the story: Do not chase after shiny objects the minute you see them, you could end up somewhere you did not want to go.
Take care...
A follow up, a month later I found a solution to my problem, it may help others in this thread.
I took the drastic measure of doing a complete and total re-installation of Daz after completely removing it (including thousands of assets) from my upgraded OS system.
Worked like a charm.
I just completed a lengthy animation render test without a crash under harsh conditions. (I was gaming while the render was humming along in the background)
I grabbed onto the notion that the new OS was not fully respecting the prior installation (read/write access) under the old OS. So that is my running theory.
Hope it helps others!
Take care...
Ok good to know! Thanks.
With Sonoma 14.3 my problems with umlauts (üöä) are fixed!