MacOS Bridge 1.2 OSError: [Errno 20]
gene4ka
Posts: 1
In the console Cinema 4D error
Traceback (most recent call last): File "/Applications/Maxon Cinema 4D R22/plugins/DazToC4D/lib/DtC4DWindow.py", line 316, in Command sss_value, normal_value, bump_value File "/Applications/Maxon Cinema 4D R22/plugins/DazToC4D/lib/CustomImports.py", line 47, in auto_import_genesis fbx_path = dtu.get_fbx_path() File "/Applications/Maxon Cinema 4D R22/plugins/DazToC4D/lib/DtuLoader.py", line 62, in get_fbx_path self.load_fbx_path() File "/Applications/Maxon Cinema 4D R22/plugins/DazToC4D/lib/DtuLoader.py", line 57, in load_fbx_path dtu_dict = self.get_dtu_dict() File "/Applications/Maxon Cinema 4D R22/plugins/DazToC4D/lib/DtuLoader.py", line 35, in get_dtu_dict self.load_dtu() File "/Applications/Maxon Cinema 4D R22/plugins/DazToC4D/lib/DtuLoader.py", line 26, in load_dtu for file in os.listdir(self.import_dir):OSError: [Errno 20] Not a directory: '/Users/xxxx/Documents/DAZ 3D/Bridges/Daz To Cinema 4D/Exports/FIG/.DS_Store'>>>
I tested it on Cinema 4d R17 and S22
Post edited by gene4ka on
Comments
Which install manager did you use to install this bridge? It appears from this error code that the files for this script were installed within to your Cinema 4D R22 plugins folder. As you are intending to use this bridge with R17, I would recommend uninstalling this bridge via DIM or Daz Connect and then installing this bridge manually.
To do this for R17, start by downloading the bridge from the Daz to C4D GitHub here:
https://github.com/daz3d/DazToC4D/releases/tag/1.3.0 -- and scroll to the bottom of the updates listed for this latest release, then download the .zip file for the source code to begin manually installing the folder containing both the Daz Studio and Cinema 4D R17 paths, respectively. Then, unzip this DazToC4D-1.3.0 folder from within the downloads folder (to your desktop), and then install the corresponding files to these locations using File Explorer. Unfortunately, I don't have a Mac OS to test these on, so I'll be listing these instructions for a Windows machine.
To begin mapping the install paths for this bridge version for Daz Studio, navigate within the unzipped DazToC4D-1.3.0 folder to:
DazToC4D-1.3.0\Daz Studio\appdir_common\scripts\support\DAZ --> and copy the entire DAZ folder. Then, type "%appdata%" within the top of your File Explorer (please note, if you install DS on another drive, this drive must first be selected); and then within this Roaming folder navigate to:
Daz 3D --> Studio4 --> RunOnce --> and finally, paste the DAZ folder here (copied earlier from DazToC4D-1.3.0).
To map the install paths for this bridge version for Cinema 4D, navigate within the unzipped DazToC4D-1.3.0 folder to:
DazToC4D-1.3.0\Cinema 4D\appdir_common\plugins and copy the entire DazToC4D folder. Then, navigate to within your system files where Cinema 4D version R17 is installed (by default, similar to: C:\Program Files\Maxon Cinema 4D R17) and then navigate to --> \Plugins and paste the entire DazToC4D folder here (copied earlier from DazToC4D-1.3.0). If you do not have a Plugins folder here, create one and paste the aforementioned DazToC4D folder here.
Once you have place installed these files to their corresponding locations, the Daz to Cinema 4D bridge should now be installed for version R17 and available within Daz Studio under Scripts --> Bridges --> Daz to Cinema 4D.
Hello! Thanks for the answer. I could not find where to write a bug report, so I wrote on the forum.
I think that this is not an error of incorrect installation of the bridge from the Daz to C4D.
I googled and found this explanation on stackoverflow:
os.listdir() will give you every single file in the directory, including hidden files like .DS_Store.
It is worth to mention what is the general meaning of the "Not a directory" error (Errno 20). It means that you are trying to operate with a path which sub-path is a real file and not a directory. This error is Unix OS specific.
I used DIM and manual installation by downloading from github
I'm sorry it's my fault, English is not my native language, so you misunderstood me.I tested this on two computers, my old computer with Cinema 4D R17 and new computer with Cinema 4D R22 (S22)
sorry this version doesn't work either
Cinema 4D R17
Cinema 4D S22
P.S. Bridge version 1.1 works fine.
Best regards, Eugenia