uiS[cript]Py: Announcement. uispy download available

logo_400pxw

I have decided to make available a python wrapper for Houdini’s uiscript. It has been the result of needs I have had and was largely ripped from another defunct project. It should be considered alpha. I am aware of a couple efforts to do this, however I think uispy is fairly robust and useful.

Hopefully this will also provide an exploratory opportunity to document its clean-up here on  eyevex.com bit by bit in the New year (assuming compatibility with h16 for now). At that time some examples, tutorials and explanations will be coming, until then feel free to download and poke around.

It is acknowledged, that a few things are broken or missing, some the scripts are a bit hacky, there are places for improvement, and a bit that is completely wrong, but working. This is alpha, which mean it has only been used my myself and really only on a specific setup, in my case that’s Linux 64, kubuntu. Earlier versions were tested win win7, but have not been in sometime. Its development also means it lack some safety checks and sometimes you may be allowed to use values that wont properly build the dialog. This will be an area of improvement as the module is cleaned up.

Why do this at all…. There’s a few reasons to… and a few reasons not to. As uiS[cript]py uses only standard python and built-in Houdini libs, it provides a clean and safe way to create simple dialogs beyond the basic tree, multiline and lists in HOMs hou.ui While currently pySide and pyQt provide ways to build large robust interfaces, often a simple native dialog without worrying about qt deps or learning large libs is needed, and this fills that space. For those familiar with parmameterTemples in HOM, the naming of methods and usage closely mirrors that workflow. UI Script is also used for Cpp plugs as a quick way to build interfaces, in the future this may provide an easy way to design uis visually and dump the script.

This is a more advanced topic and not all basics wont be gone over, hopefully all interested will get something from it, but in the end the inner workings will likely most interesting to Pipeline/dept/show Tds. Example usages will probably be of broader interest and for reader that just wants to get to using it.

happy CG’ing. (|;-D>

eyevexTools HOM redundant functions depreciation

This space has gotten a bit stagnant and as for a multitude of reasons several post never made it to publish, however I am moving forward with a larger series on uiS[cript]Py. Most of eyevextools is working although need to be tested in recent versions. However, a lot of the much needed functionality we explored here has since appeared in the HOM module. This is great, but has made much of EVT redundant. In the near future I will be depreciating these parts. Posts and downloads will remain available for those that want to follow along but depreciated features wont be maintained.

(|;-D>

Status

I have been busy this winter in a several step move hopefully keeping me in Montreal making good CGs for some time. Hold tight as I prepare an in-depth series of advanced posts and library addictions the next couple of weeks.

As I haven’t had a chance to decide the best way to deal with comments that are %99.9 spam, I have had to shut down commenting for the moment. For the few people that have posted legit comments I do appreciate the feedback and feel free to email me as I do still want to hear it, just not links to replica merchandise and grey market pharmaceuticals.

Congrats to the SESI crew on another release full of surprises tools to help make the Magic happen with H12.5 I haven’t had time to verify compatibility of EVT pys, so any that find hiccups, please do email me.

Happy CG’in (|;-D>

Another Bulk Post

Status

In the future I will be trying to post one part in a series at a time — we shall see if this works out. As, obvious from the last two series, I tend to accumulate the whole thing before refining and posting it all, but this does leave a bit of editing to do at once.

I will be going to siggraph and hopefully getting some ideas of some simple things to post towards the end of the summer.

As always feel free to leave feedback or bug reports about any of the posts or tools, thanks for reading.

eyevexTools updated to 0.3.1

Apparently, in my sleepy haze I had forgotten to add the py lib folder/name.
This new zip has it present and named correctly.

There are no other changes so, if you downloaded 0.3.0, just make sure all the python files (that were in a folder called ‘python’ in the zip) are installed inside the appropriate python location in a folder named ‘eyevexTools (without the quotes).

i.e. $HOME/houdini11.1/scripts/python/eyevexTools/*.py

** Thanks reader Dan W  for spotting my lack of coffee at time of upload… oops… Sorry about that…
(|;-D>

I thought to myself “why don’t I have a blog?”

So after being asked several times if I had a blog, I thought to myself “why don’t I have a blog?” So here it is.

Often it can be difficult to find more practical examples and instructions for production tools and asset development as the world of TDs is encumbered by legality and non-disclosure typically associated with working in a studio. I hope to provide some insight to some techniques via pet projects and free time scripting and experiments. Hopefully this will help students, hobbyists, and other professionals who are trying to learn a little more about Houdini in addition to showcasing some personal work.

This is my first venture into the blogosphere so its likely to change somewhat , but the consistent themes will be Houdini, related software and techniques, and some general 3D CG.

Some initial intended uses of this space will be to:

  • log some what I am currently working on both in dev and in software
  • share my own professional news as well as general Houdini news
  • offer tips & tricks for both Houdini RnD and artist use
  • offer instructional entries for those researching or learning
  • share some tools from my personal arsenal with hopefully some explanation

Of course these are just my initial intentions and as time goes on I expect it evolves. So, welcome! … glad to have you along for the ride.

(|;-D>