# Valley Plateau - Decay parameter does not display 0% when at minimum

**URL:** <https://forum.4ms.info/t/valley-plateau-decay-parameter-does-not-display-0-when-at-minimum/2681>\
**Category:** Bug Reports and Fixes\
**Created:** [June 28, 2026, 7:50pm UTC](https://forum.4ms.info/t/valley-plateau-decay-parameter-does-not-display-0-when-at-minimum/2681 "2026-06-28T19:50:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anDREW](https://forum.4ms.info/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@anDREW](https://forum.4ms.info/u/anDREW)\
**Post date:** [June 28, 2026, 7:50pm UTC](https://forum.4ms.info/t/valley-plateau-decay-parameter-does-not-display-0-when-at-minimum/2681/1 "2026-06-28T19:50:43Z")

</div>

Tiny visual bug (on firmware v2.2.0 with latest version of the plugins:

Valley Plateau - Displays ‘3.5632e-07%’ instead of ‘0%’ when set to the minimum setting

---

<div class="post-metadata">

**Author:** ![danngreen](https://forum.4ms.info/user_avatar/forum.4ms.info/danngreen/32/14_2.png) [@danngreen](https://forum.4ms.info/u/danngreen)\
**Post date:** [June 29, 2026, 11:57pm UTC](https://forum.4ms.info/t/valley-plateau-decay-parameter-does-not-display-0-when-at-minimum/2681/2 "2026-06-29T23:57:56Z")

</div>

🙂  
That’s funny, I can confirm this (also is the same on VCV Rack).

---

<div class="post-metadata">

**Author:** ![anDREW](https://forum.4ms.info/letter_avatar_proxy/v4/letter/a/f19dbf/32.png) [@anDREW](https://forum.4ms.info/u/anDREW)\
**Post date:** [June 30, 2026, 3:20pm UTC](https://forum.4ms.info/t/valley-plateau-decay-parameter-does-not-display-0-when-at-minimum/2681/3 "2026-06-30T15:20:42Z")

</div>

Oh… I did not check the VCV Rack version. Hopefully is just a small display bug.

---

<div class="post-metadata">

**Author:** ![danngreen](https://forum.4ms.info/user_avatar/forum.4ms.info/danngreen/32/14_2.png) [@danngreen](https://forum.4ms.info/u/danngreen)\
**Post date:** [June 30, 2026, 4:04pm UTC](https://forum.4ms.info/t/valley-plateau-decay-parameter-does-not-display-0-when-at-minimum/2681/4 "2026-06-30T16:04:36Z")

</div>

Technically, the Decay parameter does not go to 0, it really does go only to 0.00000035632, so the firmware is accurately displaying the value of the Decay parameter. It’s just that it looks ugly to see sci notation in that context, so I think calling anything under 0.000005 “close enough” to 0 is probably best.