Hi,
I'm experimenting with noVNC+SPICE and
when I started using SPICE without enabling the VD agent, I noticed a bug regarding mouse movement acceleration.
Basically it seems that mouse acceleration was getting doubled.
After I enabled VD agent, the mouse was much better behaved in the SPICE client, but in noVNC the mouse breaks as soon as you set the video driver to SPICE/QXL
Well, I notice that the way that noVNC breaks, looks and feel a LOT like the "double acceleration" mouse bug that SPICE has before the VD agent is enabled.
And I think, without VD Agent the mouse movements are relative and that's where the bug is, it's in the relative movement mouse acceleration and I think they're getting doubled, or the acceleration curve is ^2 or something like that.
And I think this is what is causing the mismatch between noVNC and SPICE.
And the problem is that this forces you to use one, or the other and you have at least a reboot to switch in between.
This usually ends up with me just giving up on SPICE being just too clunky and I prefer that noVNC works poorly everywhere, rather than have better responding SPICE but that I need to make work everywhere else.
But, other than the cursor, noVNC and SPICE work totally fine. With VD Agent I can resize the SPICE window to resize the guest OS display resolution, and noVNC updated just as quickly and accurately. Really the only problem is that cursor bug.
Is there any effort active to resolve that ? It does seem like virtualization in general has given up on SPICE, as video encoding appears not to work and the client still doesn't have dark mode. I imagine it got in that weird zone where, it should be good enough to use, but most people don't and it was probably assume that people just don't care, but really, it's just too clunky to use, even though it is really really close to being usable !
I'm experimenting with noVNC+SPICE and
when I started using SPICE without enabling the VD agent, I noticed a bug regarding mouse movement acceleration.
Basically it seems that mouse acceleration was getting doubled.
After I enabled VD agent, the mouse was much better behaved in the SPICE client, but in noVNC the mouse breaks as soon as you set the video driver to SPICE/QXL
Well, I notice that the way that noVNC breaks, looks and feel a LOT like the "double acceleration" mouse bug that SPICE has before the VD agent is enabled.
And I think, without VD Agent the mouse movements are relative and that's where the bug is, it's in the relative movement mouse acceleration and I think they're getting doubled, or the acceleration curve is ^2 or something like that.
And I think this is what is causing the mismatch between noVNC and SPICE.
And the problem is that this forces you to use one, or the other and you have at least a reboot to switch in between.
This usually ends up with me just giving up on SPICE being just too clunky and I prefer that noVNC works poorly everywhere, rather than have better responding SPICE but that I need to make work everywhere else.
But, other than the cursor, noVNC and SPICE work totally fine. With VD Agent I can resize the SPICE window to resize the guest OS display resolution, and noVNC updated just as quickly and accurately. Really the only problem is that cursor bug.
Is there any effort active to resolve that ? It does seem like virtualization in general has given up on SPICE, as video encoding appears not to work and the client still doesn't have dark mode. I imagine it got in that weird zone where, it should be good enough to use, but most people don't and it was probably assume that people just don't care, but really, it's just too clunky to use, even though it is really really close to being usable !