tan ya ting

Hi, May I know if there's any updates with regards to this matter?

Thanks for this. We'll give it a try and update here again.

yea man. After downloading and reinstalling the houdini package 0.3.1, it's not working still. Still getting the errors

Hi Henrik, Thanks for the reply! but I'm alittle confused here haha. If houdini connect 0.3.1 is not shipped with ftrack connect package 1.1.2, then which version of the houdini connect should I be looking for installation? The link attached above in the reply is houdini connect 0.3.1 , which is the one i'm using for the test though. Here are the ftrack connect and houdini connect version that I'm using: -ftrack connect 1.1.8 -ftrack connect package 1.1.2 -ftrack connect houdini: 0.3.1 Nonetheless, I'll try reinstalling the houdini package! Will get back to you againn

Hi Steve, Thanks for responding. Unfortunately It's alittle tricky to update the deadline version right now as we're still in the middle of rendering for a job. I'll give that a try once the job is finished! I've tried plugging in the URL from the browser, got "internal server error occurred". 😶

Hi Guys, I'm trying the Houdini Connect Plugin (ftrack-connect-houdini-0.3.1) and I need some clarifications and help with some issues that I'm facing. With regards to Publishing: 1. failed publish of geometry type (fbx) in houdini, with the following error in houdini console. on the other hand. I was able to export the fbx fine with the native houdini plugin (file>Export>FilmboxFBX) Traceback (most recent call last): File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins\ftrack-connect-houdini-0.3.1\dependencies\ftrack_connect_houdini\ui\publisher.py", line 189, in publishAsset publishedComponents, message = self.connector.publishAsset(pubObj) File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins\ftrack-connect-houdini-0.3.1\dependencies\ftrack_connect_houdini\connector\houdinicon.py", line 122, in publishAsset publishedComponents, message = pubAsset.publishAsset(iAObj) File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins\ftrack-connect-houdini-0.3.1\dependencies\ftrack_connect_houdini\connector\houdiniassets.py", line 432, in publishAsset fbxRopnet.parm('sdkversion').set(GenericAsset.parseComboBoxNameValue(iAObj.options.get('fbxSDKVersion'))) TypeError: unbound method parseComboBoxNameValue() must be called with GenericAsset instance as first argument (got unicode instance instead) With regards to Importing: 2. failed import of ALEMBIC files in houdini using "merge" option, with the following error in houdini console. Traceback (most recent call last): File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\common.zip\ftrack_connect\ui\widget\import_asset.py", line 172, in importSelectedComponents File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\common.zip\ftrack_connect\ui\widget\import_asset.py", line 220, in onImportComponent File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins\ftrack-connect-houdini-0.3.1\dependencies\ftrack_connect_houdini\connector\houdinicon.py", line 55, in importAsset result = importAsset.importAsset(iAObj) File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins\ftrack-connect-houdini-0.3.1\dependencies\ftrack_connect_houdini\connector\houdiniassets.py", line 321, in importAsset GenericAsset.importAsset(self, iAObj) File "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins\ftrack-connect-houdini-0.3.1\dependencies\ftrack_connect_houdini\connector\houdiniassets.py", line 91, in importAsset 'alembicarchive', iAObj.assetName) File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.391/houdini/python2.7libs\houpythonportion\ui.py", line 927, in decorator return func(*args, **kwargs) File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.391/houdini/python2.7libs\hou.py", line 9377, in createNode return _hou.Node_createNode(*args, **kwargs) hou.OperationFailed: The attempted operation failed. Invalid node name 3. failed import of houdini binary scene file (published using geotype) using the merge option as well. Needs Clarification: 4. What's the difference between the houdini binary scene format and normal houdini .hip format? Are there any benefits of publishing [geometry] using houdini scene options? Cause from what I can see, it seems to function the same way as a normal houdini .hip format 5. Lastly Importing of published houdini scenes using the ftrack connect works fine! But can I clarify on what's the difference between using the "import" vs "merge" options for importing scene files? (.hip) As "merge" seems to work fine in importing the contents of the .hip file, but "import" option brings in an empty null instead. *attached images below for reference... Sorry for the spam of questions hahha 😅 Thanks in advance for any insight! -Yating

Hey guys, Hope this is the correct place to be asking questions, I’ve been trying to setup and test the ftrack connect in my company and I'm facing some issues. For integration of Ftrack in Deadline for Maya, I'm getting errors in "attempting to retrieve user from ftrack" when submitting a maya job with the integrated submission script. When i click on “connect user” in Deadline submitter > maya pipeline tool > project management , I met with the following error: Retrieving sticky settings… done! UNEXPECTED ERROR: <class ‘xmlrpclib.ProtocolError’> ProtocolError for #####.ftrackapp.com/client/: 404 Not Found I’ve already configured the deadline events plugin for ftrack, inserting ftrack URL and the API key generated from ftrack. The state was switched to “Global Enabled” as well. I've posted in the deadline forums as well but didn't seem to get any response from the guys there. Really appreciate any insights in getting this to work! Thank you!! ☺️ Cheers, Yating Versions: Deadline Client Version: 10.0.28.2 ftrack-connect-package-1.1.2 ftrack-connect-maya-1.3.0