Full Version: Houdini Engine and Android
Any chance for Houdini Engine working in Unity's Android Player any time soon? Or ever…?
That sounds like runtime support in which case the answer is “we're thinking about it”. 
It's a hard problem that we know a lot of people would like us to solve. It's unlikely to be solved in the near future but I don't think it's impossible either.
It's a hard problem that we know a lot of people would like us to solve. It's unlikely to be solved in the near future but I don't think it's impossible either.
Not necessarily real-time, although this would be awesome.
I was mostly thinking about support in the editor when it is switched to Android platform. Last time I checked (in H15, I believe) Houdini Engine didn't work in it and in order to modify parameters of an asset I had to switch back to PC platform, modify them, then switch back to Android (which usually broke the asset).
But maybe something has changed since then and now it works? I'll give it a shot. This would be fantastic.
I was mostly thinking about support in the editor when it is switched to Android platform. Last time I checked (in H15, I believe) Houdini Engine didn't work in it and in order to modify parameters of an asset I had to switch back to PC platform, modify them, then switch back to Android (which usually broke the asset).
But maybe something has changed since then and now it works? I'll give it a shot. This would be fantastic.
Oh, ya, that still doesn't work. I haven't tried to fix it myself in a while but the problem usually came down to simply not being able to use any APIs not native to the platform the editor was set to.
For example, if you switch your platform to Android, I can't use windows APIs to check the registry for the location of Engine. That's even if you are still in the Editor. That's because Unity tries to limit all C# code to the platform that you are currently set to.
The other issue was that there was no way to tell if our code was actually running on Android or if it was running on Windows with the platform set to Android.
In any case, this request has not been forgotten. There just isn't anything in the pipe I can talk about at the moment.
For example, if you switch your platform to Android, I can't use windows APIs to check the registry for the location of Engine. That's even if you are still in the Editor. That's because Unity tries to limit all C# code to the platform that you are currently set to.
The other issue was that there was no way to tell if our code was actually running on Android or if it was running on Windows with the platform set to Android.
In any case, this request has not been forgotten. There just isn't anything in the pipe I can talk about at the moment.
Oh bummer. I suspected that it had something to do with Unity itself.
However, I'm confident that you folks will eventually succeed in lobbying Unity guys. And they will change things that block you, so the gates for Houdini Engine could open for any platform.
Jeez, having Houdini Engine working in Unity's Android mode would save me so much time… Not to mention our lead programmer from whom a lot of workload would be taken off.
However, I'm confident that you folks will eventually succeed in lobbying Unity guys. And they will change things that block you, so the gates for Houdini Engine could open for any platform.
Jeez, having Houdini Engine working in Unity's Android mode would save me so much time… Not to mention our lead programmer from whom a lot of workload would be taken off.
i also wish this so much, i hope houdini engine work on unity android
We just fixed this issue. So the latest daily build of Houdini Engine should now work in Unity Editor when targeting other platforms, including Android.
Fantastic!!!
Thank you so much for fixing this! This was the number one on my Houdini wish list.
Thank you so much for fixing this! This was the number one on my Houdini wish list.
I'm getting this error:
Hi,
Try build Houdini 16.0.628. There was another change made yesterday that fixed that particular error.
Try build Houdini 16.0.628. There was another change made yesterday that fixed that particular error.
Thanks!