Matt Ebb

mattebb

About Me

.

Connect

LOCATION
Not Specified

Houdini Skills

Availability

Not Specified

My Badges

Houdini Academy Advisor
Since Jan 2024

My Talks

obj-image HIVE
Procedural Modelling/LookDev
obj-image HIVE
Doing Big Work with a Small Team

Recent Forum Posts

Event Trigger for python callback on drag and drop Feb. 11, 2020, 9:16 p.m.

Just bumping this, it would be extremely helpful if we could access the full data of drop events inside houdini (eg. including web urls), not just files.

I'd also like to get Shotgun drag/drop working here too.

Making TOPs less confusing June 28, 2019, 3:51 a.m.

kenxu
Ok, some notes from our earlier meeting on what to do about the usability issues. This is not the whole list, but just what's relevant to the discussion on this thread.

That's great to hear, thank you very much!

I think one of the stumbling blocks for TOPs is how it's so different to the rest of Houdini. I think the more that these potential changes/solutions could be more consistent with other aspects of Houdini the easier it will be for people to start picking it up.

cheers

Making TOPs less confusing June 26, 2019, 8 p.m.

mattebb
At the very least there should be a local scheduler added by default when you create a TOPnet (like the copnet inside /img). Seeing this unusual floating scheduler node immediately would go some way towards communicating how TOPs works differently to other Houdini networks.

I just found that this is actually a bug when creating a TOP network inside a ROP network. Creating it inside Sops or OBJ does indeed make a local scheduler by default. So it just seems like just a simple oversight, which is good! I've logged the bug with support.