Maruan Anbaki
Maruan Anbaki
About Me
Connect
LOCATION
Not Specified
ウェブサイト
Houdini Engine
Availability
Not Specified
Recent Forum Posts
GetInt can only be called from the main thread. 2015年5月2日7:53
thank you for the response.
GetInt can only be called from the main thread. 2015年4月17日8:48
Hello,
I'm having some weird errors with any otl that I import in Unity.
the error is:
Also I had another error while building a project with the spaceship otl inside
the error was pointing out to HoudiniAssetUtility.cs with
Thank you,
I'm having some weird errors with any otl that I import in Unity.
the error is:
ArgumentException: GetInt can only be called from the main thread.
Constructors and field initializers will be executed from the loading thread when loading a scene.
Don't use this function in the constructor or field initializers, instead move initialization code to the Awake or Start function.
UnityEditor.EditorPrefs.GetInt (System.String key) (at /Users/builduser/buildslave/unity/build/artifacts/generated/common/editor/Utility.gen.cs:864)
HoudiniHost.getBool (System.String name) (at Assets/Houdini/Scripts/HoudiniHost.cs:1115)
HoudiniHost.get_prGenerateUVs () (at Assets/Houdini/Scripts/HoudiniHost.cs:320)
HoudiniAsset.reset () (at Assets/Houdini/Scripts/HoudiniAsset.cs:866)
HoudiniAssetOTL.reset () (at Assets/Houdini/Scripts/HoudiniAssetOTL.cs:67)
HoudiniControl..ctor () (at Assets/Houdini/Scripts/HoudiniControl.cs:78)
HoudiniAsset..ctor ()
HoudiniAssetOTL..ctor ()
Also I had another error while building a project with the spaceship otl inside
the error was pointing out to HoudiniAssetUtility.cs with
HoudiniAssetUtility.cs(1624,28): error CS0246 The type or namespace name `UnwrapParam' could not be found.however i added
#if UNITY_4_3 || UNITY_4_4 || UNITY_4_5 || UNITY_4_6at each part that the error was pointing, which did the trick.
and #endif
Thank you,
Choppy audio playback in Houdini 14 2015年3月31日10:13
Simon wrote:I'm thinking that it may be a problem with my setup as judging from the lack of response other users aren't having the same issues.
I just figured out that I also have your problem with v14, running on OS X 10.10.2, and I don't think is related to my setup anyway.
Did you submitted it as a bug? or did you solved it?