Jump to content

Henrik Norin

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Henrik Norin

  1. Hi Peter, We have had a look at your logs and there seems to be a Houdini launcher created and should be available within ftrack: ftrack_application_launcer:log:970: DEBUG - MainThread - 2021-10-14 16:42:00,134 - 118 - ftrack_application_launcher.discover_applications.DiscoverApplications - Creating App launcher <label:Houdini|id:ftrack-connect-launch-houdini|variant:None> with priority 100 As there is py3 builds of Houdini, we are planning to have a rc4 with improved Houdini launch out within the next couple of days. I would suggest you try this out and then lets see if the problem persists, will reach out to you as soon as we have the release available at the forum. Cheers /Henrik
  2. Hi Aline, You would need to create both the event and the related project and/or users within the same transaction, e.g: ce=session.create('CalendarEvent',{'name':'TEST_PIPELINE','start': arrow.get('2021-08-25'),'end': arrow.get('2021-08-31')}) user=session.query('User where username is "aline3d"').first() event = session.create('CalendarEventResource',{'calendar_event_id':ce['id'],'resource_id':user['id']}) session.commit() Cheers /Henrik
  3. Hi, I verified your code and could not get the issue you are reporting (testing on 4.7.0.current.13.277). Could you please create a ticket at support@ftrack.com and supply your ftrack details - ftrack url (and version, if onprem). Cheers /Henrik
  4. Hi Yating, Answers to your questions: This is a confirmed bug, will be fixed for next release. Tried to replicate it but no luck, could be unsupported alembic format. Could you share the file? Also a confirmed bug, will be fixed for next release. Yes, the label should be "Houdini nodes" not "Houdini binary", dictating if selected/all nodes also should be exported to a .hip. "Attach scene to asset" will generate a new scene containing selected/all nodes. Import creates a new subnet node and import all the nodes beneath, while merge imports the nodes into the current scene with risk of possible node name conflicts. We can't replicate the issue you have with Import generating an empty node, could you share the .hip? Cheers /Henrik
  5. FYI, this has been discussed and explained in a separate thread: https://forum.ftrack.com/topic/677-sessiongettypedcontext-entity_id-not-working/?tab=comments#comment-3584
  6. Hi Yating, We will look into this matter and come back to you. Cheers /Henrik
  7. Hello Yating, First, you mentioned you were trying out 0.3.1 but that version is not shipped with Connect package 1.1.2 (were your first traceback originates from). Could you try once more after downloading the latest Houdini integration here and replacing the dated within "C:\Program Files (x86)\ftrack-connect-package-1.1.2\resource\connect-standard-plugins"? Cheers /Henrik
  8. Hi, Forgot to point out that events also can be queried by the API: https://bitbucket.org/ftrack/workspace/snippets/ggyrb/api-example-working-with-events Cheers /Henrik
  9. Hi, This is available as an advanced configuration option for ftrack on-prem deployments: http://help.ftrack.com/en/articles/1040523-configuring-server-options#fetch-update-events-directly-from-internal-queue Cheers /Henrik
  10. Hello Peter, This PR make sense, I will create one and take it further with our QC team. Thanks /Henrik Norin ftrack staff
  • Create New...