When you edit HDAs, you do it per node, one at a time. There's no 'maya reference editor' style thing to get a central overview of all HDAs used in the hip.As well as dumping a bunch of nodes to an external location, you can also put parameters on the top of the hda to control nodes within it, which is a trick you can't do with maya references.Saving and updating is kind of magical and in-place, needs a mild leap of faith to trust its working.You can't just go File -> Export on a bunch of nodes, you need to use the HDA workflows to export.They have a few features that make them a little more complicated than maya references: You export a chunk of a hip to an external file (eg c:/projects/library/coolthing.hda), now those nodes live somewhere else on disk, and you can bring them into your hip like a reference. 4 Load $HIP/hda on hip load via hou.sessionĪ Houdini Digital Asset is like a maya reference.3 Lock states, editing and saving and reverting hdas.
#Cant type in houdini engine maya software#
Please contact other problem is that, in Maya, the files created before the use of the Software Entity still have a Context with the Entity set to the Asset, even when deleting their caches, when all new Entities have the Software as Context’s Entity. Error: Message: Shotgun encountered a problem changing the Engine’s context. Usually this is because the context contains insufficient information for an environment to be determined. TankEngineInitError: Engine tk-maya cannot initialize - the pick environment hook was not able to return an environment to use, given the context model, Software Maya. “for an environment to be determined.” % (engine_name, context) Refresh_engine(engine_name, prev_context, menu_name)įile “/app/user/alefeve/package/tk_core/0.19.6-sps.1.0/studio/install/app_store/tk-maya/v0.10.1/engine.py”, line 199, in refresh_engineįile “/app/user/alefeve/package/tk_core/0.19.6-sps.1.0/studio/install/core/python/tank/platform/engine.py”, line 778, in change_contextĮngine_name=self.instance_name, tk=self.tank, context=new_contextįile “/app/user/alefeve/package/tk_core/0.19.6-sps.1.0/studio/install/core/python/tank/platform/engine.py”, line 3382, in get_env_and_descriptor_for_engineĮnv_name = _pick_environment(engine_name, tk, context)įile “/app/user/alefeve/package/tk_core/0.19.6-sps.1.0/studio/install/core/python/tank/platform/engine.py”, line 3429, in _pick_environment Usually this is because the context contains insufficient information for an environment to be determined.’įile “/app/user/alefeve/package/tk_core/0.19.6-sps.1.0/studio/install/app_store/tk-maya/v0.10.1/engine.py”, line 208, in on_scene_event_callback Error: Shotgun 1f5a04b23213444fbb414ee500050260: Could not refresh the engine error: ‘Engine tk-maya cannot initialize - the pick environment hook was not able to return an environment to use, given the context model, Software Maya. The following error appears when saving a new scene:
The only difference seems to be that the maya folder, defined as a Software Entity in the schema, has its own folder and yml, when the other softwares are created via a generic folder using the software name. With Houdini and Nuke, the Context’s Entity is the Asset (or Shot). It used to be a simple folder, and now it’s a Software Entity.įor some reason, Maya sets the Context’s Entity to the Software, when Houdini and Nuke don’t. We have a folder representing the software name under the Task folder in our schema.
0 kommentar(er)
