AUTOlTER Posted October 27, 2024 Posted October 27, 2024 Hi I've been working with this AWESOME library for some time, on different versiones of windows and different PCs and I have never faced this problem. Yesterday, after running my scripts in a new PC with Windows 11, I noticed that FFSnapShot works just the first time I call it. The next calls seem to produce the same snapshot as the first time, i.e it doesn't detect changes on the screen. This is a simplified version of the script Local $hWin = WinGetHandle("") While True FFSnapShot(0, 0, 120, 20, 0, $hWin) ConsoleWrite("@error: " & @error & @CRLF) ConsoleWrite("Last Error: " & FFGetLastError() & @CRLF) FFGetPixel(114, 0) Sleep(1000) WEnd I have also tried replacing the calls whit these ones, making explicit the $NoSnapShot with same results. FFSnapShot(0, 0, 120, 20, 1, $hWin) FFGetPixel(114, 0, 1) The last error is an empty string and @error equals 0 (with $FFDefaultDebugMode = 0xE7) I have also noticed that restarting the script doesn't help. The same script works just fine on other PCs, even with Windows 11. Thanks in advance.
Solution AUTOlTER Posted October 29, 2024 Author Solution Posted October 29, 2024 Hi again I've found a solution, making Windows choose the integrated graphics (power saving): This notebook have 2 GPUs: I share system specs just in case I think this might be interesting for the author: @FastFrench. Let me thank you personally for this work. It's quite useful for my projects. In addition to the previous post. The return of FFSnapShot is always True. So there is no error even when FFSnapShot produces the same SS as the first call, which I checked using FFGetPixel and FFSaveJPG.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now