Loading...
> >

Can't open my daz duffs on my Mac laptop. Please help.

freni-kynfreni-kyn Posts: 394
in The Commons

I've saved some duffs on my pc but wanted to work on them on the mac laptop while I had things rendering on the pc.  For some reason it is turning a lot of the clothing and even some morphs into blocks and gives me the message that it can't find something or it needs to be installed.  The mac accesses the exact same folder (share drive) as the pc does for files so I am not sure what I'm doing wrong.

Comments

  • Richard HaseltineRichard Haseltine Posts: 108,176

    Are you sure the content directories are set the same on both? One possibility would be that oen of the sets was pointing a level too high or two deep in the folder hierarchy. Also, since it's an external drive, make sure that the mac is really seeing the drive on its usual path - if it's seeing it as a different drive then of course it won't look there for the content.

  • freni-kynfreni-kyn Posts: 394
    Richard Haseltine said:

    Are you sure the content directories are set the same on both? One possibility would be that oen of the sets was pointing a level too high or two deep in the folder hierarchy. Also, since it's an external drive, make sure that the mac is really seeing the drive on its usual path - if it's seeing it as a different drive then of course it won't look there for the content.

    Yes the content directories are the same.  I even went in and updated them to make sure.  It's not an external drive, it's on my hdrive, within my desktop.  I have three desks butted up to each other so I can have several comps running at one time.  I will check to see that it is seeing it correctly.  That had not occured to me.  I did make sure all the pertinent folders were shared.

  • freni-kynfreni-kyn Posts: 394
    Richard Haseltine said:

    Are you sure the content directories are set the same on both? One possibility would be that oen of the sets was pointing a level too high or two deep in the folder hierarchy. Also, since it's an external drive, make sure that the mac is really seeing the drive on its usual path - if it's seeing it as a different drive then of course it won't look there for the content.

    You were completly correct.  I can not figure out a way to make this work so I guess I will work on separate projects on it.  Thanks for pointing me in the right direction.

  • TotteTotte Posts: 14,716

    Do the .dufs contain any items if the type.daz ? Thay would explain your issues. 

  • freni-kynfreni-kyn Posts: 394
    Totte said:

    Do the .dufs contain any items if the type.daz ? Thay would explain your issues. 

    Not sure what you mean. 

  • TotteTotte Posts: 14,716
    freni-kyn said:
    Totte said:

    Do the .dufs contain any items if the type.daz ? Thay would explain your issues. 

    Not sure what you mean. 

    If the dufs you saved (scenes containing various items(, contains items of the type .daz, this is what happens, it can also happen if the data folder cannot be located.

  • freni-kynfreni-kyn Posts: 394
    Totte said:
    freni-kyn said:
    Totte said:

    Do the .dufs contain any items if the type.daz ? Thay would explain your issues. 

    Not sure what you mean. 

    If the dufs you saved (scenes containing various items(, contains items of the type .daz, this is what happens, it can also happen if the data folder cannot be located.

    Well this just shows how little I know about the mac.  lol  My husband explained to me that even though the laptop is accessing the exact same files as I am on my desktop, it sort of renames them to fit the mac file system.  As in, the H drive that my stuff sits on is not labeled a H drive on the mac laptop.  So basically I'm screwed.  With the advances that mac had made in compatibility I had no idea that the file system was still going to be an issue. Since he set it up for me I did not see the issue until I tried to load a duf and daz didn't know where things were.  I've decided to use the laptop to create new works, which should also lower my down time while rendering.  I'm also considering some cheap laptops with nvidia cards in them to send things off to render on.  Never in a million years would have predicted a day when I would need a bunch of computers to keep me happy. 

  • TotteTotte Posts: 14,716
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:

    Do the .dufs contain any items if the type.daz ? Thay would explain your issues. 

    Not sure what you mean. 

    If the dufs you saved (scenes containing various items(, contains items of the type .daz, this is what happens, it can also happen if the data folder cannot be located.

    Well this just shows how little I know about the mac.  lol  My husband explained to me that even though the laptop is accessing the exact same files as I am on my desktop, it sort of renames them to fit the mac file system.  As in, the H drive that my stuff sits on is not labeled a H drive on the mac laptop.  So basically I'm screwed.  With the advances that mac had made in compatibility I had no idea that the file system was still going to be an issue. Since he set it up for me I did not see the issue until I tried to load a duf and daz didn't know where things were.  I've decided to use the laptop to create new works, which should also lower my down time while rendering.  I'm also considering some cheap laptops with nvidia cards in them to send things off to render on.  Never in a million years would have predicted a day when I would need a bunch of computers to keep me happy. 

    This really sounds like a flawed setup, sorry. 

    Here is a quick description how things works "internally", at least what I've fugured out by studiying how things behave.

    When you save a scene - the scene contains referenses to the items you use, those referenses are saved as references to /data/sometghing/something/something. As log as the items are ,duf, the only thing that can prevent an item to work across paths is if the content libraries are differnt or the mapping is different. The content is totally ignorant to the fact that some systems uses drive letters and other start all paths with /, everything is locally seaarched from the Content directory roots.

    So, if it doesn't work these are the possible errors in the setup:
    (1) The content is not installed correctly in both systems
    (2) The content directories are not correctly setup on both systems

    What you should not try to do, is to link to the content directory on one machine from the other machine (by adding the mounted directory as a content directory), that is bound to fail, specially when mounting from the OS X machine, as whenever the Windows box (or a remote disk) does AWOL for a while, then comes back, it's remounted under another name, but the Finder cleverly hides that from you.

    To see that, use the terminal and do cd /Volumes 
    The list the directory (which is a pain to type in the forums due to the hacker protection), but I try: ls -ls

  • freni-kynfreni-kyn Posts: 394
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:

    What you should not try to do, is to link to the content directory on one machine from the other machine (by adding the mounted directory as a content directory), that is bound to fail, specially when mounting from the OS X machine, as whenever the Windows box (or a remote disk) does AWOL for a while, then comes back, it's remounted under another name, but the Finder cleverly hides that from you.

    To see that, use the terminal and do cd /Volumes 
    The list the directory (which is a pain to type in the forums due to the hacker protection), but I try: ls -ls

    This is exactly what I have been doing. I simply share the h drive on my primary computer with the Mac. Since that seems to work fine I also thought I could share my dufs.  

  • TotteTotte Posts: 14,716
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:

    What you should not try to do, is to link to the content directory on one machine from the other machine (by adding the mounted directory as a content directory), that is bound to fail, specially when mounting from the OS X machine, as whenever the Windows box (or a remote disk) does AWOL for a while, then comes back, it's remounted under another name, but the Finder cleverly hides that from you.

    To see that, use the terminal and do cd /Volumes 
    The list the directory (which is a pain to type in the forums due to the hacker protection), but I try: ls -ls

    This is exactly what I have been doing. I simply share the h drive on my primary computer with the Mac. Since that seems to work fine I also thought I could share my dufs.  

    You should, but as I said before, it depends on what items are in those, if they contain items of .daz formats or not, or if as I said later, the drive las been lost and found.

     

  • freni-kynfreni-kyn Posts: 394
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:

    What you should not try to do, is to link to the content directory on one machine from the other machine (by adding the mounted directory as a content directory), that is bound to fail, specially when mounting from the OS X machine, as whenever the Windows box (or a remote disk) does AWOL for a while, then comes back, it's remounted under another name, but the Finder cleverly hides that from you.

    To see that, use the terminal and do cd /Volumes 
    The list the directory (which is a pain to type in the forums due to the hacker protection), but I try: ls -ls

    This is exactly what I have been doing. I simply share the h drive on my primary computer with the Mac. Since that seems to work fine I also thought I could share my dufs.  

    You should, but as I said before, it depends on what items are in those, if they contain items of .daz formats or not, or if as I said later, the drive las been lost and found.

     

    He says it is not finding a new drive each time so that is not the issue.  Thanks for your input on this.  We are looking at purchasing a new computer so that I have a second pc that I can use for this.  Dealing with the mac issues is too annoying for me.  Shame because it renders faster.

  • TotteTotte Posts: 14,716
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:

    What you should not try to do, is to link to the content directory on one machine from the other machine (by adding the mounted directory as a content directory), that is bound to fail, specially when mounting from the OS X machine, as whenever the Windows box (or a remote disk) does AWOL for a while, then comes back, it's remounted under another name, but the Finder cleverly hides that from you.

    To see that, use the terminal and do cd /Volumes 
    The list the directory (which is a pain to type in the forums due to the hacker protection), but I try: ls -ls

    This is exactly what I have been doing. I simply share the h drive on my primary computer with the Mac. Since that seems to work fine I also thought I could share my dufs.  

    You should, but as I said before, it depends on what items are in those, if they contain items of .daz formats or not, or if as I said later, the drive las been lost and found.

     

    He says it is not finding a new drive each time so that is not the issue.  Thanks for your input on this.  We are looking at purchasing a new computer so that I have a second pc that I can use for this.  Dealing with the mac issues is too annoying for me.  Shame because it renders faster.

    Can you show what the studio log says?

     

  • freni-kynfreni-kyn Posts: 394
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:
    freni-kyn said:
    Totte said:

    What you should not try to do, is to link to the content directory on one machine from the other machine (by adding the mounted directory as a content directory), that is bound to fail, specially when mounting from the OS X machine, as whenever the Windows box (or a remote disk) does AWOL for a while, then comes back, it's remounted under another name, but the Finder cleverly hides that from you.

    To see that, use the terminal and do cd /Volumes 
    The list the directory (which is a pain to type in the forums due to the hacker protection), but I try: ls -ls

    This is exactly what I have been doing. I simply share the h drive on my primary computer with the Mac. Since that seems to work fine I also thought I could share my dufs.  

    You should, but as I said before, it depends on what items are in those, if they contain items of .daz formats or not, or if as I said later, the drive las been lost and found.

     

    He says it is not finding a new drive each time so that is not the issue.  Thanks for your input on this.  We are looking at purchasing a new computer so that I have a second pc that I can use for this.  Dealing with the mac issues is too annoying for me.  Shame because it renders faster.

    Can you show what the studio log says?

     

    I will the next time I attempt to use it. 

Sign In or Register to comment.