The Mac FAQ

18889909193

Comments

  • inquireinquire Posts: 2,242

    @memcneil70: Beautiful work. Do you have any idea how long this would have taken on an older, Intel Mac?

  • memcneil70memcneil70 Posts: 4,309

    Thank you for the compliment @inquire. It shows when you are restricted to a limited range of options you can come out with something! Kind of like restrictions to only a few colors of paint creates masterworks.

    No, my old iMac had an Nvidia 660 card and I did have D|S loaded on it in 2016, but after a very bad crash in 2017 I never reinstalled D|S. That computer became my hub to keep records, and do my editing work. But I was only able to do a character, kitted out, scene, simple lights on it. It is why I was desperate to replace it with a new computer and I do like the Mac OS.

    But nowadays, my GTX 1080 and GTX 1080Ti Windows 10 machines have some issues with the newer, more demanding products. And on my MacBook Pro M1, there are some products I have had to uninstall because they cause problems or crash/freeze the computer.

    Maybe others with the older computers who have the Intel Macs can advise you?

    A positive thing about the Mac Mini M4 I have noted, is the speed which even large-size files download and install through DIM, along with other programs.

  • edited December 2024

    I'm strongly considering 'Genesis Generation X2' and addons, but I'm concerned about the installation format. Obviously, I'm a macOS user (13.x). But the old Bitrock Installer apps more often than not refuse to work (regardless of disabling Gatekeeper) probably (certainly?) due to the installer. My question: Does 'Genesis Generation X2' 64-bit have a newer better updated installer that will actually work for Ventura and DS 4.22? Does it install via Install Manager?

    Post edited by Mortimer J Snodsworth III on
  • memcneil70memcneil70 Posts: 4,309

    I just installed it through DIM into my new Mac Mini without thinking about it and its addons. I haven't tried it, but no issues that I know of.

  • memcneil70 said:

    I just installed it through DIM into my new Mac Mini without thinking about it and its addons. I haven't tried it, but no issues that I know of.

    Thank you! You've quelled my concern. AND it and its addons just went on sale today! 65% off!! Merry Christmas!

  • Unfortunately, despite following tutorials, GenX2 crashes DS seconds after initiating the transfer. It begins but then crashes. Log details don't offer any clue.

    Equally unfortunate, if not more so, is that the search function in the DAZ 3D forums is horrendous. In my experience, any keyword search results in each and every reference to the keyword in each and every post and susequent post for all time. I'd forgotten how bad is was.

  • memcneil70memcneil70 Posts: 4,309

    Don't search by way of the forum, use Google.

  • inquireinquire Posts: 2,242
    edited December 2024

    Sometimes I use the Mac search Such as Spotlight, or Command F, and then type in what I'm looking for. Sometimes that works and is better than the DazStudio search.

    oops, sorry:

    The above is if you have a product you've downloaded, and you can't locate it in the dad studio app, then those other methods sometimes works best.

    But yes, for searching the forums, Google usually works better than using the forum search item.

    Post edited by inquire on
  • Is it possible to use an iRay Server on a Windows machine to render on Macbooks?

    And is possible to delegate even the iRay preview to an iRay Server?

  • YacomoYacomo Posts: 39

    Neverdie Axis said:

    Is it possible to use an iRay Server on a Windows machine to render on Macbooks?

    And is possible to delegate even the iRay preview to an iRay Server?

    Never cared about the preview, but rendering using iRay Server works fine for me. I am currently running iRay Server 2024.0.4-377400.3959 on a gaming laptop with a GeForce 3080 together with Studio Beta 4.23 on my MacBook Pro. I could not get the current public Studio version to connect though, only the Beta wanted to cooperate...

    One thing I learned is that you do NOT want to use the render queue. Instead you want to check the 'Rendering' check box - afterwards all normal renders will be sent to the server including when rendering animations.

     

  • inquireinquire Posts: 2,242

    What exactly is an iRay Server?

  • YacomoYacomo Posts: 39

    inquire said:

    What exactly is an iRay Server?

    A server process running an a Windows or Linux machine with an NVidea graphics card:

    https://www.irayplugins.com/iray-server/

    You can connect to such a server using the 'Bridge' tab in the 'Render Settings' pane and do your renders on the server instead of your local machine. 

  • ElorElor Posts: 1,954
    edited January 7

    Neverdie Axis said:

    Is it possible to use an iRay Server on a Windows machine to render on Macbooks?

    And is possible to delegate even the iRay preview to an iRay Server?

    For the first question, yes. One thing to keep in mind: off the top of my head, if you're rendering a scene with an HDRI visible, Iray Server will hide it by default. It's still stored inside the picture but you'll have to, I think, remove the Alpha Channel to see it.

    If you have ImageMagick installed on your mac, you can do it with the following command:

    convert "[source_image]" -alpha off "[targer_image]"

    For the second question, I think it's possible to do it but never did.

    Jay Versluis has an old video about Iray Server:

    Post edited by Elor on
  • inquireinquire Posts: 2,242

    Is this the same kind of thing that Totte Mentioned Above?

    The video shows a component that must be downloaded. Is this always the case?
    I'm just trying to understand how this thing works.

  • ElorElor Posts: 1,954

    Yes, it is what Totte spoke about.

    They are two ways to use Iray Server:

    1. by downloading it and installing it on one of your own Windows/Linux computer using a Nvidia GPU.
    2. by paying someone else to take care of that and renting one of their computers.

    I think Totte is using the second way, renting someone else's computer when he needs a render.

  • inquireinquire Posts: 2,242

    So he just needs to communicate online through the Internet: is that correct?
    Would he then upload the Fial to the Internet?

    Would whatever app is on the Internet be able to sense which file on his computer was ready to be processed? And when the processing was over, would everything appear on his computer, so that he wouldn't have to download anything from the Internet?

  • OakMoon99OakMoon99 Posts: 27

     

    Maybe someone’s already asked this, but I figured I’d give it a shot anyway… My Mac got updated to OS 15.2 Sequoia yesterday, which turned out to be a really dumb move because now Daz Studio keeps crashing. Before this, I think I was using OS 13, and everything was working perfectly fine then.

    Here’s what I’ve noticed: every time I switch away from the Daz interface—whether to Finder or a browser—Daz immediately stops working. Is there any way to manually fix this issue? Or do I just have to give up on Daz until it gets patched?

  • GhostofMacbethGhostofMacbeth Posts: 1,673

    I am not sure but I will ask a question to help diagnose things. What version of Mac do you have? I think certain chips behave differently.

  • OakMoon99OakMoon99 Posts: 27

    GhostofMacbeth said:

    I am not sure but I will ask a question to help diagnose things. What version of Mac do you have? I think certain chips behave differently.

    I'm using a Macbook Pro 2019 (intel)

  • 42snoopy4242snoopy42 Posts: 31

    inquire said:

    So he just needs to communicate online through the Internet: is that correct?
    Would he then upload the Fial to the Internet?

    Would whatever app is on the Internet be able to sense which file on his computer was ready to be processed? And when the processing was over, would everything appear on his computer, so that he wouldn't have to download anything from the Internet?

    I use iray server on a local Linux device, i just have the server running and when I send a job to it it via iray bridge it "just works". It should be the same if I had a local windows server running iray server - I just find it easier to maintain a local Linux machine vs. a local Windows machine (since I'm a MacOS user). If leveraging an internet hosted iray server you'd still "send" the job request and then once the job is done it would be a simple download of the a zip file of the completed jpg/png file.  

  • seascapeclseascapecl Posts: 2
    edited January 25

    I am running a MacBook Pro M4 Pro 24GB Sequoia 15.2. I used to have a Mac Studio 30GB running DAZ 4.22. DAZ ran without issue on the Mac Studio.

    It takes several attempts to open DAZ 4.23 on the new machine. The icon blinks a couple of times and doesn't open. Occasionally, I will get the launch window (with the face) before DAZ crashes a second later. After about a dozen or so tries, DAZ usually opens. Any other program I use (FinalDraft, Photoshop, Blender, Kindle Create, Word, etc.) works without issue on the new machine. Render speeds in Photoshop and Blender are faster on the new machine. I've been sending the DAZ crash reports to Apple. 

    I sent in a help request to DAZ but they haven't responded. 

     

    Post edited by seascapecl on
  • inquireinquire Posts: 2,242

    Totte said:

    Scavenger said:

    Totte said:

    Ok.. black friday-cyber monday time.. so I'm at the decision point.

    I'm thinking the Mac Mini Pro base with the 24 gig memory will be the choice.... I'm debating heavily on the processor upgrade or the ram upgrade... but I'm leaning (trying to convince myself) that the base will be more than I need and the extra money is better used elsewhere.

    Apple M4 Pro chip with 12‑core CPU, 16‑core GPU, 16‑core Neural Engine24GB unified memory$1,399

    (this is also versus the

    Apple M4 chip with 10‑core CPU, 10‑core GPU, 16‑core Neural Engine32GB unified memory$1,199

    I think it's the right balance between power, capability, and price that should give me a lot of years of use (and if i start making more money off stuff that i NEED more..ram for example...I can look into the potentional 3rd party ram upgrades that are being worked on, or buy back/buy new plans)

    (I'm upgrading from a 2012 imac and a 6 or more yo windows pc with a 1070ti, so it's more future years I'm looking at rather than imrpovement over current as that's a given).

    ALL INSIGHTS and OPINONS are helpful.

    I say 32GB RAM, at least. I have issues rendering on my 32GB machine with Iray as it chews up all RAM and then it gets really slow (much worse when using consolidated RAM/VRAM. I have no problem rendering a scene on my 64GB MacPro 2013 when Studio uses 100+ GB RAM, but when Studio hits 26 GB RAM on the 32GB RAM macStudio shit hits the fan

    when you look at specs for the new MACs, Those with M chips, It doesn't list RAM. So what do you look at to judge what you're getting that is compatible with RAM? Is it unified memory?

  • wsterdanwsterdan Posts: 2,404

    inquire said:

    Totte said:

    Scavenger said:

    Totte said:

    Ok.. black friday-cyber monday time.. so I'm at the decision point.

    I'm thinking the Mac Mini Pro base with the 24 gig memory will be the choice.... I'm debating heavily on the processor upgrade or the ram upgrade... but I'm leaning (trying to convince myself) that the base will be more than I need and the extra money is better used elsewhere.

    Apple M4 Pro chip with 12‑core CPU, 16‑core GPU, 16‑core Neural Engine24GB unified memory$1,399

    (this is also versus the

    Apple M4 chip with 10‑core CPU, 10‑core GPU, 16‑core Neural Engine32GB unified memory$1,199

    I think it's the right balance between power, capability, and price that should give me a lot of years of use (and if i start making more money off stuff that i NEED more..ram for example...I can look into the potentional 3rd party ram upgrades that are being worked on, or buy back/buy new plans)

    (I'm upgrading from a 2012 imac and a 6 or more yo windows pc with a 1070ti, so it's more future years I'm looking at rather than imrpovement over current as that's a given).

    ALL INSIGHTS and OPINONS are helpful.

    I say 32GB RAM, at least. I have issues rendering on my 32GB machine with Iray as it chews up all RAM and then it gets really slow (much worse when using consolidated RAM/VRAM. I have no problem rendering a scene on my 64GB MacPro 2013 when Studio uses 100+ GB RAM, but when Studio hits 26 GB RAM on the 32GB RAM macStudio shit hits the fan

    when you look at specs for the new MACs, Those with M chips, It doesn't list RAM. So what do you look at to judge what you're getting that is compatible with RAM? Is it unified memory?

    Yes. The two highlighted machine above are 24 and 32 gigabyte machines, respectively. There is only "unified memory" RAM on silicon-based machines, the CPU and GPU share the RAM.

  • memcneil70memcneil70 Posts: 4,309

    I had an update for Sequoia 15.3 on my MacMini M4 and MacBook Pro M1 this morning. No issues with the install but as I tried to open Daz Studio 4.23.1.23 it crashed 4 times, not giving me a crash report. The 5th time it finally opened. And as I started this entry, a crash report for Apple finally showed up. So don't be surprised if it takes a bit to get D|S ready to work for you. If I have further issues, I will note them.

  • memcneil70 said:

    I had an update for Sequoia 15.3 on my MacMini M4 and MacBook Pro M1 this morning. No issues with the install but as I tried to open Daz Studio 4.23.1.23 it crashed 4 times, not giving me a crash report. The 5th time it finally opened. And as I started this entry, a crash report for Apple finally showed up. So don't be surprised if it takes a bit to get D|S ready to work for you. If I have further issues, I will note them.

    I'm also having this problem, but restarting multiple times doesn't help. DS crashes, crashes, crashes, all when it's the loading plugin phase, and I can't use it at all. M1 MBP, 16 GB RAM, MacOS 15.3. Latest DS built

  • Richard HaseltineRichard Haseltine Posts: 102,669

    aaráribel caađo said:

    memcneil70 said:

    I had an update for Sequoia 15.3 on my MacMini M4 and MacBook Pro M1 this morning. No issues with the install but as I tried to open Daz Studio 4.23.1.23 it crashed 4 times, not giving me a crash report. The 5th time it finally opened. And as I started this entry, a crash report for Apple finally showed up. So don't be surprised if it takes a bit to get D|S ready to work for you. If I have further issues, I will note them.

    I'm also having this problem, but restarting multiple times doesn't help. DS crashes, crashes, crashes, all when it's the loading plugin phase, and I can't use it at all. M1 MBP, 16 GB RAM, MacOS 15.3. Latest DS built

    It would seem likely that there is an issue with one or more plug-ins - either the local installation or in general. For those installed through DIM you can, if you have the default filters, click the funnel icon next to the filter text box at top-right and select Tags>Plugins and then the release channel/architecture to get a list, from which you can select and unisntall the non-Daz plug-ins; if, before uninstalling, you right-click on one of the items and select Filter Installed>By Selected the text in the filter box will be updated to show only the items currently seelcted, you can then save that by clicking the Funnel icon and selecting Save Filter so that you can easily get the list back to selectively reinstall (if the crashing stops, so as to identify the culprit) or to reisntall all.

    You can also use http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start to deisable non-Daz plug-ins, which may be useful after the previous steps if you have manually installed plug-ins from external sources. You could then reenable those through Help>About Installed Plug-ins followed by restarting Daz Studio if one of them seemed to be causing the crash, to identify the culprit.

  • YacomoYacomo Posts: 39
    edited January 30

    I do not believe that this is related to some plugin or the last macOS update.

    For the last two betas, Studio seems to have become even more unstable on Apple Silicon. Crashes upon launch are new to me. 

    It does not always crash on launch, but it does crash about 50 - 70% of the time for me:

    Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
    0   Rosetta Runtime Routines           0x100018a84 ???
    1   <translation info unavailable>           0x1013f88ec ???
    2   dyld                                     0x2001c11d7 abort_with_payload_wrapper_internal + 82
    3   dyld                                     0x2001c1209 abort_with_payload + 9
    4   dyld                                     0x2001536e5 dyld4::halt(char const*, dyld4::StructuredError const*) + 335
    5   dyld                                     0x2001bffe2 abort_report_np + 146
    6   dyld                                     0x2001c0fed Diagnostics::assertNoError() const (.cold.1) + 26
    7   dyld                                     0x20014b0f7 Diagnostics::assertNoError() const + 17
    8   dyld                                     0x20018feb2 dyld3::MachOFile::getDylibInstallName(char const**, unsigned int*, unsigned int*) const + 160
    9   dyld                                     0x2001774d9 invocation function for block in dyld4::APIs::NSVersionOfRunTimeLibrary(char const*) + 76
    10  dyld                                     0x2001561b8 dyld4::RuntimeLocks::withLoadersReadLock(void () block_pointer) + 46
    11  dyld                                     0x200177445 dyld4::APIs::NSVersionOfRunTimeLibrary(char const*) + 121
    12  AppKit                                0x7ff80b297027 NSTrackingAreaAKPostEventsAtBackDefaultValueFunction + 278
    13  AppKit                                0x7ff80a932e69 _NSGetBoolAppConfig + 238
    14  AppKit                                0x7ff80b290d8c -[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:] + 11956
    15  AppKit                                0x7ff80b291e32 -[_NSTrackingAreaAKManager routeEnterExitEvent:] + 27
    16  AppKit                                0x7ff80aac598d -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 533
    17  AppKit                                0x7ff80aac555d -[NSWindow(NSEventRouting) sendEvent:] + 339
    18  QtGui                                    0x109c085a2 -[QCocoaWindow sendEvent:] + 114
    19  AppKit                                0x7ff80b28604e +[_NSTrackingAreaAKManager routeEnterExitEvent:] + 97
    20  AppKit                                0x7ff80b23f7b2 +[_NSTrackingAreaManager routeEnterExitEvent:] + 315
    21  AppKit                                0x7ff80b3c0758 -[NSApplication(NSEventRouting) sendEvent:] + 340
    22  QtGui                                    0x109c0c07e -[QNSApplication sendEvent:] + 94
    23  QtGui                                    0x109c14e49 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1601
    24  QtCore                                   0x108a2e0dc QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 78
    25  libdztimeline.dylib                      0x1141025b9 0x1140d3000 + 193977
    26  libdztimeline.dylib                      0x1141026d1 0x1140d3000 + 194257
    27  libdztimeline.dylib                      0x1140df703 0x1140d3000 + 50947
    28  QtCore                                   0x108a43131 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2001
    29  libdztimeline.dylib                      0x1140ea900 0x1140d3000 + 96512
    30  libdztimeline.dylib                      0x114106c63 0x1140d3000 + 212067
    31  libdzcore.dylib                          0x10c6b2e73 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8321331
    32  libdzcore.dylib                          0x10c6b6f72 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8337970
    33  libdzcore.dylib                          0x10c6fabd4 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8615572
    34  libdzcore.dylib                          0x10c701a40 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8643840
    35  libdzcore.dylib                          0x10c7027e5 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8647333
    36  libdzcore.dylib                          0x10c702e5f DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8648991
    37  libdzcore.dylib                          0x10ba5d979 DzScopeResolver::initIdentifierReplacements() + 413591
    38  QtCore                                   0x108a43131 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2001
    39  libdzcore.dylib                          0x10c643868 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7865128
    40  libdzcore.dylib                          0x10c6450da DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7871386
    41  DAZStudio                                0x1000025dd main + 461
    42  DAZStudio                                0x100002304 start + 52

    Also, many scripts crash randomly, all with the same trace:

    Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
    0   <translation info unavailable>           0x104b77b28 ???
    1   QtCore                                   0x108a37c65 QMetaType::construct(int, void const*) + 1953
    2   QtCore                                   0x108a4d242 construct(QVariant::Private*, void const*) + 1762
    3   QtGui                                    0x109c95678 construct(QVariant::Private*, void const*) + 2088
    4   QtCore                                   0x108a50591 QVariant::QVariant(int, void const*) + 49
    5   QtScript                                 0x111f8de75 QScript::callQtMethod(QTJSC::ExecState*, QMetaMethod::MethodType, QObject*, QTJSC::ArgList const&, QMetaObject const*, int, bool) + 4165
    6   QtScript                                 0x111f91848 QScript::QtFunction::execute(QTJSC::ExecState*, QTJSC::JSValue, QTJSC::ArgList const&) + 408
    7   QtScript                                 0x111f85526 QScript::QtFunction::call(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) + 186
    8   QtScript                                 0x111ee4de1 QTJSC::NativeFuncWrapper::operator()(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) const + 113
    9   QtScript                                 0x111ecd32d cti_op_call_NotJSFunction + 221
    10  ???                                   0x5c968b23c279 ???
    11  QtScript                                 0x111e8e5f9 QTJSC::Interpreter::execute(QTJSC::EvalExecutable*, QTJSC::ExecState*, QTJSC::JSObject*, int, QTJSC::ScopeChainNode*, QTJSC::JSValue*) + 975
    12  QtScript                                 0x111e8e77c QTJSC::Interpreter::execute(QTJSC::EvalExecutable*, QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::ScopeChainNode*, QTJSC::JSValue*) + 114
    13  QtScript                                 0x111f68a80 QScriptEnginePrivate::evaluateHelper(QTJSC::ExecState*, long, QTJSC::EvalExecutable*, bool&) + 754
    14  QtScript                                 0x111f68c36 QScriptEngine::evaluate(QScriptProgram const&) + 140

    That one was with Alienator Pro II Set Builder, but for instance most of Riversofts Scripts can crash randomly on Apple Silicon as well. Interestingly, if the first attempt to run such a script succeeds, then all subsequent attempts will work as well.

    Mac support was always bad at DAZ, the argument lately being that their QT version is totally outdated and in essence incompatible with current versions of macOS.

    However Studio 5 which is presumably based on a modern QT is nowhere to be seen. Honestly I do not know where to go from here, is it even worth reporting such bugs? Does anybody at DAZ even care?

    Post edited by Yacomo on
  • inquireinquire Posts: 2,242

    I'm wondering if this is happening because the app is running in emulation on the Apple Silicon chips. As the OS is modified, perhaps the emulation also has to go through tweaks. Could this be what is causing problems with the app running in an emulation mode: to whit, Unexpected tweaks?

  • aaráribel caađoaaráribel caađo Posts: 690
    edited January 31

    I removed all the plug-ins, unless there's possibly someting I installed manually and forgot—which seems unlikely—and it still crashes. 

     

    Edit: I removed all the plug-ins from teh plug in folder, uninstalled DS, reinstalled it, and it still crashes

    Post edited by aaráribel caađo on
  • memcneil70memcneil70 Posts: 4,309

    I didn't post further because D|S settled down for me on my Mac Mini M4. I have been downloading old products without metadata (4 digit SKUs) and have been adding it, and when I previously tried to gather like scattered items up with selecting the CMD key and left mouse button it would crash D|S at least once, but now it seems to do it without issue. But yeah, opening D|S is still iffy, but that is not something new. What worried me was 'no log report'. And 5 times was excessive. I just opened up and it was perfect today.

    What I have noticed is that every D|S update that has come out seems to be improving the interface of MacOS Metals with D|S. That is my uneducated opinion. Until this update from Apple arrived.

    I only install with DIM and my only issue with my plug-ins and scripts has been forgetting how they work and having to relearn them. Once I get back into the tutorials/documentations, they work as I remember. I just haven't been able to 'use' D|S as intended for months and I have lost my muscle-memory of their operation.

Sign In or Register to comment.