Jump to content

Henrik Norin

Administrators
  • Posts

    10
  • Joined

  • Last visited

  • Days Won

    2

Posts 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 Yating,

     

    Answers to your questions:

     

    1. This is a confirmed bug, will be fixed for next release.
    2. Tried to replicate it but no luck, could be unsupported alembic format. Could you share the file?
    3. Also a confirmed bug,  will be fixed for next release.
    4. 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. 
    5. 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

  4. 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

×
×
  • Create New...