Loading...
> >

DAZ Studio Crashing with Mac Updated to macOS Ventura

FauvistFauvist Posts: 2,219
in The Commons

This Mac update to it's operating system came out 3 years ago.  I just updated to it.  Now DAZ Studio crashes every time I open it.  What's going on?

Thanks!

Comments

  • nemesis10nemesis10 Posts: 3,772

    May I ask a few questions?  First, what order did you update your system: OSX and then Daz Studio or Daz Studio then OS X?  I highly recommend updated the OS first then installing the latest version of your software which has the latest patches. The second suggestion is to add the lastest Beta; I currently run Tahoe and am using it as my primary renderer.

  • FauvistFauvist Posts: 2,219

    nemesis10 said:

    May I ask a few questions?  First, what order did you update your system: OSX and then Daz Studio or Daz Studio then OS X?  I highly recommend updated the OS first then installing the latest version of your software which has the latest patches. The second suggestion is to add the lastest Beta; I currently run Tahoe and am using it as my primary renderer.

    I didn't touch ANY of the files or data on the computer, ALL I did was update the Mac operating system.  The computer updated, turned off, turned back on, and I opened DAZ Studio and it crashed after about a minute. 

  • FauvistFauvist Posts: 2,219

    nemesis10 said:

    May I ask a few questions?  First, what order did you update your system: OSX and then Daz Studio or Daz Studio then OS X?  I highly recommend updated the OS first then installing the latest version of your software which has the latest patches. The second suggestion is to add the lastest Beta; I currently run Tahoe and am using it as my primary renderer.

    Computers have been around FOREVER by now.  This is the kind of thing that used to happen in the 1900s.  It's absurd it should still happen.  Apple is one of the biggest companies in the world.  It's infuriating. 

  • nemesis10nemesis10 Posts: 3,772

    I am still a little confused which version of Daz studio you have?  Generally, when you update your computer or phone for that matter,  you get updates for your software also so that the software and OS play nicely.  So if you are using an antiquated version of Daz Studio then it is expected to be unstable in a new OS.  I agree that Daz studio is probably the culprit; if you are dilligent in staying up to date, I would suggest just reinstalling Daz Studio and CMS in case any of those are no longer compatible. Likewise, if something is corrupted in the update, it might solve that problem. Computers are all about updates and security as they continue to evolve. Nonetheless, I currently run the current standard, the current Beta, and the special 2025 Beta simultaneously on my M3 mac with stability so I think your problem is solvable.

  • wsterdanwsterdan Posts: 3,054

    Fauvist said:

    nemesis10 said:

    May I ask a few questions?  First, what order did you update your system: OSX and then Daz Studio or Daz Studio then OS X?  I highly recommend updated the OS first then installing the latest version of your software which has the latest patches. The second suggestion is to add the lastest Beta; I currently run Tahoe and am using it as my primary renderer.

    Computers have been around FOREVER by now.  This is the kind of thing that used to happen in the 1900s.  It's absurd it should still happen.  Apple is one of the biggest companies in the world.  It's infuriating. 

    It still happens, as operating systems and the software running on them are always upgrading and sometimes not quite working together correctly all the time, that's why there's constant updates to both.

    I know it sounds lame but as simple as it sounds, I'd shut the computer down and after it's been off for a minute or so, restart the computer and once it's up and running try DAZ Studio again and if it crashes the first time, try DAZ Studio again. I have had it crash after an upgrade on the first try but have it work fine thereafter.

    I did mention it was a lame suggestion and if you've already done all that, I'm not sure what more I can suggest without more information.

    Good luck! 

  • FauvistFauvist Posts: 2,219

    nemesis10 said:

    I am still a little confused which version of Daz studio you have?  Generally, when you update your computer or phone for that matter,  you get updates for your software also so that the software and OS play nicely.  So if you are using an antiquated version of Daz Studio then it is expected to be unstable in a new OS.  I agree that Daz studio is probably the culprit; if you are dilligent in staying up to date, I would suggest just reinstalling Daz Studio and CMS in case any of those are no longer compatible. Likewise, if something is corrupted in the update, it might solve that problem. Computers are all about updates and security as they continue to evolve. Nonetheless, I currently run the current standard, the current Beta, and the special 2025 Beta simultaneously on my M3 mac with stability so I think your problem is solvable.

    Thanks. I'll reinstall DAZ Studio - whatever the newest version is.  Can I keep the old version of DAZ Studio somehow? 

  • nemesis10nemesis10 Posts: 3,772

    Thanks. I'll reinstall DAZ Studio - whatever the newest version is.  Can I keep the old version of DAZ Studio somehow? 

    Okay, some secret knowledge: since you are on an Mac,  

    Remember Finder is the Desktop

    1. Go to Finder, Go to the Application folder and select Daz Studio, "Duplicate" it (go to the Main menu on top Finder> File > Duplicate), and drag the duplicate to the desktop into a new folder
    2. Hold Option key down, go to Finder, go to Go in the Main Menu Finder> Library> Application Support> Daz 3d (this Library is the library for your specific user account and not the whole computer library 
    3. Duplicate that Daz 3d folder and drag that duplicate to that desktop folder I told you to create.
    4. Name that folder, "Old Daz Studio", compress it (Finder> File>Compress), move the zip to some place safe like a folder in your Documents folder for example or an external drive...
    5. Install your updated Daz Studio and (maybe CMS if it says so), go into DIM and get caught up on your updates (a few files have updates to work better) and render as always.
    6. I can make a diagram if you like

    If you don't like it, revert by replacing Daz Studio with your duplicate Daz Studio in the Application Folder and the Daz 3D folder in the Library> Application Support folder, open Daz Studio again and you are back where you started

    Now my question, why are you still using such an old version of Daz Studio?  The reason I asked was I used to manage a group of mac users (25 mac's) and people were always lax in updating even though it would make their lives easier.  They were never clear why they didn't keep up with software maintenance so I had to be very aggressive and assertive that they used old software 

  • TotteTotte Posts: 14,688

    Hi,

    First, a crashlog or two would be very good to see where it crashes. Secondly (no, I didn't read through the whole thread), what hardware are you using and exactly what are you doing when it crashes.

    I run DS on macOS and have since I started back in 2011 and been through a lot of macOS, hardware and DS updates over the years. I've seen quite a few crashes ( self inflicted during development of plugins and scripts) and other. What I can say is that Studio 4 on Mx hardware can when running scripts be stupid and crash, and then next time it works perfectly. The crashlogs states that they are "not correct", which means the callstack has been corrupted. That is usually due to the Rosetta2 X86_64 emulation driving of the road as it's is sensitive to the way Qt scripts works.

    If you dont know how to post crsshlog here give me a shout and I tell you. Other things that can crash are plugin collisions, but that can be seen in the cashlogs too. It's important if you run amcOS 13 or higher to use DS 4.24.0.3 Release as it fixes a bug in Qt menu handling with macOS 13+.

     

  • FauvistFauvist Posts: 2,219

    Totte said:

    Hi,

    First, a crashlog or two would be very good to see where it crashes. Secondly (no, I didn't read through the whole thread), what hardware are you using and exactly what are you doing when it crashes.

    I run DS on macOS and have since I started back in 2011 and been through a lot of macOS, hardware and DS updates over the years. I've seen quite a few crashes ( self inflicted during development of plugins and scripts) and other. What I can say is that Studio 4 on Mx hardware can when running scripts be stupid and crash, and then next time it works perfectly. The crashlogs states that they are "not correct", which means the callstack has been corrupted. That is usually due to the Rosetta2 X86_64 emulation driving of the road as it's is sensitive to the way Qt scripts works.

    If you dont know how to post crsshlog here give me a shout and I tell you. Other things that can crash are plugin collisions, but that can be seen in the cashlogs too. It's important if you run amcOS 13 or higher to use DS 4.24.0.3 Release as it fixes a bug in Qt menu handling with macOS 13+.

     

    I've been using Macs since near the begining of Apple. This Macbook Pro I'm on now has NEVER crashed before.  I'm an artist, I'm not a computer technician, I don't know what ANY of this stuff on the crash log means.  I've never looked at a crash log before.  So I copied the crash report from the crash log and this DAZ forum gave me this message: "Body is 290068 characters too long."

    So the solution to the solution is burried in 300,000 characters.

    Thanks

     

  • FauvistFauvist Posts: 2,219
    edited October 18
     

    Now my question, why are you still using such an old version of Daz Studio?  The reason I asked was I used to manage a group of mac users (25 mac's) and people were always lax in updating even though it would make their lives easier.  They were never clear why they didn't keep up with software maintenance so I had to be very aggressive and assertive that they used old software 

    I'm using the old version of DAZ Studio because updating it made some of the DAZ products not work - products I relied on (one in particular, which allowed me to use old characters on newer figures - like use Michael 4 and Michael 5 characters on Genesis 2, I can't even remembrer the name of the product and I don't think it's in the store anymore because the inventor of it died)  When I asked about it in the Forum - Richard told me to use the old version of Studio, or use some Beta version of Studio.  So I chose to use the old version.  

    Every time I update the Mac OS or update a version of software for anything, it causes SOMETHING not to work.

    AI exists now.  Why can't these problems fix themselves?  You can make a feature film and compose and record an orchestra performing an orgiinal symphony with AI,  but you can't get your existing software to work.

    The 2nd (biggest reason) I didn't update the DAZ Studio software is that I expect AI to make DAZ Studio obsolete by now and I wouldn't be using it anymore.  Is that clear enough?  AI is replacing old software.

    EDIT:  I'm sorry I sound so harsh, I don't mean to be disrespectful, and I appreciate your help - but I broke my foot and 3 of my toes and spent 11 hours in the Emergency ward yesterday and now, not only can't I walk, I'm in pain, that won't allow me to sleep.

    Post edited by Fauvist on
  • TotteTotte Posts: 14,688

    Fauvist said:

    Totte said:

    Hi,

    First, a crashlog or two would be very good to see where it crashes. Secondly (no, I didn't read through the whole thread), what hardware are you using and exactly what are you doing when it crashes.

    I run DS on macOS and have since I started back in 2011 and been through a lot of macOS, hardware and DS updates over the years. I've seen quite a few crashes ( self inflicted during development of plugins and scripts) and other. What I can say is that Studio 4 on Mx hardware can when running scripts be stupid and crash, and then next time it works perfectly. The crashlogs states that they are "not correct", which means the callstack has been corrupted. That is usually due to the Rosetta2 X86_64 emulation driving of the road as it's is sensitive to the way Qt scripts works.

    If you dont know how to post crsshlog here give me a shout and I tell you. Other things that can crash are plugin collisions, but that can be seen in the cashlogs too. It's important if you run amcOS 13 or higher to use DS 4.24.0.3 Release as it fixes a bug in Qt menu handling with macOS 13+.

     

    I've been using Macs since near the begining of Apple. This Macbook Pro I'm on now has NEVER crashed before.  I'm an artist, I'm not a computer technician, I don't know what ANY of this stuff on the crash log means.  I've never looked at a crash log before.  So I copied the crash report from the crash log and this DAZ forum gave me this message: "Body is 290068 characters too long."

    So the solution to the solution is burried in 300,000 characters.

    Thanks

     

    Print to pdf and upload the pdf. Or zip the crashlog file and upload the zip file  

Sign In or Register to comment.