If you have other renderers and plugins, I would remove all other plugins from HOUDINI_PATH, get HtoA working, and then put the other stuff back. You want to see the HtoA location at the start of HOUDINI_PATH Third, check Help > About Houdini > Show Details You want something like this (PATH is for Windows only): # htoa config start Second, what’s your houdini.env look like? That is almost always because the environment (PATH and HOUDINI_PATH) is not set up correctly for HtoA and Houdini.įirst, how to do you start Houdini? Don’t double-click on a hip file, because the Houdini environment won’t be set up correctly. set QT_QPA_PLATFORM_PLUGIN_PATH=C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing\Current\AdskLicensingAgent\platforms The solution? Set QT_QPA_PLATFORM_PLUGIN_PATH to point to the AdskLicensingAgent\platforms folder. Using Process Monitor, I saw (as expected) that the problem was that the AdskLicensingAgent was loading Qt platform plugins from Houdini: Ġ0:00:31 153MB WARNING | rendering with watermarks because of failed authorization:Ġ0:00:31 153MB | timeout before callback was called Reinstalling the application may fix this problem.Īvailable platform plugins are: minimal, offscreen, webgl, windows.Īfter AdskLicensingAgent crashed, the render would continue, but license authorization would fail: 00:00:00 148MB | authorizing with license manager: user.
This application failed to start because no Qt platform plugin could be initialized. In this case, a Houdini command-line render with Arnold (HtoA) failed because the AdskLicensingAgent failed to start. Or, “things that happen when you use single-user licensing on a render node” 😉
0 kommentar(er)
