-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UwcIsWindowsGraphicsCaptureCursorCaptureEnabledApiSupported crash #26
Comments
Hi Curtis, thank you for the information! |
Hi Hecomi, That's great, let me know if you need any further information or would like me to test with the user who found the issue! |
I was unable to reproduce this crash on my laptops (1909 / 1903)... |
I will try this now, thanks! |
That seems to have fixed the crash this user was experiencing, thank you! |
Hi Hecomi, That same user just reported another crash that seems to be related to the same method, though it could just be a coincidence.
So far I have not heard of this crash from other users, however, there aren't many in my testing team who have no monitors on the main GPU. They did report that with the crash fix (v1.0.2-temp) Windows.Graphics.Capture is working as intended, the yellow borders show around windows to confirm this. This appears to have happened upon activating the window GameObject. |
Could you please try again with v1.0.2? |
I am having the user try the new build, I will let you know in a few days! |
Hello,
It seem that by disabling the cursor, getting the errors of the dll on unity log, capping the streaming at 20fps and using the PrintWindow method for streaming , there is less crashes. |
Hi Hecomi,
Loving the new update, Windows.Graphics.Capture is great!
Though I have found a crash:
0x00007FFF29546122 (uWindowCapture) UwcIsWindowsGraphicsCaptureCursorCaptureEnabledApiSupported ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFF29539287) 0x00007FFF29539287 (uWindowCapture) (function-name not available) 0x00007FFF2953D8F7 (uWindowCapture) UwcIsWindowsGraphicsCaptureCursorCaptureEnabledApiSupported 0x00007FFF2953DC17 (uWindowCapture) UwcIsWindowsGraphicsCaptureCursorCaptureEnabledApiSupported 0x00007FFF29570210 (uWindowCapture) UwcIsWindowsGraphicsCaptureCursorCaptureEnabledApiSupported 0x00007FFF479053FE (KERNEL32) BaseThreadInitThunk 0x00007FFF496A590B (ntdll) RtlUserThreadStart
This same system also returned 'Unsupported' for all displays by uDesktopDuplication, so I assume all their displays are off their main GPU.
They are on Windows 10 version 2004 or later, Windows.Graphics.Capture is supported by the OS version at least.
The text was updated successfully, but these errors were encountered: