search

sideeffects / HoudiniEngineForUnity

Houdini Engine for Unity
http://www.sidefx.com/unity
226 stars 87 forks source link

Switch to Unity Packages ? #15

Open melMass opened 3 years ago

melMass commented 3 years ago

Hi,

I have just tried to transform the plugin into a proper unity package, I'm about to test it further:

https://github.com/melMass/com.sidefx.houdiniengine

watsonsong commented 3 years ago

Good work! I think package is a better way to distribute the houdini engine. Hoping the SideFX will continue support this unity bridge. This repository has been no commit after the Epic invest SideFX...

melMass commented 3 years ago

Yes me too... I'm not sure if it's related to the investment but the Unity bridge is always ahead in features, but behind in integration, which is strange given how easier it is to extend Unity vs Unreal. But I think it's because Unreal is used by many non-technical artists whereas in Unity no one holds your hand (which I prefer for my use cases)

ghost commented 3 years ago

nice work with the package manager format, +1 that SideFX should switch to this. They have 2018.x as a minimum version, and that supports packages.

just throwing out an idea (might explore it though its low priority), I think a refactor of HEU_Defines to make use of a ScriptableObject for any unity asset references (like the default shaders) would be a lot friendlier to customization (for example swapping the default shaders with SRP compatible shader graphs).

There would need to be some work done to have it detect the SO asset via AssetDatabase or automatically create it within Assets if it is missing, but it is entirely possible (very similar to how the SRP scriptable objects work)

It could also hold the other values too, as that avoids having to re-merge future changes or modify the package. It could likely also just be a yaml or json file somewhere within the project's assets folder too.

Similar could probably occur with heu_settings.ini with where it is located, that will go on version control ignore lists for sure. (I'm not really sure what the significance of it being a separate ini is, unless it is some legacy stuff)