# 'Adjust Hue/Saturation' command does not work/show \[v1.3-beta1\]

**URL:** https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327
**Category:** Bug Reports
**Created:** [May 29, 2021, 4:23pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327 "2021-05-29T16:23:22Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Arecher](https://community.aseprite.org/user_avatar/community.aseprite.org/arecher/32/23749_2.png) [@Arecher](https://community.aseprite.org/u/Arecher)
#### Post date: [May 29, 2021, 4:23pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327/1 "2021-05-29T16:23:23Z")

</div>

It seems that in the latest beta branch the ‘Adjust Hue/Saturation’ command has stopped working completely. The dialog does not show, and you get locked out of using any tools or doing other commands, until you back out of the command, by using ESC.

This happens both when using `Edit > Adjustments > Hue/Saturation...` and custom set keybinds.

Other adjustments do seem to work however.

---

<div class="post-metadata">

### Author: ![BraidAcer](https://community.aseprite.org/user_avatar/community.aseprite.org/braidacer/32/7193_2.png) [@BraidAcer](https://community.aseprite.org/u/BraidAcer)
#### Post date: [May 29, 2021, 7:41pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327/2 "2021-05-29T19:41:05Z")

</div>

Hmm… works for me. Specify what sprite RGB/Indexed of what size and how many layers do you try to change with Hue/Saturation. Any selected regions?

---

<div class="post-metadata">

### Author: ![KashouC](https://community.aseprite.org/user_avatar/community.aseprite.org/kashouc/32/1404_2.png) [@KashouC](https://community.aseprite.org/u/KashouC)
#### Post date: [May 29, 2021, 10:18pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327/3 "2021-05-29T22:18:47Z")

</div>

My hunch says that the hue/saturation dialogue is opening outside of the monitor for some reason. Try going into edit \> preferences \> experimental and uncheck UI with multiple windows, restart Aseprite, and try again. After you can revert it and restart again and see if it works.

---

<div class="post-metadata">

### Author: ![Arecher](https://community.aseprite.org/user_avatar/community.aseprite.org/arecher/32/23749_2.png) [@Arecher](https://community.aseprite.org/u/Arecher)
#### Post date: [May 30, 2021, 4:34pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327/4 "2021-05-30T16:34:32Z")

</div>

Seems you’re right. Upon reinstalling the Aseprite Beta branch (after I decided to revert back), it seems to all work as expected. Did some quick tests to see what might have caused it, but I can’t reproduce the issue anymore.

Guess I should have tested the issue a little more thoroughly. For now this issue can be closed.

---

<div class="post-metadata">

### Author: ![dacap](https://community.aseprite.org/user_avatar/community.aseprite.org/dacap/32/10_2.png) [@dacap](https://community.aseprite.org/u/dacap)
#### Post date: [May 31, 2021, 2:10pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327/5 "2021-05-31T14:10:33Z")

</div>

Hi there 👋 there is an issue opening windows that are outside the limits of the available workarea (the issue can appear in certain cases when we send a window to other monitor and then we unplug the second monitor).

---

<div class="post-metadata">

### Author: ![dacap](https://community.aseprite.org/user_avatar/community.aseprite.org/dacap/32/10_2.png) [@dacap](https://community.aseprite.org/u/dacap)
#### Post date: [June 4, 2021, 10:31pm UTC](https://community.aseprite.org/t/adjust-hue-saturation-command-does-not-work-show-v1-3-beta1/9327/6 "2021-06-04T22:31:02Z")

</div>

Today we’ve released [Aseprite v1.3-beta2](https://community.aseprite.org/t/aseprite-v1-3-beta1/9222/1) which should fix this issue.
