Highrez

Please fill in this template when posting!
XMBC Version: 2.20 Beta 4
Installed or Portable version: Installed
Windows Version: Windows 11 build 22593.1
Mouse Information (brand/model): Hama AM 8200
Relevant Computer Information (CPU, RAM etc): Intel Core i7 9th Gen, 16 GB RAM, ASUS ROG Stix
Did the problem occur after an upgrade of XMBC? (If so, from what version?): No
Did the problem occur after a Windows update/upgrade? (If so, from what version?): Yes, after upgrade to 22593.1
How long have you used XMBC?: For 4-5 years
What language and keyboard layout do you use in Windows?: Hungarian

Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).:

Dear Phil,

I'm very sad, because XBMC stopped working on this new build of Win11. They have changed something, but there is no info about it.
The function that does not work is the brightness setting. I use my side buttons (4 and 5) of my mouse to change brightness with the {BRIGHTNESS-}{ACTIVATE} and {BRIGHTNESS+}{ACTIVATE} commands, and it worked well until this upgrade.
Can you please test XBMC with this Win11 build to find out what happened? The brightness flyout has an X, and the slider stays on the bottom, and I cannot change the brightness.

Thank you in advance!
Adaz

I'm not running beta builds of win11 currently, so no I cant test it right now.
I have the current version of Win11 on my laptop (22000.556), but I just don't have the time to test every beta/dev build. It will have to wait I'm afraid.
I cant off the top of my head remember how the brightness stuff works, but I think its a rather complex one - so if Microsoft have changed it, it could be a bit of a bu**er to fix!

Dear Phil,
I see, thank you. Then I'll wait and hope

Out of interest, is this the 22H2 build tree?

There does look to be some good stuff in there so I will probably get to it before final, but only on a test device (my main dev machines are still Windows 10 - for various reasons, not lease TPM support). I've only recently upgraded my laptop/surface to II. It might be that I could stick the surface on the dev/insider branch but it will take me a while to find some time to get all that sorted out.

I used to be all over pre-release builds but the tendency recently has been to stick with what I know! I guess it happens to us all at some point

Ah, that's great news then! I hope you can install this build on a test machine in the near future, and try to repeat the issue.
I hope you will find a solution...

phil wrote: ↑Tue Apr 12, 2022 11:07 am Out of interest, is this the 22H2 build tree?

I don't know, it could be a never released build, but probably they will bring this change with them to the future builds.

Thank you in advance,
Adaz

By the way, 22598 is affected as well.
This build can be downloaded as an ISO here: a k a . m s / wipISO

Best,
Adaz

Good news!
Build 22616 came out today, and the brightness is working again!
There is no mention of this error in the announcement, so I think they silently resolved it. I hope it will be permanent, and not a "mistake".
So thank you, you don't have to deal with this error anymore. I'll let you know if it occurs again.

phew! I was quietly hoping that would happen! The wonders of beta testing! Keep me informed if anything else changes!