Is your feature request related to a problem? Please describe.
If you perform any PoE-overlay operations (e.g. F9, Ctrl+Q) while watching Youtube/Twitch using Google Chrome on the sub-screen, the Youtube/Twitch screen will black out.
Describe the solution you'd like
The workaround is
Chrome experimental flag "Calculate window occlusion on Windows"
Calculate window occlusion on Windows will be used in the future to throttle and potentially unload foreground tabs in occluded windows – Windows
calculate-native-win-occlusion
is to set it to "Disabled". I found that the problem does not occur after setting the flag.
It's best if your app doesn't conflict with Chrome, but here we'll add it to the README.md as "Known Issues" to give you quick access to the solution mentioned in the workarounds mentioned above.
I would like to suggest that you list the conflict issue with Chrome.
Describe alternatives you've considered
(already written above)
Additional context
This issue was reported in #253, #333, but was not treated as a bug.
I found these after discovering a workaround on my own.
The fact that it can be circumvented by simply changing Chrome's flags makes me hopeful that there may be a way to circumvent the hardware acceleration limitations mentioned in the ticket above.
It is preferable to list multiple solutions/workarounds until the technical details are clear.
🚀 feature request
Is your feature request related to a problem? Please describe.
If you perform any PoE-overlay operations (e.g. F9, Ctrl+Q) while watching Youtube/Twitch using Google Chrome on the sub-screen, the Youtube/Twitch screen will black out.
Describe the solution you'd like
The workaround is Chrome experimental flag "Calculate window occlusion on Windows"
It's best if your app doesn't conflict with Chrome, but here we'll add it to the README.md as "Known Issues" to give you quick access to the solution mentioned in the workarounds mentioned above. I would like to suggest that you list the conflict issue with Chrome.
Describe alternatives you've considered
(already written above)
Additional context
This issue was reported in #253, #333, but was not treated as a bug. I found these after discovering a workaround on my own. The fact that it can be circumvented by simply changing Chrome's flags makes me hopeful that there may be a way to circumvent the hardware acceleration limitations mentioned in the ticket above. It is preferable to list multiple solutions/workarounds until the technical details are clear.