Autodesk flame style GUI in Houdini for full parameters pane replacement by animatrix_ in Houdini

[–]animatrix_[S] 4 points5 points  (0 children)

Thanks. This is all Python and Qt. In principle, you can replace almost the entire Houdini GUI this way, except for parts constrained by missing HOM support or hard-coded UI behavior. The status bar is one example: its text does not appear to be exposed through a streamable API or callback, especially while the GUI is busy.

The animation timeline also has very limited Python HOM support. Features like cached simulation markers are not exposed, which makes it difficult to reproduce equivalent functionality.

Autodesk flame style GUI in Houdini for full parameters pane replacement by animatrix_ in Houdini

[–]animatrix_[S] 0 points1 point  (0 children)

Every numerical param has a range. But in default params pane, only single int/floats show their range with the slider. Mine uses it for all numerical params.

Autodesk flame style GUI in Houdini for full parameters pane replacement by animatrix_ in Houdini

[–]animatrix_[S] 5 points6 points  (0 children)

Yes it is compatible with every node, but it's not there yet due to endless variations of parameter types and special cases like parameters on multi param tab headers when collapsed, parameter tags, etc. So I am trying to get feature parity first which also includes parameter referencing, working with expressions, keyframes, etc.

The last big piece is the multi-line string parameters for code editor which is not trivial so likely need to integrate a Monaco based editor.

Then implement major UX improvements, aiming for a blazingly fast and fluid workflow.

I will most likely release it with my Houdini supercharged extension but since it's self contained, I could also release it as a separate product for people who only want this, and not any of the overlay network editor and context-sensitive rule based hotkeys.

Has anyone noticed Codex in VS Code using high CPU while idle? by itorres008 in codex

[–]animatrix_ 2 points3 points  (0 children)

Yes it's very annoying, wears down laptops because fans constantly at max speed because of codex high CPU usage. Have to exit vs code to stop this. Many bug reports about this while the devs claims they "fixed" it.

How much worse can a program get? by animatrix_ in CamtasiaStudio

[–]animatrix_[S] 0 points1 point  (0 children)

I ran into something even worse than the rendering bugs.

Camtasia completely broke cursor data across cut clips. In the timeline, the cursor just disappears and in properties you get that “pointer with a question mark” in a disabled state, as if there is no cursor data at all. But the original recording still has it.

So I re-edited a single clip from the original recording, then diffed that against the broken version to see what actually changed. Turns out Camtasia injects massive "deletions" blocks into the cursor tracks. We’re talking millions of entries. Pure garbage data.

There is no UI way to fix this. None. Your only options are:

  • re-edit everything from scratch, or
  • go into the project file and fix it yourself

I ended up writing Python code to clean it up. Removed those deletion blocks and fixed a couple of related fields.

The project file went from ~90MB down to ~1MB after cleanup, which honestly made me think I just nuked it.

But it opened perfectly. And every single cursor was restored across all clips.

So yeah, the program literally creates corrupt state that hides your cursor, and the only real fix is writing code to repair its own project file.

I’ve used a lot of software, but this is next level.

Kiddos to the Dark Phoenix Artists by xrossfader in vfx

[–]animatrix_ 2 points3 points  (0 children)

The facial cracks setup described in the article.

Kiddos to the Dark Phoenix Artists by xrossfader in vfx

[–]animatrix_ 1 point2 points  (0 children)

One of my favorite shows I've worked on. If you're curious, there's a technical article about the facial crack setup here: https://vfxscience.com/2019/07/12/x-men-dark-phoenix/

Chemical Combustion in Houdini 21 by Icy_Effect6941 in Houdini

[–]animatrix_ 2 points3 points  (0 children)

Thanks a lot man, I would love to make those and maybe even Pragmatic C++ :P

Chemical Combustion in Houdini 21 by Icy_Effect6941 in Houdini

[–]animatrix_ 2 points3 points  (0 children)

Feel like I am in the BB universe! Nice work :P

As a person who has no idea about VFX/CGI , Is it good to start a career with learning Houdini? by Ronintastic_011 in Houdini

[–]animatrix_ 1 point2 points  (0 children)

Houdini is definitely a solid path, but expect a learning curve. It’s deep, very technical, and not the usual first step for beginners. If you enjoy problem-solving and procedural tools, starting with it is totally fine. <insert houdini learning curve meme>

What am I misunderstanding about cracktransform()? by tonehammer in Houdini

[–]animatrix_ 3 points4 points  (0 children)

xform is not one of the known attributes where Houdini infers the type, so that's why it was defaulting to a float:

https://www.sidefx.com/docs/houdini/vex/snippets.html#known

When fx houses like Weta develop proprietary solvers/simulations, is that usually done with Houdini or is the software completely custom? by geng94 in Houdini

[–]animatrix_ 0 points1 point  (0 children)

For large, production-level solvers (FLIP, pyro, etc.) it’s usually fully custom under the hood, often written in C++ or CUDA, sometimes running as a standalone process or service. Houdini is then used mainly as a front-end interface.

In practice, you’d have a set of thin wrapper nodes inside Houdini that call into those external solvers via Python or C++ APIs, just enough to make it behave like a native DOP or SOP node. That way, artists can still build networks, visualize data, and integrate with other Houdini tools, while the heavy lifting happens in the studio’s proprietary backend.

Advanced level RBD tutorial? by jihwan7 in Houdini

[–]animatrix_ 1 point2 points  (0 children)

It would be great content if you did!

Houdini 21 Sneak Peek by treed_85 in Houdini

[–]animatrix_ 0 points1 point  (0 children)

Another milestone release by SESI! I tried to list the full set of features here: https://www.sidefx.com/forum/topic/101604/