# Directly channel reference values

**URL:** <https://discourse.shapr3d.com/t/directly-channel-reference-values/41589>\
**Category:** Feature requests\
**Created:** [September 7, 2026, 7:33am UTC](https://discourse.shapr3d.com/t/directly-channel-reference-values/41589 "2026-09-07T07:33:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gary](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@gary](https://discourse.shapr3d.com/u/gary)\
**Post date:** [September 7, 2026, 7:33am UTC](https://discourse.shapr3d.com/t/directly-channel-reference-values/41589/1 "2026-09-07T07:33:47Z")

</div>

**The problem that this feature will solve:**

_The need to always create variables for shared values_

**Brief description of the outcomes that you expect from this feature:**

_Creating variables is great, but as a houdini user the ability to directly channel reference values is incredibly valuable. In Houdini: make a box. right click in any field, copy parameter. in another field (another object, reference, whatever) paste relative reference. Now they’re linked._

**What can’t you achieve without this feature?**

_Creating variables for all shared values results in large variable lists that can be cumbersome._

---

<div class="post-metadata">

**Author:** ![ivy125cordes](https://avatars.discourse-cdn.com/v4/letter/i/278dde/32.png) [@ivy125cordes](https://discourse.shapr3d.com/u/ivy125cordes)\
**Post date:** [September 8, 2026, 7:39am UTC](https://discourse.shapr3d.com/t/directly-channel-reference-values/41589/2 "2026-09-08T07:39:32Z")

</div>

Strongly agree with this. Direct parameter references would make it much easier to share values without creating a variable for every dependency. This would reduce clutter and make complex setups significantly easier to manage, especially for users coming from Houdini [Official Site](https://www.nipr.com.co)
