Fabian
Fabian
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Huge bugbear: why does Houdini default to start at frame 1, not zero? Aug. 23, 2017, 8:52 a.m.
Hi,
probably because animation always started on frame 1, look at any old dopesheet and it will start at frame 1. Also frame numbers and timecode are two different things with quite different histories. Nuke also starts on frame 1. Only programmers are weird and start counting at 0 ;-)
Best regards,
Fabian
probably because animation always started on frame 1, look at any old dopesheet and it will start at frame 1. Also frame numbers and timecode are two different things with quite different histories. Nuke also starts on frame 1. Only programmers are weird and start counting at 0 ;-)
Best regards,
Fabian
Thinking of moving from Rhino to Houdini Jan. 24, 2017, 5:28 a.m.
Hi,
I know both and they are not replacements for each other but can on occasion be used in a complementary way. Learning Houdini can be well worth it but not as a replacement for Rhino. Houdini is more intuitive and faster for some modelling stuff but Rhino's NURBS modelling tools are way more intricate and a bunch of the stuff you can do with Grasshopper is not replicable in Houdini.
A lot of Houdini's recently improved modelling tools are for poly modelling whereas Rhino is a pure NURBS modeller with a few mesh processing tools mostly for clean-up for printing. Be very aware of the differences here.
Forget stuff like sections, layouts, panelling tools, rhino cam, etc. and any of the Archicad and Revit live integrations as well as robust cad format interop. i/o like robust IGES, STP and DWG support. Also running data out for construction and documentation is not the same. For taking in data Houdini doesn't have a concept of layers like in cad programs and as such you will have problems taking in data with any level of complexity. Also unless something has changed recently, naming limitations will result in layer names to get screwed up if layers are named with something other than ascii characters making a roundtrip a royal pain (you need to break layers out into separate files before taking them to Houdini you want to stand a chance).
In your case you might look into writing some script to automate running through various settings for your sim in Rhino over night so you don't need to sit there trying values.
For processing/massaging point cloud or raw mesh data Houdini can be used nicely though. I've only done this in a one-way scenario where heavy geo-data came into Houdini for use in an animation and needed filtering and cleaning but there Houdini breezed through stuff I'm sure would have been a nightmare in Grasshopper.
Best of luck and happy learning,
Fabian
I know both and they are not replacements for each other but can on occasion be used in a complementary way. Learning Houdini can be well worth it but not as a replacement for Rhino. Houdini is more intuitive and faster for some modelling stuff but Rhino's NURBS modelling tools are way more intricate and a bunch of the stuff you can do with Grasshopper is not replicable in Houdini.
A lot of Houdini's recently improved modelling tools are for poly modelling whereas Rhino is a pure NURBS modeller with a few mesh processing tools mostly for clean-up for printing. Be very aware of the differences here.
Forget stuff like sections, layouts, panelling tools, rhino cam, etc. and any of the Archicad and Revit live integrations as well as robust cad format interop. i/o like robust IGES, STP and DWG support. Also running data out for construction and documentation is not the same. For taking in data Houdini doesn't have a concept of layers like in cad programs and as such you will have problems taking in data with any level of complexity. Also unless something has changed recently, naming limitations will result in layer names to get screwed up if layers are named with something other than ascii characters making a roundtrip a royal pain (you need to break layers out into separate files before taking them to Houdini you want to stand a chance).
In your case you might look into writing some script to automate running through various settings for your sim in Rhino over night so you don't need to sit there trying values.
For processing/massaging point cloud or raw mesh data Houdini can be used nicely though. I've only done this in a one-way scenario where heavy geo-data came into Houdini for use in an animation and needed filtering and cleaning but there Houdini breezed through stuff I'm sure would have been a nightmare in Grasshopper.
Best of luck and happy learning,
Fabian
RFE: Input operators list "Mute Button" April 3, 2014, 9:16 p.m.
I'd think that it would have to be addressed at the base UI code level no? Lists of input operators turn up on basically any OP that takes multiple input or not?
I'll write it up and submit it at the end of the week when I have a minute. Anyone else with a +1 please leave it here and I will include a link to the thread.
Best regards,
Fabian
I'll write it up and submit it at the end of the week when I have a minute. Anyone else with a +1 please leave it here and I will include a link to the thread.
Best regards,
Fabian