Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I'm currently running DS 4.12 on my iMac (2019 edition) with MacOS 10.15.4 Catalina with very few problems. The only problem I have encounted is some keyboard shortcuts causes daz to crash (DAZ3D are aware of this)
Zai, thanks very much for this info. It gives me hope that this will work out with the new iMac and 4.12. Heck, if the stars all align just right, the Daz tech people may even be able to isolate the problem with DS now on this current computer (although they weren't very hopeful in the initial message to me), and I'll be able to set up aniomation scenes on it while an animation is rendering on the new one.
This is great to hear, @Platnumk. Thanks very much for the info. Yes, I saw in some thread a discussion about crash on using the keyboard shortcut to save, and that a ticket had been submitted. Maybe by the time the new iMac rolls up the driveway, they will have resolved that.
Hrm..ok that's different for me. I have no issues using shortcuts to render or save. Were there any other shortcuts that were causing issues?
Also, just for info, I am running multiple runtimes on multiple external drives with no issues.
The saving issue is covered in this thread: Mac constant crashes since update
The second message there, from Richard Haseltine, says it's a known issue (which already may have been resolved as far as I know, which isn't very far).
Don't know which other shortcuts may have been involved because I don't yet have any release version of 4.12.
Oh, sorry, but so many people are posting the "magic fix" for the postgresql cms connection without any qualifications. The magic fix might help in certain circumstances, or in certain versions of OS X. OK, beyond that, mavante's troubles are likely due to an old version of DAZ Studio and an old Mac. Maybe I missed the clarification on those issues. I do wish mavante well. Hopefully one day postgresql cms connection will work for us all.
The problem with "Error connection to postgres CMS" can be figured out in one of these steps:
(1) If the ~/Library/Application Support/DAZ 3D/cms/ContentCluster/ is an empty directory, the permissions on that folder (and sometimes the inherited permissions on ../cms folder is wrong, which prevents postgres to put database files there. Fix permissions by setting "you" as owner of the directory (which is what my cmsfixer does), run DS and DS will the create the CMS database files through postgres and yu are happy.
(2) If there are files there, there is a postgres logfile there, it will tell you about problems, often it cant start the databases because permissions allows others than owner to access the files, which postgres dislikes from a security reason. This happens if you "repair permissions under 10.15.3 or higher" or "Install 10.15.3 or higher" as Apple has decided that some OS processes, like the mds (file system indexer) and the iCloud backup copy process should have access to all files under ~/Library, but postgres don't want that as it violates the security. One solution could be to move the cms cluster to a directory where Apple won't go in and change permissions.
(3) It can be a database corruption, firewall blocking the port or something else, but so far 90% of the cases I've solved has been one of the two above.
Thank you my Bald Wizard Hero! That's is an excellent breakdown of why :)
@Totte: I'm wondering if one or more of the scenarios you've laid out above about the postgre issues might be accounting for the different (but related?) issues I'm having with Daz 4.11 instantly crashing when I try to load anything into a scane, or open a saved scene.
For your (1) above, ~/Library/Application Support/DAZ 3D/cms/ContentCluster/ is not an empty directory.
As for (2) above, the "dblog.txt" file only goes back to approximately when the weirdnesses started with 4.11, and it has this line repeated throughout it several times (I've changed my user name to "MyUserName"):
It also has this statement quite a few times:
So here are all the current permissions settings for the hierarchy of my Home folder (~) down to that ContentCluster folder, in descending order:
~ permissions
xxxxxxxxxxx(Me).....Read & Write
staff...............Read only
everyone............Read only
~/Library permissions
xxxxxxxxxxx(Me).....Read & Write
staff...............Read & Write
everyone............Read & Write
~/Library/Application Support permissions
_spotlight..........Read only
xxxxxxxxxxx(Me).....Read & Write
staff...............Read only
everyone............Read only
~/Library/Application Support/DAZ 3D permissions
_spotlight..........Read only
xxxxxxxxxxx(Me).....Read & Write
staff...............Read only
everyone............Read only
~/Library/Application Support/DAZ 3D/ContentCluster permissions
_spotlight..........Read only
xxxxxxxxxxx(Me).....Read & Write
everyone............No Access
It seems weird to me that my ~/Library folder should have Read & Write permissions for the whole shootin' match, but whadda I know?
If you see anything that might send me down the right path to a fix, I would be extremely grateful. Waiting for tech help is like waiting for Godot.
That is (3) - sounds like database corruption, which can cause all kinds of misery
Thanks very much. Maybe this is a lighted path to recovery.
I did "Reset Database" and then "Reimport metadata" from the DB Maintenance panel when the crashing started, and the crashing still happened after that, so the "Reset database" function didn't fix whatever corruption is there. Any suggestions for how to resolve it—and somehow stay with 4.11, if possible?
Can you please post a couple of crashlogs? You find them in console.app (in /Applications/Utilities). I'm one of those who actually can read a crashlog and get something useful from it, lol.
I think you can print the crashlog to pdf and attach the pdf with your post, to get all of the crashlog.
You'll have to tell me where in Console to find what you want, and what you mean by "a couple." There are quite a few categories, and within some of them there are very long lists of files. See attached. (I'm not attaching it because I think you don't know what's in Console, but because I don't know what's in Console where.)
And about those lists of files in various categories: The names are truncated and inscrutable, and I can't resize the column the names are in. There also is no "Date" column, so I have no idea when each file was created.
Sorry. I really don't want to waste your time, but I'm likely to waste far more of it if I don't ask. Also, depending on what is in those files, I may want to send it to you privately, if you're amenable.
Under "User Reports"
Thanks. So with Console open to "User Reports," and scrolled to the section of files with names beginning "DAZStudio," I launched DS and crashed it intentionally by attempting to create a plane primitive—which I knew would crash it. I wasn't disappointed. I watched Console create the report, and found the date and time in the top section of the report, so we both can know it represents the current state of things. It is attached as a text file titled "2020-05-17 Console Crash Log DS.txt". I also created a text file, attached, of the next most recent DS crash, which was on 12 May. It is titled "2020-05-12 Console Crash Log DS.txt".
Let me know if you need anything else.
@mavante: The crashes might suggest that you should take a löook under Prefecences and Interface and check the Display Optimization. Are you using OpenGL or Iray Viewport?
The crashes happens when a button is clicked (Render button?) and when DZ is working with meshes. Both crashes are very similar.
It was set to "Best." I had been using "Better" for quite a long time, but sometime in the last month or so, I read or saw a tutorial that said it should be set to "Best" for better viewport-update speed when in Iray mode. (I don't think that was date-coincident with when the crashes started, but possible.) I just opened DS, changed it back to "Better," applied and accepted, then quit DS, and then restarted it. I tried to create a Plane primitive. Pause, instant disappear-o. Crash and burn.
It isn't open right now, but if I recall correctly, I may have changed that pixelization control option in that part of the Preferences, at the same time I changed to "Best." It's where you can set it to fractions, such as 1/8, 1/16, etc. Could that be it?
If by "OpenGL" in the main viewport you mean "Texture Shaded," I commonly switch back and forth between them (and others), and DS opens with whatever last one I was using. Currently, every time I open DS it is in Texture Shaded. It was when it just crashed. Again.
I hadn't clicked on the Render button or any other button, other than the "Accept" button (I think that's what it says) on the Primitives requester that pops up. I've been leaving all the defaults, Plane, when testing this crashing business, although at various times I've also tried a cube. Instant crash.
And so I am clear, the first time it instantly crashed was when I tried to load a scene I had been working on. That happened like twice in a row, so I decided to try to load a product from Smart Content into a blank scene. Instant crash when I double-clicked on the product to load it. That happened several times in a row. That's when I decided to go as "primitive" as possible (yes, pun intended), and do nothing but try to create a primitive in a new scene.
And here we are.
Should I upload the Crash Log for the first instant crash I can find, which I think will be when I tried to load a scene?
This is what my permissions looks like
~/Library
xxxxxxxxxxxxxxx (Me)....... Read & Write
Everyone........ No Access
~/Library/Application Support
xxxxxxxxxxxxxxx (Me)....... Read & Wright
Everyone............................ No Access
~/Library/Application Support/DAZ 3D
xxxxxxxxxxxxxxxx (Me)....... Read & Wright
staff...................................... Read Only
Everyone.............................. Read Only
~/Library/Application Support/DAZ 3D/cms
xxxxxxxxxxxxxxxx (Me)....... Read & Wright
staff...................................... Read Only
Everyone.............................. Read Only
~/Library/Application Support/DAZ 3D/cms/ContentCluster
xxxxxxxxxxxxxxx (Me)....... Read & Wright
Everyone............................ No Access
I'm not sure where the user _spotlight has come from but it shouldn't be there as far as I know
OK, so it crashes when you create a primivite. Does it crash when you add content to the scene.
Try this:
in DS Under Help->Troubleshooting...->View Log File.. you can get the DS logifle, upload that here too. or even better, locate it on disk ~/Library/Application Support/DAZ 3D/Studio 64/ -> log.txt. delete the logfile, start DS, when it has crashed, upload logfile here. I suspect there is something else involved that is causing your 4.11 to crash, something getting overlooked. Finding crashes is often like an Agatha Christie murder mystery, finding the clues...
Totte, There is no Content Cluster folder on my Mac (see screenshot). The DAZ folder gives permission to nobody & everyone. Those permissions are related to Dropbox. I rely on Dropbox. I'm at a total loss here.
Where does Studio say the CMS is supposed to be located? (Yoiu find that under Preferences -> CMS Settings.
If it points to ~/Library/Application Support/DAZ 3D/cms (where ~is your hiome catalogue), set you as owner of cms, then manually create ContentCluster folder inside cms, then start DS.
Mine is set like this:
Totte, that didn't work either. I noticed that my setting has a different port number than yours... is that relevant at all?!
Depends only on what port postgres starts at. Did you get any files in ComntentCluster after you created it and ran DS?
No. I didn't get any files. I must be nuts. I decided to eliminate my entire install setup and start over. This will be my last attempt. I'm all the more convinced to buy a new PC for DAZ Studio. I'm hoping to have the money by the end of the year.
It works - just need to get there...
Which version of DIM are you using? Which OS X version are ytou running.
Did you set yourself as owner of the ContentCluster folder?
The DIM version always gets updated if necessary...it's part of the process. I'm running macOS Catalina v 10.15.4
This is what gets me. I spent several hundred dollars buying content over the past week. I haven't been able to use it. I can't find anything, due to the way DAZ splatters content all over the place. I can't get Smart Content to work due to the problems with postgres. I want to have artistic fun, not spend all my time troubleshooting.
Yes. As I've said a couple of times upthread:
My computer is completely tied up with an unrelated job right now, but as soon as I deliver that later today and it is free I will try what you ask. Maybe I will do it three different times, with each of the actions numbered above, moving the log.txt file out into a separate folder somewhere each time, Hercule.
That way I guess (hope?) you'll be able to see if there is anything common to all three actions. Thank you very much for all your patient help and interest.
Installation of content is controlled by DIM (if you install with DIM), and it installs content where you tells it to.
The 10.15.3+ woes with postgres is sadly Apples repair permissions that causes it, and the solution has been to ensure that the cms folder is writable by the user, you, and that the ContentCluster folder is writable by you too, and not acceessible by anyone else.
This relly sounds like a sever issue with either graphics card, graphics drivers or something similar. Can you screenshot the Help->Troubleshooting -> About Videocard dialog?