Houdini Main Changelogs
6.0.202 | New Occlusion and Irradiance VOPs in the surface and light contexts. |
Wed. February 5, 2003 | |
6.0.202 | New Occlusion and Irradiance VOPs in the surface and light contexts. |
Wed. February 5, 2003 | |
6.0.202 | New Occlusion and Irradiance VOPs in the surface and light contexts. |
Wed. February 5, 2003 | |
6.0.202 | Removed the "get" from the neighbour VOPs, polished the help and did a minor reorg of the inputs. |
Wed. February 5, 2003 | |
6.0.202 | Removed the "get" from the neighbour VOPs, polished the help and did a minor reorg of the inputs. |
Wed. February 5, 2003 | |
6.0.202 | Removed the "get" from the neighbour VOPs, polished the help and did a minor reorg of the inputs. |
Wed. February 5, 2003 | |
6.0.202 | Removed the "get" from the neighbour VOPs, polished the help and did a minor reorg of the inputs. |
Wed. February 5, 2003 | |
6.0.202 | Removed the "get" from the neighbour VOPs, polished the help and did a minor reorg of the inputs. |
Wed. February 5, 2003 | |
6.0.202 | Making disabled text easier to read. |
Wed. February 5, 2003 | |
6.0.202 | Making disabled text easier to read. |
Wed. February 5, 2003 | |
6.0.202 | Making disabled text easier to read. |
Wed. February 5, 2003 | |
6.0.202 | Making disabled text easier to read. |
Wed. February 5, 2003 | |
6.0.202 | Making disabled text easier to read. |
Wed. February 5, 2003 | |
6.0.202 | It is no longer possible to create a VOPNET inside another network type (such as creating a VOPNET inside an Object). All VOPNETs must be created in the /vex network. |
Wed. February 5, 2003 | |
6.0.202 | It is no longer possible to create a VOPNET inside another network type (such as creating a VOPNET inside an Object). All VOPNETs must be created in the /vex network. |
Wed. February 5, 2003 | |
6.0.202 | It is no longer possible to create a VOPNET inside another network type (such as creating a VOPNET inside an Object). All VOPNETs must be created in the /vex network. |
Wed. February 5, 2003 | |
6.0.202 | It is no longer possible to create a VOPNET inside another network type (such as creating a VOPNET inside an Object). All VOPNETs must be created in the /vex network. |
Wed. February 5, 2003 | |
6.0.202 | It is no longer possible to create a VOPNET inside another network type (such as creating a VOPNET inside an Object). All VOPNETs must be created in the /vex network. |
Wed. February 5, 2003 | |
6.0.202 | There is a new parameter to control which lights should be active in renders. This is similar to the visible objects field in many output drivers. |
Wed. February 5, 2003 | |
6.0.202 | There is a new parameter to control which lights should be active in renders. This is similar to the visible objects field in many output drivers. |
Wed. February 5, 2003 | |
6.0.202 | There is a new parameter to control which lights should be active in renders. This is similar to the visible objects field in many output drivers. |
Wed. February 5, 2003 | |
6.0.202 | There is a new parameter to control which lights should be active in renders. This is similar to the visible objects field in many output drivers. |
Wed. February 5, 2003 | |
6.0.202 | There is a new parameter to control which lights should be active in renders. This is similar to the visible objects field in many output drivers. |
Wed. February 5, 2003 | |
6.0.202 | Object selection now behaves differently with subnets. There is now a select entire subnets option in the left hand viewer toolbar. The default for this can be changed with Settings::Main Preferences::Objects And Geometry::Select Entire Subnets On By Default. It is on by default. Turning it off will generate the same picking behaviour as 5.5. When this mode is on you will only be able to pick objects at your current view level. When your viewer is at /obj, you will only be able to pick objects that are immediate children of /obj, eg: /obj/light1, /obj/model, or /obj/subnet1. If you pick a child node, for example, /obj/subnet1/geo1, it is the subnet that will be picked and all the objects in the subnet will be highlighted. As the transform state can now transform subnets, this will have the expected behaviour. To pick individual components of a subnet, either dive into the subnet (view /obj/subnet1) or turn off this flag (hotkey '-'). |
Wed. February 5, 2003 | |
6.0.202 | Object selection now behaves differently with subnets. There is now a select entire subnets option in the left hand viewer toolbar. The default for this can be changed with Settings::Main Preferences::Objects And Geometry::Select Entire Subnets On By Default. It is on by default. Turning it off will generate the same picking behaviour as 5.5. When this mode is on you will only be able to pick objects at your current view level. When your viewer is at /obj, you will only be able to pick objects that are immediate children of /obj, eg: /obj/light1, /obj/model, or /obj/subnet1. If you pick a child node, for example, /obj/subnet1/geo1, it is the subnet that will be picked and all the objects in the subnet will be highlighted. As the transform state can now transform subnets, this will have the expected behaviour. To pick individual components of a subnet, either dive into the subnet (view /obj/subnet1) or turn off this flag (hotkey '-'). |
Wed. February 5, 2003 |