Loading...
> >

The New Mac FAQ

2456

Comments

  • TotteTotte Posts: 14,677

    inquire said:

    Well, I really feel that we should have more updates from DAZ3D. They should tell us Whether or not, they are making progress and developing an Apple Silicon version of DS.

    Also, at WWDC, There is an indication that Apple will help companies incorporate Apple Intelligence into their apps. It would be great if DAZ Made an Apple version of DS And included Apple Intelligence in it. It would be super if DAZ Included Apple Metal In it. Someone could write a translation version from Nvidia shaders to metal shaders. I would really like to experiment with that.
    I think filament is a poor alternative to the nVidia Rendering.

    Filament in DS 6 / 2025 is based on Metal on macOS.
    The Viewport is also based on Metal on macOS.
     
    Check profiler under Activity Monitor:
    /System/Library/Extensions/AppleMetalOpenGLRenderer.bundle/Contents/MacOS/AppleMetalOpenGLRenderer
    /private/var/db/oah/ea72064422e54f697b7431461ee92103a0179fc81d9631db29c3a82d0a133dba/ec3eef5a240e192d228a24d5e25638b901834cf1350d9d66c250b493a94b4b6d/AppleMetalOpenGLRenderer.aot
    /System/Library/Extensions/AGXMetalG13X.bundle/Contents/Resources/ds.g13s
    /System/Library/Extensions/AGXMetalG13X.bundle/Contents/MacOS/AGXMetalG13X
    /System/Library/Extensions/AppleMetalOpenGLRenderer.bundle/Contents/Resources/default.metallib
    /System/Library/Extensions/AppleMetalOpenGLRenderer.bundle/Contents/Resources/PixelConverter.metallib

     


     

     

  • inquireinquire Posts: 2,416

    News to me. Thank you. I just looked at the examples for the ads and the products in the DAZ Shop. I didn't think that filament looked as good as the Nvidia vendors look.

  • Richard HaseltineRichard Haseltine Posts: 107,857

    inquire said:

    News to me. Thank you. I just looked at the examples for the ads and the products in the DAZ Shop. I didn't think that filament looked as good as the Nvidia vendors look.

    Filament isn'ty intended as a full render engine, using Metal doesn't automatically change that.

  • wsterdanwsterdan Posts: 3,040
    edited June 10

    inquire said:

    News to me. Thank you. I just looked at the examples for the ads and the products in the DAZ Shop. I didn't think that filament looked as good as the Nvidia vendors look.

    I think we did discuss this back in the old thread, and I did suggest checking the store out to see what Filament products there are and how they look when used properly.

    As Richard said, Filament isn't designed to be a high-end rendering engine but one that's lightweight enough to be used for mobile and games and such. It's not as photorealistic as NVIDIA, it's slightly stylized. That said, it's capable of some excellent renders (as shown by some of the store products), it's extremely fast and lightweight, and as you're aware now has Filatoon; all this, for the type of work I do, makes it an excellent replacement for most of what 3Delight and OpenGL used to provide.  

    The ever-helpful Leana provided links to threads for Trek-modeller extrordinaire rduda on Filatoon, both excellent theads:

    https://www.daz3d.com/forums/discussion/comment/9193591/#Comment_9193591

    And Mec4d supplies some excellent information on shaders for Filament here:

    https://www.daz3d.com/forums/discussion/445567/filament-tutorials-shaders-lights/p1

    Post edited by wsterdan on
  • ElorElor Posts: 3,130

    Tatefa3D said:

    Thanks for the feedback and suggestion. I'm going with the 4TB. 

    If at one point in the future you want an external SSD, I suggest looking for one with support for USB 4, capable of speed up to 4000MB/s: I bought one recently (Corsair EX400U) and it made Daz Studio feels as reponsive as it was when all my content was on my MBP internal SSD, something the Samsung T7 I had before wasn't able to do.

  • memcneil70memcneil70 Posts: 5,237

    Another great use for Filament is the setting up of a scene, preparing to test a character or product and the switching to Iray for the final render. Jay Versluis has a great tutorial on this. I loved it when I had only my Windows computers and felt cramped up when I got my MacBook Pro and then the Mac Mini M4 Pro. But with DS6, I have it back. It is not just for toons.

  • TotteTotte Posts: 14,677

    memcneil70 said:

    Another great use for Filament is the setting up of a scene, preparing to test a character or product and the switching to Iray for the final render. Jay Versluis has a great tutorial on this. I loved it when I had only my Windows computers and felt cramped up when I got my MacBook Pro and then the Mac Mini M4 Pro. But with DS6, I have it back. It is not just for toons.

    Indeed, as it "looks better" than the basic viewport. 

  • inquireinquire Posts: 2,416

    You know, I think it is when I set a main heavyweight bone minion on a figure, and then save the file, when I try to reopen that scene file, it causes Daz studio to crash. This is version 24.0.3, running in emulation on macOS Sequoia 15.5.

  • TotteTotte Posts: 14,677

    Check the crashlog, if it's script issue, you usually get a line number, some issues crashes opn macOS while they just gives an error on Windows (macOS is a bit pickier when processes does non-allowed things)

  • inquireinquire Posts: 2,416

    Here's what I got from a log file.


    2025-07-14 10:34:31.439 [VERBOSE] ::     libdzshadermixergui.dylib
    2025-07-14 10:34:31.452 [VERBOSE] ::     libdzsmartcontentpane.dylib
    2025-07-14 10:34:31.459 [VERBOSE] ::     libdzspotrendertool.dylib
    2025-07-14 10:34:31.466 [VERBOSE] ::     libdzstrandbasedhaireditor.dylib
    2025-07-14 10:34:31.628 [VERBOSE] ::     libdztextureatlas.dylib
    2025-07-14 10:34:31.640 [VERBOSE] ::     libdztimeline.dylib
    2025-07-14 10:34:31.648 [VERBOSE] ::     libdztransferutility.dylib
    2025-07-14 10:34:31.659 [VERBOSE] ::     libdzu3dexporter.dylib
    2025-07-14 10:34:31.665 [VERBOSE] ::     libdzweightmapbrush.dylib
    2025-07-14 10:34:31.678 [VERBOSE] ::     MF_meshgrab.dylib
    2025-07-14 10:34:31.779 [VERBOSE] ::     MF_meshmorph.dylib
    2025-07-14 10:34:31.788 [VERBOSE] ::     MF_meshrot.dylib
    2025-07-14 10:34:31.795 [VERBOSE] ::     SDK_SceneInfoPane.dylib
    2025-07-14 10:34:31.803 [VERBOSE] ::     libdzdrawstyles.dylib
    2025-07-14 10:34:31.812 [VERBOSE] ::     libdzpowerpose.dylib
    2025-07-14 10:34:31.829 [WARNING] :: Error writing author data.
    2025-07-14 10:34:31.853 [INFO] Iray :: Initializing...
    2025-07-14 10:34:31.853 Iray [INFO] - API:MISC ::   0.0   API    misc info : Loaded "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/libneuray.so"
    2025-07-14 10:34:31.854 Iray [INFO] - API:MISC ::   0.0   API    misc info : Iray 2023.1.4, build 373000.3036, 18 Mar 2024, macosx-x86-64
    2025-07-14 10:34:31.855 [INFO] Iray :: Rendering Configuration:
    2025-07-14 10:34:31.855 [INFO] Iray ::     CPU Fallback: enabled
    2025-07-14 10:34:31.855 [INFO] Iray ::     GPU Detection: enabled
    2025-07-14 10:34:31.855 [INFO] Iray ::     GPU Driver Version Check: enabled
    2025-07-14 10:34:31.855 [INFO] Iray :: Loading Plugins...
    2025-07-14 10:34:31.858 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/aix.so".
    2025-07-14 10:34:31.874 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/axf_importer.so".
    2025-07-14 10:34:31.877 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/cb_importer.so".
    2025-07-14 10:34:31.879 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/ct.so".
    2025-07-14 10:34:31.886 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/dds.so".
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn : Loading /Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/ffmpeg_video_decoder.so: dlopen(/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/ffmpeg_video_decoder.so, 0x0001): Library not loaded: @executable_path/libavutil.58.dylib
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn :   Referenced from: <9BBF3130-EAF4-3914-A319-5DEAB6C72291> /Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/libavcodec.60.dylib
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn :   Reason: tried: '/Applications/DAZ 3D/DAZStudio4 64-bit/DAZStudio.app/Contents/MacOS/libavutil.58.dylib' (no such file), '/usr/local/lib/libavutil.58.dylib' (no such file), '/usr/lib/libavutil.58.dylib' (no such file, not in dyld cache)Library not loaded: @executable_path/libavcodec.60.dylib
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn :   Referenced from: <97FCC184-6473-32AD-9EE0-41C7EA9A5535> /Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/libavformat.60.dylib
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn :   Reason: tried: '/Applications/DAZ 3D/DAZStudio4 64-bit/DAZStudio.app/Contents/MacOS/libavcodec.60.dylib' (no such file), '/usr/local/lib/libavcodec.60.dylib' (no such file), '/usr/lib/libavcodec.60.dylib' (no such file, not in dyld cache)Library not loaded: @executable_path/libavutil.58.dylib
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn :   Referenced from: <C917C427-E3D7-33BF-B419-5A742B7213D3> /Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/libswscale.7.dylib
    2025-07-14 10:34:31.889 [WARNING] :: /src/pluginsource/DzIrayRender/dzneuraymgr.cpp(373): Iray [WARNING] - LINK:PLUGIN ::   0.0   LINK   plug warn :   Reason: tried: '/Applications/DAZ 3D/DAZStudio4 64-bit/DAZStudio.app/Contents/MacOS/libavutil.58.dylib' (no such file), '/usr/local/lib/libavutil.58.dylib' (no such file), '/usr/lib/libavutil.58.dylib' (no such file, not in dyld cache)
    2025-07-14 10:34:31.894 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/iray_bridge_client.so".
    2025-07-14 10:34:31.898 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/iray_bridge_server.so".
    2025-07-14 10:34:31.908 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/libiray.so".
    2025-07-14 10:34:31.911 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/mdl_distiller.so".
    2025-07-14 10:34:31.916 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/mi_exporter.so".
    2025-07-14 10:34:31.922 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/mi_importer.so".
    2025-07-14 10:34:31.937 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/nv_openimageio.so".
    2025-07-14 10:34:31.940 Iray [INFO] - PLUG:PLUGIN ::   0.0   PLUG   plug info : Loaded library "/Applications/DAZ 3D/DAZStudio4 64-bit/libs/iray/screen_video.so".
    2025-07-14 10:34:31.940 [INFO] Iray :: Starting...
    2025-07-14 10:34:31.959 Iray [INFO] - INDEX:MAIN ::   0.1   INDEX  main info : Loaded NVIDIA IndeX 2.4 (build 373000.3036, 18 Mar 2024, macosx-x86-64-clang1400)
    2025-07-14 10:34:31.981 Iray [INFO] - CLUSTR:NETWORK ::   0.1   CLUSTR net  info : Networking is switched off.
    2025-07-14 10:34:31.983 Iray [INFO] - AIX:IMAGE ::   1.1   AIX    img  info : Plugin "aix" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.983 Iray [INFO] - CT:IMAGE ::   1.1   CT     img  info : Plugin "ct" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.983 Iray [INFO] - DDS:IMAGE ::   1.1   DDS    img  info : Plugin "dds" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.983 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_bmp" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_exr" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_gif" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_hdr" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_jpg" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_jp2" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_j2k" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_png" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_pnm" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_psd" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_tga" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_tif" (build 373000.3036, 18 Mar 2024) initialized
    2025-07-14 10:34:31.984 Iray [INFO] - OIIO:IMAGE ::   1.1   OIIO   img  info : Plugin "oiio_webp" (build 373000.3036, 18 Mar 2024) initialized

  • inquireinquire Posts: 2,416

    Here's part of the most recent crash I had just moments ago. As soon as I tried to apply the bone minion for Genesis 8 to a G9 figure, studio crashed. I can't include the full report because when I click on post comment, it says the report is too long.

    Process:               DAZStudio [2418]
    Path:                  /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
    Identifier:            com.DAZ.DAZStudio
    Version:               4.24.0.3 (4.24.0.3)
    Code Type:             X86-64 (Translated)
    Parent Process:        launchd [1]
    User ID:               501

    Date/Time:             2025-07-14 10:42:51.4053 -0700
    OS Version:            macOS 15.5 (24F74)
    Report Version:        12
    Anonymous UUID:        20457816-10C8-B8C8-4A9C-C4F4FECAAEC5


    Time Awake Since Boot: 1300 seconds

    System Integrity Protection: enabled

    Notes:
    RIP register does not match crashing frame (0x12D4392B0 vs 0x105559F38)

    Crashed Thread:        0  Dispatch queue: com.apple.main-thread

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
    Exception Codes:       0x0000000000000001, 0x0000000000000000

    Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
    Terminating Process:   exc handler [2418]

    VM Region Info: 0 is not in any region.  Bytes before following region: 4294967296
          REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
          UNUSED SPACE AT START
    --->  
          __TEXT                      100000000-100003000    [   12K] r-x/rwx SM=COW  /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio

    Error Formulating Crash Report:
    RIP register does not match crashing frame (0x12D4392B0 vs 0x105559F38)

    Kernel Triage:
    VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter


    Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
    0   ???                                      0x105559f38 ???
    1   QtCore                                   0x108a1bc65 QMetaType::construct(int, void const*) + 1953
    2   QtCore                                   0x108a31242 construct(QVariant::Private*, void const*) + 1762
    3   QtGui                                    0x109c79678 construct(QVariant::Private*, void const*) + 2088
    4   QtCore                                   0x108a34591 QVariant::QVariant(int, void const*) + 49
    5   QtScript                                 0x111f9ce75 QScript::callQtMethod(QTJSC::ExecState*, QMetaMethod::MethodType, QObject*, QTJSC::ArgList const&, QMetaObject const*, int, bool) + 4165
    6   QtScript                                 0x111fa0848 QScript::QtFunction::execute(QTJSC::ExecState*, QTJSC::JSValue, QTJSC::ArgList const&) + 408
    7   QtScript                                 0x111f94526 QScript::QtFunction::call(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) + 186
    8   QtScript                                 0x111ef3de1 QTJSC::NativeFuncWrapper::operator()(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) const + 113
    9   QtScript                                 0x111edc32d cti_op_call_NotJSFunction + 221
    10  ???                                   0x5184b0a3d09a ???
    11  QtScript                                 0x111e9d5f9 QTJSC::Interpreter::execute(QTJSC::EvalExecutable*, QTJSC::ExecState*, QTJSC::JSObject*, int, QTJSC::ScopeChainNode*, QTJSC::JSValue*) + 975
    12  QtScript                                 0x111e9d77c QTJSC::Interpreter::execute(QTJSC::EvalExecutable*, QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::ScopeChainNode*, QTJSC::JSValue*) + 114
    13  QtScript                                 0x111f77a80 QScriptEnginePrivate::evaluateHelper(QTJSC::ExecState*, long, QTJSC::EvalExecutable*, bool&) + 754
    14  QtScript                                 0x111f77c36 QScriptEngine::evaluate(QScriptProgram const&) + 140
    15  libdzcore.dylib                          0x10c2a1c54 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4106932
    16  libdzcore.dylib                          0x10c2a2556 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4109238
    17  libdzcore.dylib                          0x10c2a2603 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4109411
    18  libdzcore.dylib                          0x10c2a277d DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4109789
    19  libdzcore.dylib                          0x10bf65888 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 714472
    20  libdzcore.dylib                          0x10bf6918f DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 729071
    21  libdzcore.dylib                          0x10bed88c9 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 137001
    22  libdzcore.dylib                          0x10bf2ac97 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 473847
    23  libdzcore.dylib                          0x10bf2dbbb DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 485915
    24  libdzcore.dylib                          0x10bf8a115 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 864117
    25  libdzcore.dylib                          0x10bf8b20b DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 868459
    26  libdzcore.dylib                          0x10c0b02b0 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 2068752
    27  libdzcore.dylib                          0x10c0b5c81 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 2091745
    28  libdzcore.dylib                          0x10c0b6529 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 2093961
    29  libdzcore.dylib                          0x10c0b65d1 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 2094129
    30  libdzcore.dylib                          0x10ba15129 DzScopeResolver::initIdentifierReplacements() + 176439
    31  libdzcore.dylib                          0x10ba16e4f DzScopeResolver::initIdentifierReplacements() + 183901
    32  QtScript                                 0x111f9ee2a QScript::callQtMethod(QTJSC::ExecState*, QMetaMethod::MethodType, QObject*, QTJSC::ArgList const&, QMetaObject const*, int, bool) + 12282
    33  QtScript                                 0x111fa0848 QScript::QtFunction::execute(QTJSC::ExecState*, QTJSC::JSValue, QTJSC::ArgList const&) + 408
    34  QtScript                                 0x111f94526 QScript::QtFunction::call(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) + 186
    35  QtScript                                 0x111ef3de1 QTJSC::NativeFuncWrapper::operator()(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) const + 113
    36  QtScript                                 0x111edc32d cti_op_call_NotJSFunction + 221
    37  ???                                   0x5184b0a39d31 ???
    38  QtScript                                 0x111e9d5f9 QTJSC::Interpreter::execute(QTJSC::EvalExecutable*, QTJSC::ExecState*, QTJSC::JSObject*, int, QTJSC::ScopeChainNode*, QTJSC::JSValue*) + 975
    39  QtScript                                 0x111e9d77c QTJSC::Interpreter::execute(QTJSC::EvalExecutable*, QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::ScopeChainNode*, QTJSC::JSValue*) + 114
    40  QtScript                                 0x111f77a80 QScriptEnginePrivate::evaluateHelper(QTJSC::ExecState*, long, QTJSC::EvalExecutable*, bool&) + 754
    41  QtScript                                 0x111f77c36 QScriptEngine::evaluate(QScriptProgram const&) + 140
    42  libdzcore.dylib                          0x10c2a1c54 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4106932
    43  libdzcore.dylib                          0x10c2a2556 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4109238
    44  libdzcore.dylib                          0x10c2a2603 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 4109411
    45  libdzcore.dylib                          0x10ba615a6 DzScopeResolver::initIdentifierReplacements() + 488884
    46  libdzcore.dylib                          0x10ba6203f DzScopeResolver::initIdentifierReplacements() + 491597
    47  QtScript                                 0x111f9ee2a QScript::callQtMethod(QTJSC::ExecState*, QMetaMethod::MethodType, QObject*, QTJSC::ArgList const&, QMetaObject const*, int, bool) + 12282
    48  QtScript                                 0x111fa0848 QScript::QtFunction::execute(QTJSC::ExecState*, QTJSC::JSValue, QTJSC::ArgList const&) + 408
    49  QtScript                                 0x111f94526 QScript::QtFunction::call(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) + 186
    50  QtScript                                 0x111ef3de1 QTJSC::NativeFuncWrapper::operator()(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) const + 113
    51  QtScript                                 0x111edc32d cti_op_call_NotJSFunction + 221
    52  ???                                   0x5184b0a1ff8c ???

  • TotteTotte Posts: 14,677

    Error Formulating Crash Report:
    RIP register does not match crashing frame (0x12D4392B0 vs 0x105559F38)

    Kernel Triage:
    VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

    This sounds like a crash when memory gets  exhausted, can be a rosetta2 issue.

  • inquireinquire Posts: 2,416

    Oh, is that it? A Rosetta 2 issue where the memory gets exhausted? I have two Swole Characters in the scene, Hercules and Fibo. Every time I try to move them, even an arm, it's slow to update. Yet I have the M3 ultra Version of Mac Studio, with the memory maxed out. So is the slowness Due to a Rosetta 2 issue?

  • ElorElor Posts: 3,130
    edited July 15

    Some hairs and clothes can make changing the pose of a character very slow and as far as I know (Totte will know better), DS4 viewport is only using one CPU core so it's not taking advantage of your M3 Ultra (it's still very useful once you're rendering).

    I would check the viewport resolution of any clothes (some clothes are loaded with a viewport resolution of 3 or more, which is usually not useful) and I would also check if the Line Tessalation value of strand based hair is not too high for the viewport.

    Post edited by Elor on
  • TotteTotte Posts: 14,677

    inquire said:

    Oh, is that it? A Rosetta 2 issue where the memory gets exhausted? I have two Swole Characters in the scene, Hercules and Fibo. Every time I try to move them, even an arm, it's slow to update. Yet I have the M3 ultra Version of Mac Studio, with the memory maxed out. So is the slowness Due to a Rosetta 2 issue?

    Studio is not yet Apple silicon ported, it's a ongoing process AFAIK

  • wsterdanwsterdan Posts: 3,040
    edited July 15

    inquire said:

    Oh, is that it? A Rosetta 2 issue where the memory gets exhausted? I have two Swole Characters in the scene, Hercules and Fibo. Every time I try to move them, even an arm, it's slow to update. Yet I have the M3 ultra Version of Mac Studio, with the memory maxed out. So is the slowness Due to a Rosetta 2 issue?

    Have you tried doing the same thing in DAZ Studio 2025 to see if it happens there, just as a test? I'd be interested to see if Metal makes a difference.

    Post edited by wsterdan on
  • inquireinquire Posts: 2,416
    edited July 15

    Well, I haven't downloaded the studio 2025. Maybe I will. If I do, I'll check it out there. It's still an alpha version, isn't it? How does it run? 

    Post edited by inquire on
  • memcneil70memcneil70 Posts: 5,237
    edited July 15

    @inquire, I would recommend reading the Evergreen thread first. I did and I am no way a programmer and it helped prepare me for what I might expect in DS2025/6. 

    Issues are being reported in the Alpha thread which today is up to page 28. Some of the issues have been addressed and one I found on the last update will be fixed on a future update. Just be prepared that scripts and plugins do not work at this time. There is a lot of discussion as to why. It is reasonable. It can be used, but be prepared to work on a file in DS6 and maybe have to save/close and reopen it in DS4 to use your scripts and plugins to fix something. 

    It is a point of testing and not for a perfect experience that we find in the regular releases. It is an Alpha. The layout is slightly different. But that kind of makes it fun too.

    Mary

    Post edited by memcneil70 on
  • inquireinquire Posts: 2,416

    Well, but it takes scripts to apply the bone minion, which is what I'm working with now. And if this alpha version won't support scripts, then I wouldn't be able to apply bone minion.

  • inquireinquire Posts: 2,416
    edited July 17

    I tried to open poser pro 11 on my new Mac studio for the first time yesterday. It asked if poser could have access to my documents folder and I clicked allow. But once open, I couldn't get poser to open any item from its libraries.

    I wanted to use an item by the vendor Pandorian. It's a wrestling ring. I decided to open it in Daz Studio. I did so. But the item has ropes that can morph up down sideways, etc. I could not get any of the morphs to work. I looked in the parameters tab, and none of the morphs showed. Clicking on the roaps in the viewport Did nothing. In fact, that only meant I had selected the entire ring.

    So what's going on? That item can be bought again on another site, but would that do any good?

    I'm stumped. Is there a way around this? I have that wrestling ring on my computer, and I have used it in studio before. Why won't it work this time?

    this is Studio 4, Not studio 2026.

    Post edited by inquire on
  • TotteTotte Posts: 14,677

    Is it rigged using the old model or the Poser version of weight mapping? The latter doesn't work in DS 

  • inquireinquire Posts: 2,416

    Well, I bought it back in 2007, I believe, and it worked in poser 11. I think that's the old version. I'm not really sure what you mean by rigging. But I can't even get the poser App to access any of its own libraries.

  • inquireinquire Posts: 2,416

    I did get the wrestling ring to work in DAZ Studio.

    I know this isn't a group for poser, but I don't understand why the app will open up, but I can't access any of the libraries. If anyone in here has used poser, Maybe you would know. This is poser 11 pro running in Rosetta 2 in Sequoia 15.5.

  • inquireinquire Posts: 2,416

    Glad to report that I got the poser pro 11 Situation figured out. Now I've got all the runtimes linked up and can bring in whatever figure or prop I wish.

    I'm wondering if I'm good enough to try out  DAZ Studio 2026. I'd like to try that suggestion that Westerndan Mentioned.

  • inquireinquire Posts: 2,416
    edited July 18

    Now, I just wanna check one more time: If I download that alpha 2026 DAZ Studio, It should be easy for me to delete it if I don't like it. It should not mess up my new Mac studio running Sequoia 15.5. Is that correct? Sorry for being such a scaredy-cat, but I've never run two versions of Studio.  Maybe I just feel a little boulder because I did solve how to get the wrestling ring working in DAZ Studio and how to get poser all linked up again so that it also works.

    I am also pretty tired of having a pause each time. I try to move some Genesis 9 figures. Perhaps it's because the viewport uses only one core in the Rosetta 2 version of studio 4. Hopefully, the alpha version of studio will be better. And I'm tired of having studio crash or  not be able to reopen saved scenes if I've added things on to characters such as bone minion.

    Post edited by inquire on
  • TotteTotte Posts: 14,677

    I have 7 different studio installations.. no problem 

  • inquireinquire Posts: 2,416

    Where do I find the place to download the alpha version of studio?

  • memcneil70memcneil70 Posts: 5,237
    edited July 19

    In DIM, go to the Downloads tab and tick on DAZ Studio 2025 (6.x). Do not change your other selections you currently have for DAZ Studio so you will continue to receive updates to the current release.

    You should already have the platform tags you use ticked.

    And make sure you Release Channel Tags are ticked too.

    Post edited by memcneil70 on
  • inquireinquire Posts: 2,416

    Thank you very much for answering. I think I've bolted up just about enough daring to do it. I think I understand your directions, however if you look in the file, I'm about to attach it shows things like the Dyson importer for poser, the install manager, and poser 9+. Do I want to leave these checked?

    DIM.png
    836 x 872 - 252K
  • memcneil70memcneil70 Posts: 5,237

    If you are using Poser on your machine, or use Poser products in DAZ Studio you do want to have Poser selected. I have a large number of the older Poser products still installed and use them fairly often. Especially Faveral's sets.

Sign In or Register to comment.