Using -parentHWND makes everything slow ..?
I am using Unity as a 3D viewer, linked with another program made in C# (WPF, Windows 10 x64). Whenever I pass -parentHWND [IntPtr of Application]
to the Unity Standalone, my main application becomes very slow. If I create two Unity processes with the same -parentHWND
, the application becomes almost non usable.
If I don't use -parentHWND
, it runs fine, but I loose the bit of integration that -parentHWND
provides.
I looks like (maybe I'm wrong) that this argument makes the two applications share the same thread or something like this, with a same or better priority for Unity, whereas without this argument they run more independently.
Is there a way to know what -parentHWND
exactly does ? (some Win32
stuff maybe?) Is it possible to make then run both at a normal speed while keeping the benefits of -parentHWND
?
Thanks
Your answer
Follow this Question
Related Questions
Unity variables disappear when a method is called on an event from an external process 0 Answers
What should I use, a Dictionary with 100 entries or a class with 100 variables? 0 Answers
Help with an error in scripting - extreme newbie 3 Answers
System.Action has some invalid arguments 0 Answers
Unity Editor freezes when starting several System.Diagnostics.Process one after another 0 Answers