The New Mac FAQ

1234568»

Comments

  • nemesis10nemesis10 Posts: 3,922
    edited April 13

    inquire said:

    OK, so they run programs, such as stable diffusion 1111, on their own computer. Is that it?

    The canned answer:
     

    Running AI locally means operating models directly on your hardware (PC/laptop) rather than in the cloud. The primary benefits are total data privacy and security, offline accessibility without internet, zero API fees or subscription costs, and reduced latency for faster responses, making it ideal for confidential, personal, or specialized tasks.

    Here is a breakdown of why you should run AI locally:

    • Speed & Reduced Latency: For many applications, local execution is faster because it eliminates network latency.
    • Customization & Control: You can freely customize, fine-tune, or change models without being locked into the constraints of commercial AI providers.
    • Privacy & Security: Sensitive, personal, or proprietary data never leaves your computer, eliminating risks associated with sharing data with third-party servers.
    • Offline Functionality: Local AI functions without an internet connection, removing dependency on cloud availability.

    Zero Costs/Subscription Fees:

     Once you own the hardware, you can run as many inferences as you want for free (electricity cost only), avoiding paying for API calls.

    A more practical one is some people do AI development and being able to do it in your own home is easier than renting out a server.

    Post edited by nemesis10 on
  • ChakradudeChakradude Posts: 294

     

    Totte said:

    And for crashing scripts, as I said before, that is most of the time ( what I have analyzed so far ), a problem with Rosetta2 emulator emulating a JS engine running JS with Qt signal and slots calls,
    Even loading an M4 ( causing the PowerLoader to activate) cashes, if Rosetta2 is unstable.
    Usually I run a script I know crashes with an unstable Rosetta2 as soon as I've started DS, then when it doesnt crash, after a few startups, I have a stable DS that runs.

     

     

     Hi Totte, I have a question for  relavent to this conversation. We may have discussed it before but I have built my script library and used your incredible manager script to back up all the scripts I just installed like I used to do on my PC. Then the computer crashed as expected after closing the app but even after it stops crashing I do not see the scripts because as you can see in my post they no longer seem to be mapped to the scripting folder or any of the subfolders I used. is there a way to remap them or are mac users consigned to hunting down every script as needed?

    Running on an M4 macbook

    Screenshot 2026-04-21 at 6.58.11 PM.png
    1832 x 1264 - 1M
  • ChakradudeChakradude Posts: 294

    Totte, also I am starting to experiment with vibe coding with some success. You mentioned elsewhere you are making scripts already for studio 2026 but waiting for building plugins. Any tips on where to start with coding for the next generation daz studio? Are the tutorials on the Daz store relevent still? I studied interface design and have an avid interest but not so much coding experience. Even being able to make a few crucial scripts for my own use would be such a relief.

  • TotteTotte Posts: 14,991

    Chakradude said:

     

    Totte said:

    And for crashing scripts, as I said before, that is most of the time ( what I have analyzed so far ), a problem with Rosetta2 emulator emulating a JS engine running JS with Qt signal and slots calls,
    Even loading an M4 ( causing the PowerLoader to activate) cashes, if Rosetta2 is unstable.
    Usually I run a script I know crashes with an unstable Rosetta2 as soon as I've started DS, then when it doesnt crash, after a few startups, I have a stable DS that runs.

     

     

     Hi Totte, I have a question for  relavent to this conversation. We may have discussed it before but I have built my script library and used your incredible manager script to back up all the scripts I just installed like I used to do on my PC. Then the computer crashed as expected after closing the app but even after it stops crashing I do not see the scripts because as you can see in my post they no longer seem to be mapped to the scripting folder or any of the subfolders I used. is there a way to remap them or are mac users consigned to hunting down every script as needed?

    Running on an M4 macbook

    Did you try to restore from Backup? It should work, but what can cause issues is for example if the content is on an extefnal drive ( recommended ), but something caused the drive to dismount, and when it remounts you will see multiple entries in the /Volumes folder 
    terminal ls /Volumnes, like External Drive then External Drive 1
    Then you need to reboot the machine so it remounts as External Drive ( as the External Drive  will point to an empty folder, and External Drive.1 now points to the correct one ).

    This is the first step to check.
     

  • TotteTotte Posts: 14,991

    Chakradude said:

    Totte, also I am starting to experiment with vibe coding with some success. You mentioned elsewhere you are making scripts already for studio 2026 but waiting for building plugins. Any tips on where to start with coding for the next generation daz studio? Are the tutorials on the Daz store relevent still? I studied interface design and have an avid interest but not so much coding experience. Even being able to make a few crucial scripts for my own use would be such a relief.

    this is the place: https://docs.daz3d.com/public/software/dazstudio/4/referenceguide/scripting/start 

    Script APIs are much similar between versions, so just look at the samples and go from there, the first 3 scripts are the worst, then you get the hang of it, define a small scope, solve it, and gain confidence.

     

  • Muon QuarkMuon Quark Posts: 580

    Afternoon,

    Received a pop up message that in a future update of the mac os (version 28) intel based apps will not work.  It was a game that I had purchased from Big Fish.  So what does that mean for DAZ studio on the mac?  I apoligize if this has been covered in another thread.  Feel free to direct me to the discussion about it.  Thanks.

  • TotteTotte Posts: 14,991

    Muon Quark said:

    Afternoon,

    Received a pop up message that in a future update of the mac os (version 28) intel based apps will not work.  It was a game that I had purchased from Big Fish.  So what does that mean for DAZ studio on the mac?  I apoligize if this has been covered in another thread.  Feel free to direct me to the discussion about it.  Thanks.

    hi, Apple Silicon version of Studio 6 in listed in the Evergrreen thread so it is coming. 

  • Muon QuarkMuon Quark Posts: 580

    Totte said:

    Muon Quark said:

    Afternoon,

    Received a pop up message that in a future update of the mac os (version 28) intel based apps will not work.  It was a game that I had purchased from Big Fish.  So what does that mean for DAZ studio on the mac?  I apoligize if this has been covered in another thread.  Feel free to direct me to the discussion about it.  Thanks.

    hi, Apple Silicon version of Studio 6 in listed in the Evergrreen thread so it is coming. 

    Thanks Totte.  I will check that out and start following it.   

  • memcneil70memcneil70 Posts: 5,765
    edited May 1

    Totte, I posted in the Commons/DIM thread I had received that warning as well for DIM. Is there any update for DIM in our future for those of us with MacMini M4?

    And from what you posted above, does that mean I will not be able to use DS 4-24 for those scripts/plug-ins that have not been able to be updated to DS6 yet?

    I have Tahoe 26.4.1 right now.

    Post edited by memcneil70 on
  • LeanaLeana Posts: 13,099

    Once support for intel based applications is gone then  you won't be able to use DS4 anymore, no. 

  • memcneil70memcneil70 Posts: 5,765

    Yes but what about DIM?

  • TotteTotte Posts: 14,991

    I think DIM will be easier to port as it is already based on higher Qt Versions and also a much "simpler" application, but I will toss a reminder to "who it will concern".

  • memcneil70memcneil70 Posts: 5,765

    Thanks Totte.

    So, to clarify, if we are able to work in DS6 now, will we continue to be able to do that after this upcoming MacOS update?

  • TotteTotte Posts: 14,991

    memcneil70 said:

    Thanks Totte.

    So, to clarify, if we are able to work in DS6 now, will we continue to be able to do that after this upcoming MacOS update?

    DS 6 is still intelbased, but macOS 28 wont come until I expect summer 2027 ( macOS27 is next next update that will be presented at WWDC on June 8).
      

  • memcneil70memcneil70 Posts: 5,765
    edited May 1

    If support is ending for 'Intel-based' apps like that pop-ups said, then that not only kills Daz Studio, but also Office 365 and other products we use on the Macs as well. Is Apple trying to destroy their business computer lines?

    Or do they think kids, AI, iPads, and iPhones are the only thing that matters?

    Post edited by memcneil70 on
  • TotteTotte Posts: 14,991

    memcneil70 said:

    If support is ending for 'Intel-based' apps like that pop-ups said, then that not only kills Daz Studio, but also Office 365 and other products we use on the Macs as well. Is Apple trying to destroy their business computer lines?

    Or do they think kids, AI, iPads, and iPhones are the only thing that matters?

    Nope, they will kill Intel support because of one main thing is Apple Intelligence, finger print login and may many upcoming things will never work on intel CPUs as they lack the Neural Engine, so right know, apple needs to keep so much "diversed code bases" to support, and they did the same when leaving 68k for PowerPC, and when leaving PowerPC for intel, six years compatiility releases, and all developers have had about 5 years of heads up already....

     

  • memcneil70memcneil70 Posts: 5,765

    Well, wonder if I can start trading my Mac products for Windows one then. Pity I do love my iPad for reading.

  • TotteTotte Posts: 14,991

    memcneil70 said:

    Well, wonder if I can start trading my Mac products for Windows one then. Pity I do love my iPad for reading.

    Most apps will be ready when macOS 28 ships, it's a probably in August 2027. 

  • memcneil70memcneil70 Posts: 5,765
    edited May 1

    But DS and DIM?

    I love working on both those two on the Mac over the Windows.

    Edit to fix a spelling goof.

    Post edited by memcneil70 on
  • Richard HaseltineRichard Haseltine Posts: 109,943

    memcneil70 said:

    But DS and DIM?

    I love working on sith those two on the Mac over the Windows.

    They know DS needs updating, and have it acknowledged in the Evergreen thread. DIM is required to install any beta of DS, so they will get a pointed reminder once they want to distribute the new version to any testers even if they haven't had it on their to-do list already.

  • memcneil70memcneil70 Posts: 5,765

    Thanks Richard. 

  • nayelinayeli Posts: 6

    Hello all,

    I've finally switched from Poser to DAZ on my Mac some month ago and so far I really love it. I've only one really anoying issue, DAZ crashes really often, around 3 of 4 times, when I start a dForce Simulation. It's allways at the start, if the simulation is running it always works perfectly. Maybe someone had similar issues ....

    I'm on a MBP with a M3 Max running on Tahoe 26.2, and I use DAZ 4.24.04.

    Many thanks in advance!

  • memcneil70memcneil70 Posts: 5,765

    @nayeli, I am on a MacMini M4 Pro and I just checked my current version of Tahoe and it is at 26.4.1. Is there a reason you haven't updated your OS?

    And yes, DAZ Studio can crash on scripts, it's picky. But simulations I generally have my issues with poses where body parts intersect another, clothing that explodes (intersecting the body or a prop). I try to be check for issues before running the simulation. One I just finished took me about an hour to get the pose and clothing and sitting prop just right. 

    Mary

  • nayelinayeli Posts: 6

    @mary: I guess I have just missed the last upates .... I don't really know how, because I've activated auto updates .... I will do it later today, but actually I don't think that's the reason.

    And I don't think as well, that it has to do anything with the scenes. The crashes allways happen before the simulation really starts .... and if I try the same simulation again, without any changes, it will work. Sometimes at the second attempt, sometimes at the third, sometimes at the fourth ..... And beside of this problem I don't have any issus with DAZ crashing at all. Everything else works stable. Very weird.

    Nayeli

  • TotteTotte Posts: 14,991

    nayeli said:

    Hello all,

    I've finally switched from Poser to DAZ on my Mac some month ago and so far I really love it. I've only one really anoying issue, DAZ crashes really often, around 3 of 4 times, when I start a dForce Simulation. It's allways at the start, if the simulation is running it always works perfectly. Maybe someone had similar issues ....

    I'm on a MBP with a M3 Max running on Tahoe 26.2, and I use DAZ 4.24.04.

    Many thanks in advance!

    Hi,

    The crashes in Studio on macOS with scripts is as far as I have investigated it ( and I've been digged deep ) is that is related to the fact that Studio runs under Rosetta2 x86_64 emulation on Apple Mx CPUs. Something is cached one way or another that causes scripts to be executed with a bad execution environment which causes Studio to go belly up. Once it has started correcly, this works. This seems also only be an issue with DS 4, DS 6 unde Qt 6 seems less prone to those issues, and when Studio is running natively on Mx CPUs that particular issue should be gone.

      

  • memcneil70memcneil70 Posts: 5,765

    Well, I am not an expert, but the one thing everyone checks first is versions installed. The other might be how they were installed? Did you use DIM for everything?

  • nayelinayeli Posts: 6

    Totte said:

    Hi,

    The crashes in Studio on macOS with scripts is as far as I have investigated it ( and I've been digged deep ) is that is related to the fact that Studio runs under Rosetta2 x86_64 emulation on Apple Mx CPUs. Something is cached one way or another that causes scripts to be executed with a bad execution environment which causes Studio to go belly up. Once it has started correcly, this works. This seems also only be an issue with DS 4, DS 6 unde Qt 6 seems less prone to those issues, and when Studio is running natively on Mx CPUs that particular issue should be gone.

    Thanks!

    I've not yet tried DS6, but I guess this might be a good reason to do so ... and to hope for a realease of an Apple Silicon version in the near future.

  • nayelinayeli Posts: 6

    memcneil70 said:

    Well, I am not an expert, but the one thing everyone checks first is versions installed. The other might be how they were installed? Did you use DIM for everything?

    I use DIM for everything that can be installed by DIM, yes.

    Software versions can often be an issue, but the last fixes of MacOS are not anything that sounds likely to have an impact on that behavior of DAZ, so I don't think this is related .... but nevertheless it's never a good idea not to be up to date with the OS, even if it's just a few minor releases that are missing. 

    I will try the suggestion by Totte and will install DS6 .... 

     

  • TotteTotte Posts: 14,991

    nayeli said:

    memcneil70 said:

    Well, I am not an expert, but the one thing everyone checks first is versions installed. The other might be how they were installed? Did you use DIM for everything?

    I use DIM for everything that can be installed by DIM, yes.

    Software versions can often be an issue, but the last fixes of MacOS are not anything that sounds likely to have an impact on that behavior of DAZ, so I don't think this is related .... but nevertheless it's never a good idea not to be up to date with the OS, even if it's just a few minor releases that are missing. 

    I will try the suggestion by Totte and will install DS6 .... 

     

    Keep in mind DS 6 is still beta and most scripts  needs to be ported to work in Studio 6, but when they do, it is much more stable.  The big OS changes that broke studio for a while was macOS 11, then devs had to do some "ugly fixes" to let it even run, because studio 4 is built on top of Qt 4, which has been deprecated for a while now, but changing framework is a huge task ( Studio 6 has been on the table for several years ).

     

  • nayelinayeli Posts: 6

    Totte said:

    Keep in mind DS 6 is still beta and most scripts  needs to be ported to work in Studio 6, but when they do, it is much more stable.  The big OS changes that broke studio for a while was macOS 11, then devs had to do some "ugly fixes" to let it even run, because studio 4 is built on top of Qt 4, which has been deprecated for a while now, but changing framework is a huge task ( Studio 6 has been on the table for several years ).

     

     

    Thanks for the warning, but a parallel installation of both versions would be a possibility to try if the preoblem with dForce disappears .....

Sign In or Register to comment.