Houdini 17 Wishlist

[Atom]

Multi-threaded everything, especially cloth.

It would be nice to have some kind of lip-synch face rig solution.

Also, hair should never go under the surface that it  is growing on.

Edited October 30, 2017 by Atom

[Tesla's fan]

I want functions and conjugate gradient methods that can handle large sparse matrices in VEX

I want functions and conjugate gradient methods that can handle large sparse matrices in VEX

I want functions and conjugate gradient methods that can handle large sparse matrices in VEX

please please please！

 

[LaidlawFX]

6 hours ago, Tesla's fan said:

I want functions and conjugate gradient methods that can handle large sparse matrices in VEX

I want functions and conjugate gradient methods that can handle large sparse matrices in VEX

I want functions and conjugate gradient methods that can handle large sparse matrices in VEX

please please please！

 

I'll give an A+ for font use.

[bonassus]

I have an obvious suggestion for chops. Dot syntax in the attribute Scope parameter field on the Channel node. 

This works P(1) 

but not this P.y

 

[Jesper Rahlff]

On 06/02/2017 at 3:33 PM, marty said:

Auto set-pivot for the viewport viewtool, shift+Z, aka C4D 

is this not the Space + Z feature?

[Guest tar]

1 hour ago, Jesper Rahlff said:

is this not the Space + Z feature?

the 'auto' bit is the difference.

[animatrix]

53 minutes ago, marty said:

the 'auto' bit is the difference.

I would love to have this as a toggle where the pivot is always set to current selection. Geometry selection over object selection, etc.

[Guest tar]

On 11/3/2017 at 9:09 AM, pusat said:

I would love to have this as a toggle where the pivot is always set to current selection. Geometry selection over object selection, etc.

https://vimeo.com/241036613#comment_16154324 

Cristin Barghiel9 hours ago

Glad to tell you that zooming and tumbling under the cursor, using ‘s’ as a sticky/volatile key for selection in the viewport and network editor, and many other much-requested features like them are indeed in H16.5. We simply couldn’t mention them all in our presentation.

Edited November 3, 2017 by tar

[CinnamonMetal]

I want it to bake me chocolate chip cookies.

[McNistor]

On 11/2/2017 at 10:09 PM, pusat said:

I would love to have this as a toggle where the pivot is always set to current selection. Geometry selection over object selection, etc.

Yeah, I'd love to have that too. For me, tumbling under the cursor is not that useful. I've explained and possibly have shown gifs with the inherent dis/advantages and differences between "selection" and "under cursor" tumbling, but I guess it didn't stick with the devs.

Not saying this new addition is harmful in any way, quite the contrary. I just wish "tumble/orbit around selection" would've seen the light at least as soon as this one.

Edited November 4, 2017 by McNistor

[kev2]

Invert the color of the font and background on the current active paramter tab. Paramter tabs that are now in a bold font are helpful but make it hard to tell quickly which tab is the exposed tab. 

[Guest tar]

On 11/4/2017 at 8:19 PM, McNistor said:

Yeah, I'd love to have that too. For me, tumbling under the cursor is not that useful. I've explained and possibly have shown gifs with the inherent dis/advantages and differences between "selection" and "under cursor" tumbling, but I guess it didn't stick with the devs.

Not saying this new addition is harmful in any way, quite the contrary. I just wish "tumble/orbit around selection" would've seen the light at least as soon as this one.

this?

 

 

[kev2]

Disable an input to the merge node without disconnecting it.

[McNistor]

@marty That seems to do the job. Works well on components, but for some reason is ignored for objects. Maybe it's the intended behavior, either way, I can love with it. Thanks for the info!

p.s. I have a RFE for this and for some reason I haven't been informed about this feature being implemented. Will check with them soon.

edit1: seems like it's working for objects too after a framing (space+F) on one.

edit2: I think I've figured what's casing the tumble pivot to become "unfocused" - it's after a camera panning; I think it should re-update the pivot on selection after every camera action, which currently it fails to do. Will file a bug report.

Edited November 14, 2017 by McNistor

[Guest tar]

33 minutes ago, McNistor said:

edit2: I think I've figured what's casing the tumble pivot to become "unfocused" - it's after a camera panning; I think it should re-update the pivot on selection after every camera action, which currently it fails to do. Will file a bug report.

Check the preference just above to the right 'Maintain Viewport Pivot when Panning'

[McNistor]

@marty Methinks I should do less testing in the viewport and more reading on that preferences tab. Again, thanks for the info!

edit: it appears that translating an object will fail to update the pivot. One has to deselect and reselect in order to update. This time I've looked in the prefs but found nothing related. Will check with support to see what's what.

Edited November 14, 2017 by McNistor

[kev2]

Re-imagine the For Each Blocks. I find the current language (Meta Import, Feedback, etc) needlessly confusing and the layout (while extremely nice aesthetically) doesn't add clarity, but rather adds a confusing DOPs-like weirdness to the otherwise straight-forward SOPs. Case in point, you set the block paramaters up in the Block End node. And I strongly disagree with the help docs statement that this is less confusion than copy stamping.  

[acey195]

15 hours ago, kev2 said:

 I strongly disagree with the help docs statement that this is less confusion than copy stamping.  

I respectfully disagree with that. (and agree with the documentation)

Have you tried both H16 and 16.5?
In 16.5 the tab menu is more specific with looping types, such as adding "foreach connectivity"

its also unfair to compare it to copy stamping, compared to the old foreach subnetwork, its just worlds better:
its faster, more stable, more difficult to make mistakes and easier to debug as well, with the new single pass option.
and like the documentation also points out: "The stamp expression function is the ultimate spooky action at a distance."
http://www.sidefx.com/docs/houdini/model/compile

Edited November 15, 2017 by acey195
now mentions the single pass option as well

[LaidlawFX]

18 hours ago, kev2 said:

Re-imagine the For Each Blocks. I find the current language (Meta Import, Feedback, etc) needlessly confusing and the layout (while extremely nice aesthetically) doesn't add clarity, but rather adds a confusing DOPs-like weirdness to the otherwise straight-forward SOPs. Case in point, you set the block paramaters up in the Block End node. And I strongly disagree with the help docs statement that this is less confusion than copy stamping.  

One of the things I did as a preset for the metadata node that could help you and maybe others for stamping is I created four parameters(iteration, numiteration, value, ivalue) that contains the expression detail(".",$CH,0), so unlike the labels you can just channel reference to those values for your stamping expression. 

I did find it weird when they first introduced the new foreach loop the metadata node did just float un-wired to other nodes and only relied on the block path. When you do more complex foreach loop operations it makes a bit more sense than simple ones.

I would agree with Twan though, the current setup is highly better than the old foreach sop and stamping expression for apples to apples comparisons. Maybe a few tweaks would be ok. 

[kev2]

3 minutes ago, LaidlawFX said:

One of the things I did as a preset for the metadata node that could help you and maybe others for stamping is I created four parameters(iteration, numiteration, value, ivalue) that contains the expression detail(".",$CH,0), so unlike the labels you can just channel reference to those values for your stamping expression. 

I did find it weird when they first introduced the new foreach loop the metadata node did just float un-wired to other nodes and only relied on the block path. When you do more complex foreach loop operations it makes a bit more sense than simple ones.

I would agree with Twan though, the current setup is highly better than the old foreach sop and stamping expression for apples to apples comparisons. Maybe a few tweaks would be ok. 

Nice tip. I never found copy stamping to be all that confusing but to be sure, the old for loop subnet business was really strange. The new For Loop blocks are powerful and I'm sure I'll get used to them but using fairly high level labels such as "metadata" and "feedback" to describe "Loop Information" and "Iterate On Top the Result of the Last Loop" might be concise but are so abstract as to be confusing.