Should I download DAZ Studio 4.8 32-Bit Version or 64-Bit Version? Which one is best for me?

I use a Mac OS X (Macbook Pro) 13-inch, Early 2011

Here are my specs:

Version 10.8.5 (Mountain Lion) 

Processor: 2.3 GHz Intel Core i5

Memory: 4 GB 1333 MHz DR3

Graphics: Intel HD Graphics 3000 384 MB

Which version would be best for me? Daz Studio 32-Bit or 64-Bit?

Please provide any information and/or advice for me, thank you.

ESK

 

Comments

  • TotteTotte Posts: 14,064
    edited December 2015

    64 bit, no question about it. OS X since 10.5 (Leopard) runs 32 bit and 64 bit side by side. With 32-bit you might be able to load a GF3 and a hair, that's about it. But your RAM is on the weaker side, 4GB RAM, I would say don't do any larger scenes....

     

    / Totte

     

    Post edited by Totte on
  • Totte said:

    64 bit, no question about it. OS X since 10.5 (Leopard) runs 32 bit and 64 bit side by side. With 32-bit you might be able to load a GF3 and a hair, that's about it. But your RAM is on the weaker side, 4GB RAM, I would say don't do any larger scenes....

     

    / Totte

    I've already downloaded the 32-bit version about couple weeks ago. Should I uninstall it and install the 64-bit? 

     

  • TotteTotte Posts: 14,064
    Totte said:

    64 bit, no question about it. OS X since 10.5 (Leopard) runs 32 bit and 64 bit side by side. With 32-bit you might be able to load a GF3 and a hair, that's about it. But your RAM is on the weaker side, 4GB RAM, I would say don't do any larger scenes....

     

    / Totte

    I've already downloaded the 32-bit version about couple weeks ago. Should I uninstall it and install the 64-bit? 

     

    You don't need to uninstall as long as you refrain from running them at the same time, but you could uninstall, but only the application and the 32bit plugins you have downloaded that must be 64 bit (software plugins).

  • If you have the room I recommend installing both 32-bit and 64-bit versions on your system. My experience is that I run the 64-bit version the vast majority (99%) of the time given the projects I have been working on the past few months. However, there are features within the 32-bit version, mainly the ability to lip-sync a lot of your models, that when I need I find invaluable to already have installed.

    Also, the key to any 64-bit vs 32-bit software is if your system is 64-bit you will generally be able to more efficiently and effectively run that software. As a general rule-of-thumb you should always want to install a 64-bit app if you have a 64-bit system.

  • No, no no, no!!!!!! If you only have 4GB of ram use the 32 bit version you can fit more in your memory.

    the 32 bit version have 4 byte size pointers while the 64 bit version use 8 byte pointer size so everything use more memory, yes the same geometry will use more memory on the 64 bit version, and with only 4GB you have no advantage at all of the 64 bit version.

     

  • TotteTotte Posts: 14,064

    No, no no, no!!!!!! If you only have 4GB of ram use the 32 bit version you can fit more in your memory.

    the 32 bit version have 4 byte size pointers while the 64 bit version use 8 byte pointer size so everything use more memory, yes the same geometry will use more memory on the 64 bit version, and with only 4GB you have no advantage at all of the 64 bit version.

    That is not entirely true, as the 32Bit version will only use 2GB RAM.

  • Ah, if that's correct (Apple developers always complain that Windows has severe limitations because it map kernel into user space and can only access a small portion of the 4GB to the application smiley ) then I am wrong, go with the 64 bit version.

  • TotteTotte Posts: 14,064

    Ah, if that's correct (Apple developers always complain that Windows has severe limitations because it map kernel into user space and can only access a small portion of the 4GB to the application smiley ) then I am wrong, go with the 64 bit version.

    The issue with windows in 32 bit mode is that the total amount of allocatable RAM is limited while on OS X each application can allocate up to 2GB, but if you have 16GB RAM and 8 32 bit applications each can allocate up to 2GB RAM each, while on Windows the total amount of allocatable RAM is limited to 4GB

  • Totte said:

    Ah, if that's correct (Apple developers always complain that Windows has severe limitations because it map kernel into user space and can only access a small portion of the 4GB to the application smiley ) then I am wrong, go with the 64 bit version.

    The issue with windows in 32 bit mode is that the total amount of allocatable RAM is limited while on OS X each application can allocate up to 2GB, but if you have 16GB RAM and 8 32 bit applications each can allocate up to 2GB RAM each, while on Windows the total amount of allocatable RAM is limited to 4GB

    Alright, so I uninstalled the 64-Bit version and now I'm downloading the 64-bit version. What does  the 64-bit have that 32-bit doesn't? 

  • Totte said:

    Ah, if that's correct (Apple developers always complain that Windows has severe limitations because it map kernel into user space and can only access a small portion of the 4GB to the application smiley ) then I am wrong, go with the 64 bit version.

    The issue with windows in 32 bit mode is that the total amount of allocatable RAM is limited while on OS X each application can allocate up to 2GB, but if you have 16GB RAM and 8 32 bit applications each can allocate up to 2GB RAM each, while on Windows the total amount of allocatable RAM is limited to 4GB

    Alright, so I uninstalled the 64-Bit version and now I'm downloading the 64-bit version. What does  the 64-bit have that 32-bit doesn't? 

    It lets a complex or busy scene load and render, as long as you have enough RAM; the 32 bit version will fail if the scene gets too large (and they can. easily).

  • TotteTotte Posts: 14,064
    Totte said:

    Ah, if that's correct (Apple developers always complain that Windows has severe limitations because it map kernel into user space and can only access a small portion of the 4GB to the application smiley ) then I am wrong, go with the 64 bit version.

    The issue with windows in 32 bit mode is that the total amount of allocatable RAM is limited while on OS X each application can allocate up to 2GB, but if you have 16GB RAM and 8 32 bit applications each can allocate up to 2GB RAM each, while on Windows the total amount of allocatable RAM is limited to 4GB

    Alright, so I uninstalled the 64-Bit version and now I'm downloading the 64-bit version. What does  the 64-bit have that 32-bit doesn't? 

    The Ability to use more than 2GB RAM 

  • StratDragonStratDragon Posts: 3,251

    2GB RAM utilization of a  32bit application is a 32 bit Windows limitation (it can be switched to 3) but Mac OS (10.5 and up) utilizes up to 4GB RAM for a single 32 bit application. That being said RAM appears to be eaten very quickly on Mac in Studio and the early 2011 MBP supports up to 16GB of PC3-10600 DDR at 1333MHz.

    Do that if cost allows, and go 64 bit.

  • TotteTotte Posts: 14,064

    2GB RAM utilization of a  32bit application is a 32 bit Windows limitation (it can be switched to 3) but Mac OS (10.5 and up) utilizes up to 4GB RAM for a single 32 bit application. That being said RAM appears to be eaten very quickly on Mac in Studio and the early 2011 MBP supports up to 16GB of PC3-10600 DDR at 1333MHz.

    Do that if cost allows, and go 64 bit.

    Server applications without GUI or Applications using the Cococa-APIs might handle it, on the right hardware, but application using Carbon-32 APIs most certainly won't.

     

  • StratDragonStratDragon Posts: 3,251
    Totte said:

    2GB RAM utilization of a  32bit application is a 32 bit Windows limitation (it can be switched to 3) but Mac OS (10.5 and up) utilizes up to 4GB RAM for a single 32 bit application. That being said RAM appears to be eaten very quickly on Mac in Studio and the early 2011 MBP supports up to 16GB of PC3-10600 DDR at 1333MHz.

    Do that if cost allows, and go 64 bit.

    Server applications without GUI or Applications using the Cococa-APIs might handle it, on the right hardware, but application using Carbon-32 APIs most certainly won't.

     

    We had instance of 32 bit Quark 6 utilizing over 3GB RAM in Tiger, but I dont know what it was built off of. 

  • One thing to know about the difference between the 32-bit and 64-bit on the Mac... if you want to use Mimic, it's only available in the 32-bit version. They never updated the plugin for the 64-bit version. If you have the ram, then the 64-bit will run smoother and faster. If you don't, then 32-bit would be fine. On a 4GB machine, 2GB is pretty much used up by the system and finder, so you only have about 2GB available at any one time.

    However, both programs are handled well by the Mac OS virtual memory setup. 64-bit can take advantage of this better. If you have an SSD drive, the the amount of ram you have isn't as important, still important, just not as much. The SSD drive will run close to the speed of your ram, so any virtual memory will keep up pretty well. More ram is still better, but SSD's help a ton with speed issues on older Macs.

  • StratDragonStratDragon Posts: 3,251
    edited December 2015
    MacSavers said:

    One thing to know about the difference between the 32-bit and 64-bit on the Mac... if you want to use Mimic, it's only available in the 32-bit version. They never updated the plugin for the 64-bit version. If you have the ram, then the 64-bit will run smoother and faster. If you don't, then 32-bit would be fine. On a 4GB machine, 2GB is pretty much used up by the system and finder, so you only have about 2GB available at any one time.

    However, both programs are handled well by the Mac OS virtual memory setup. 64-bit can take advantage of this better. If you have an SSD drive, the the amount of ram you have isn't as important, still important, just not as much. The SSD drive will run close to the speed of your ram, so any virtual memory will keep up pretty well. More ram is still better, but SSD's help a ton with speed issues on older Macs.

    SSD's have limited writes you may not wish to utilize the drive for swap files. NAND does not make a good alternative to RAM in fact I would think it could cause the drive to have a severely compensated lifespan with all the R/W/X necessary for swap

    Post edited by StratDragon on
Sign In or Register to comment.