You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drawing with GPU acceleration makes canvas background black (regardless of flushed or not), and SKSurface.Snapshot() is empty after second SKCanvas.Flush().
After the first render (the red circled area is the entire canvas is having the problem. the other canvas is the entire window):
After the second render:
If I take SKSnapshot straight after second flush, the snapshot is empty, but if I do the drawing-and-flushing process multiple times at some other point in the program and not directly before the snapshot, there isn't an issue.
The text was updated successfully, but these errors were encountered:
Just a quick thought maybe in some specific cases when canvas.Clear(); passes a transparent color somewhere internally it treats it as Black instead of Transparent.
That empty second frame makes me think of double-buffering where the second buffer was shown but not filled..
This is quite a long question.
Drawing with GPU acceleration makes canvas background black (regardless of flushed or not), and SKSurface.Snapshot() is empty after second SKCanvas.Flush().
I am creating an SKCanvas like this:
And rendering to it like this:
Then finally drawing it to another canvas that uses a Silk.NET GLFW window GLContext:
After the first render (the red circled area is the entire canvas is having the problem. the other canvas is the entire window):
![image](https://user-images.githubusercontent.com/46281840/143937726-2179dbd7-7ba4-4a7d-8711-1e1a56608180.png)
![image](https://user-images.githubusercontent.com/46281840/143938000-1f50294f-3681-4807-8d15-2d1d7671eb47.png)
After the second render:
If I take SKSnapshot straight after second flush, the snapshot is empty, but if I do the drawing-and-flushing process multiple times at some other point in the program and not directly before the snapshot, there isn't an issue.
The text was updated successfully, but these errors were encountered: