Jump to content
Alexey Vanzhula

hscript

Recommended Posts

Unless SESI has secretly released something newer that replaces it, I would say 'No'.

Share this post


Link to post
Share on other sites

They are really pushing for people to be using Python these days, but I'm not sure if that counts as HScript being officially 'deprecated.'

 

Here are some relevant quotes from the Houdini documentation that I've run into:

 

 

The Houdini Object Model (HOM) is an application programming interface (API) that lets you get information from and control Houdini using the Python scripting language. HOM replaces the functionality of Houdini’s previous scripting solutions, the expression language and HScript.

 

HScript is the Houdini’s old scripting language. HScript is still available in Houdini for compatibility with older files and scripts. For new scripts, we recommend you use the scripting APIinstead.

 

I think HScript will probably be supported for a while yet, largely because most people still seem to be using the HScript-based expressions, but if you're doing any kind of serious scripting Python is definitely the way to go. 

Share this post


Link to post
Share on other sites

No, I don't want SESI to remove hscript expressions. No. It still very useful and faster than python in simple cases.
But I don't like python-hscript fusion in shelf tools (when you drop nodes island to shelf) for example.

And why scene file (HIP) still not a Python script? I don't understand.

Share this post


Link to post
Share on other sites

NOPE

Hscript is still very deep into Houdini.

SESI advice to use Python rather than Hscript , but at the moment, Hscript is faster more reliable and in some cases has functions that doesn't exists in hom.

Also callbacks implemented with Python don't scale well.

For all of these I still prefer to use Hscrit for expressions.

Share this post


Link to post
Share on other sites
For all of these I still prefer to use Hscrit for expressions.

 

I only use hscript expressions ;)

 

Also callbacks implemented with Python don't scale well

 

What callbacks do you mean?

Share this post


Link to post
Share on other sites

Yep, it's easy to see why most people still prefer the old-style expressions. Consider the ubiquitous $PT expression vs. the Python equivalent:

 

pwd().curPoint().number()

 

Now which one of those is easier to remember?  ;)

Share this post


Link to post
Share on other sites

What callbacks do you mean?

Parameters callbacks

Share this post


Link to post
Share on other sites

I don't know about python but in my experience VEX seems to be replacing Hscript. The cooking times are much faster in VEX and in many ocasions it's easier than attribute VOP to setup something. I am pushing myself to learn VEX as much as possible.

Share this post


Link to post
Share on other sites

HScript expressions: For simple one liners on parameters

HScript commands: Deprecated in favour of Python where possible

Python: For scripting (when you need loops and functions, or more)

VEX/VOP: Large data processing

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×