X/Y Pad Still Scenes for Each Individual Mover

[ShagLight]

With the X/Y pad as it is now, when you want to have a still scene within the X/Y pad, you can only have the same pan and tilt settings for all movers.

If for instance, I have 8 movers, I would like to be able to set different pan and tilt values for each individual mover.

My reason for this is I use several different still positions (shown in attached photos) with different pan settings and control the tilt with a fader patched to an X/Y pad. And all my EFXs are in relative mode.

I currently just use scene function for my still positions but would be nice if I could have it all in one widget (X/Y pad). And 8 X/Y pads does not work for me.

[GGGss]

But you can create all kinds of presets and add them to your XY-pad. When creating a preset, not all movers need to have the same pan/tilt settings!
Somehow I don't understand your request
https://docs.qlcplus.org/v4/virtual-console/xy-pad

[ShagLight]

But you can create all kinds of presets and add them to your XY-pad. When creating a preset, not all movers need to have the same pan/tilt settings!
Somehow I don't understand your request
https://docs.qlcplus.org/v4/virtual-console/xy-pad

I've heard it said that it's better to trigger still scenes and EFXs from withing the x/y pad.

But there is at least one glaring problem with the z/y pad (at least for me). I need to trigger those things from an external controller such as an APC Mini (or APC40 MK2 in my case). When attempting this the preset buttons don't work right. They act similar to a flash button and they don't send feedback data correctly.

As for setting a scene from within the x/y pad vs. importing a still scene, it seems like the first option would be better if there were a way to set each individual mover.

But either way, the problem with triggering the presets with an external controller makes x/y pad presets unusable for me. x/y pad is nice, but still needs a lot of work.

[GGGss]

But there is at least one glaring problem with the z/y pad (at least for me). I need to trigger those things from an external controller such as an APC Mini (or APC40 MK2 in my case). When attempting this the preset buttons don't work right. They act similar to a flash button and they don't send feedback data correctly.

To try and debug I should try to rebuild your environment.
I honestly never tried to bind external controls to the XY pad's preset buttons. The flash part astonishes me.

As a workaround, could you create a frame and add some buttons to it? Then, create a loopback universe and add some generic dimmers. Then, create some scenes with those dimmers.
Now, bind those scenes to the buttons and configure their external input to the controls of your external device.
Using the loopback, you should now be able to call the XY-pad presets without the flashing behaviour.

[ShagLight]

But there is at least one glaring problem with the z/y pad (at least for me). I need to trigger those things from an external controller such as an APC Mini (or APC40 MK2 in my case). When attempting this the preset buttons don't work right. They act similar to a flash button and they don't send feedback data correctly.

To try and debug I should try to rebuild your environment.
I honestly never tried to bind external controls to the XY pad's preset buttons. The flash part astonishes me.

As a workaround, could you create a frame and add some buttons to it? Then, create a loopback universe and add some generic dimmers. Then, create some scenes with those dimmers.
Now, bind those scenes to the buttons and configure their external input to the controls of your external device.
Using the loopback, you should now be able to call the XY-pad presets without the flashing behaviour.

I posted a new thread under Issue Reports with a simple show file. Here is that file.