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
This usually is logged in firefox when you try to read pixels from an out-of-viewport location and render them. Because there are no out-of-viewport pixels to read the browser has to create a buffer filled with zeroes for you, which is slow.
Hmm, I don't understand... Viewport specifies the region of the render target and how is this related to the texture to be read?
// This has two usecases:
// 1. Lazy zeroing of uninitialized textures:
// a. Before draw, when FakeBlack isn't viable. (TexStorage + Draw*)
// b. Before partial upload. (TexStorage + TexSubImage)
// 2. Zero subrects from out-of-bounds blits. (CopyTex(Sub)Image)
OK so probably texture is not initialized when it is used. However, not-initializing is intentional in Ebiten for performance.
Version 60.0.2 (64-bit)
The text was updated successfully, but these errors were encountered: