Houdini Main Changelogs
5.5.20 | Fixed Windows XP stability problems due to bug in the C run time library, MSVCRT.DLL (version 7.0.2600.0). |
Tue. June 11, 2002 | |
5.5.20 | Fixed Windows XP stability problems due to bug in the C run time library, MSVCRT.DLL (version 7.0.2600.0). |
Tue. June 11, 2002 | |
5.5.20 | Fixed Windows XP stability problems due to bug in the C run time library, MSVCRT.DLL (version 7.0.2600.0). |
Tue. June 11, 2002 | |
5.5.20 | Added an Inline Code VOP. This operator lets you write VEX code that appears directly in your VOPNET's generated shader code. |
Tue. June 11, 2002 | |
5.5.20 | Added an Inline Code VOP. This operator lets you write VEX code that appears directly in your VOPNET's generated shader code. |
Tue. June 11, 2002 | |
5.5.20 | Added an Inline Code VOP. This operator lets you write VEX code that appears directly in your VOPNET's generated shader code. |
Tue. June 11, 2002 | |
5.5.20 | Added an Inline Code VOP. This operator lets you write VEX code that appears directly in your VOPNET's generated shader code. |
Tue. June 11, 2002 | |
5.5.20 | Added an Inline Code VOP. This operator lets you write VEX code that appears directly in your VOPNET's generated shader code. |
Tue. June 11, 2002 | |
5.5.19 | Renamed the "Context To Device" VOP to "To NDC" and "Device To Context" to "From NDC". |
Mon. June 10, 2002 | |
5.5.19 | Renamed the "Context To Device" VOP to "To NDC" and "Device To Context" to "From NDC". |
Mon. June 10, 2002 | |
5.5.19 | Renamed the "Context To Device" VOP to "To NDC" and "Device To Context" to "From NDC". |
Mon. June 10, 2002 | |
5.5.19 | Renamed the "Context To Device" VOP to "To NDC" and "Device To Context" to "From NDC". |
Mon. June 10, 2002 | |
5.5.19 | Renamed the "Context To Device" VOP to "To NDC" and "Device To Context" to "From NDC". |
Mon. June 10, 2002 | |
5.5.19 | Fixing a problem where hkey would not think you were entitled to a license extension when the license had expired and you were not viewing expired licenses. |
Mon. June 10, 2002 | |
5.5.19 | Fixing a problem where hkey would not think you were entitled to a license extension when the license had expired and you were not viewing expired licenses. |
Mon. June 10, 2002 | |
5.5.19 | Fixing a problem where hkey would not think you were entitled to a license extension when the license had expired and you were not viewing expired licenses. |
Mon. June 10, 2002 | |
5.5.19 | Fixing a problem where hkey would not think you were entitled to a license extension when the license had expired and you were not viewing expired licenses. |
Mon. June 10, 2002 | |
5.5.19 | Fixing a problem where hkey would not think you were entitled to a license extension when the license had expired and you were not viewing expired licenses. |
Mon. June 10, 2002 | |
5.5.19 | On Windows, we now use a more consistent method of generating the server codes, which should only affect users running with multiple network adapters (e.g. users with laptops). |
Mon. June 10, 2002 | |
5.5.19 | On Windows, we now use a more consistent method of generating the server codes, which should only affect users running with multiple network adapters (e.g. users with laptops). |
Mon. June 10, 2002 | |
5.5.19 | On Windows, we now use a more consistent method of generating the server codes, which should only affect users running with multiple network adapters (e.g. users with laptops). |
Mon. June 10, 2002 | |
5.5.19 | On Windows, we now use a more consistent method of generating the server codes, which should only affect users running with multiple network adapters (e.g. users with laptops). |
Mon. June 10, 2002 | |
5.5.19 | On Windows, we now use a more consistent method of generating the server codes, which should only affect users running with multiple network adapters (e.g. users with laptops). |
Mon. June 10, 2002 | |
5.5.19 | If you specify a global variable name or a VCC reserved word as the Parameter Name in a Parameter VOP, the Parameter VOP now gets an error flag which says that an invalid Parameter Name has been specified. Previously, specifying a Global Variable name would result in the Parameter Name automatically changing itself. Setting it to a VCC reserved word would result in compiler warnings or errors. |
Mon. June 10, 2002 | |
5.5.19 | If you specify a global variable name or a VCC reserved word as the Parameter Name in a Parameter VOP, the Parameter VOP now gets an error flag which says that an invalid Parameter Name has been specified. Previously, specifying a Global Variable name would result in the Parameter Name automatically changing itself. Setting it to a VCC reserved word would result in compiler warnings or errors. |
Mon. June 10, 2002 |