DASD
DASD
About Me
Expertise
Not Specified
Location
Not Specified
Website
Connect
Recent Forum Posts
Any starting documentation for Houdini API with Unreal Engine 4? Jan. 23, 2019, 2:29 p.m.
Are you still looking into this?
Build lighting Jan. 12, 2019, 6:48 p.m.
Which Unreal Engine version is it?
Once you baked the hda out, you should have something like a Blueprint with instance static mesh component and a static mesh. Those assets would then be native Unreal assets. If you set the settings on those correctly it should be all good.
Once you baked the hda out, you should have something like a Blueprint with instance static mesh component and a static mesh. Those assets would then be native Unreal assets. If you set the settings on those correctly it should be all good.
Procedural Pipe - on Curve?? [just like the unreal demo shown] Jan. 7, 2019, 4:13 p.m.
I was thinking that we first need to have this in Houdini and then we could apply the tech developed for that in Maya.
Probiner Probiner (Facebook account) has recently posted this:
WIP: Bezier Deform Offsets per control.
https://streamable.com/l7rb3?fbclid=IwAR0WlqugKymNefycp_n9K7ZM_cncgMDUOTPLdY1DtuaAaxwo_oTibFkjhgA [streamable.com]
This is Houdini and it is basically what I would expect as a solution for my RFE. Though I would also hope for additional sliders for arbitrary attributes that could be generated when needed.
I think something similar can be then achieved in Maya with (callback) scripts and custom attributes. You would then maybe have a shelf tool to create a special NURBS curve that has some scripts associated with it.
I have have seen in the Maya script editor, that even though the vertices do not have scale and rotation values, the calls are executed when you use the gizmos. (But I don't know whether you can get those calls.) The additional information could then be stored in custom attributes.
Obviously there would be a bit of overhead, but I think the overall workflow possibilities would make it worth it.
Maybe it makes sense to use custom NURBS shapes for controlling the knots of the curve (instead of locators, because those don't properly show scale).
In my experience it is desirable to have input curves as independent objects. The other important thing is that they are easy to use.
To clarify why it's useful to have input curves as separate objects: They could be (re-)used by multiple different scripts, models and HDAs. They can also be moved across scenes. They would not loose information from updates etc.
Probiner Probiner (Facebook account) has recently posted this:
WIP: Bezier Deform Offsets per control.
https://streamable.com/l7rb3?fbclid=IwAR0WlqugKymNefycp_n9K7ZM_cncgMDUOTPLdY1DtuaAaxwo_oTibFkjhgA [streamable.com]
This is Houdini and it is basically what I would expect as a solution for my RFE. Though I would also hope for additional sliders for arbitrary attributes that could be generated when needed.
I think something similar can be then achieved in Maya with (callback) scripts and custom attributes. You would then maybe have a shelf tool to create a special NURBS curve that has some scripts associated with it.
I have have seen in the Maya script editor, that even though the vertices do not have scale and rotation values, the calls are executed when you use the gizmos. (But I don't know whether you can get those calls.) The additional information could then be stored in custom attributes.
Obviously there would be a bit of overhead, but I think the overall workflow possibilities would make it worth it.
Maybe it makes sense to use custom NURBS shapes for controlling the knots of the curve (instead of locators, because those don't properly show scale).
In my experience it is desirable to have input curves as independent objects. The other important thing is that they are easy to use.
To clarify why it's useful to have input curves as separate objects: They could be (re-)used by multiple different scripts, models and HDAs. They can also be moved across scenes. They would not loose information from updates etc.