search for: blit

...(0x502) from attach_surface_fbo @ device.c / 6096 fixme:dsound:DllCanUnloadNow (void): stub fixme:dsound:DllCanUnloadNow (void): stub fixme:dsound:DllCanUnloadNow (void): stub fixme:dsound:DllCanUnloadNow (void): stub fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Blt Filters not supported in software blit fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Blt Filters not supported in software blit fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Blt Filters not supported in software blit fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Blt Filters not supported in software blit fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Bl...

Trying to run THIS (http://appdb.winehq.org/objectManager.php?sClass=version&iId=5130) game using a current wine build (latest dev) results in the game STARTING, changing the resolution, showing the intro... But as soon as you press ESC it freezes (music keeps playing). If you don't press ESC, intro runs, high scores are displayed on title screen, and then nada... Any ideas on getting

...;> of doing the following: >>>> >>>> When rendering (i.e. draw_vbo & co) and the fbo has changed (and has >>>> one of the problems above), I would instead put in a temporary texture >>>> as the depth attachment. Before actually drawing, I would blit from >>>> the real target texture into the temporary texture, and then when >>>> rendering is done, blit back from the temp texture back into the >>>> target. This deals with the target texture getting modified between >>>> draws with various blits/ma...

...e structured, I was thinking >> of doing the following: >> >> When rendering (i.e. draw_vbo & co) and the fbo has changed (and has >> one of the problems above), I would instead put in a temporary texture >> as the depth attachment. Before actually drawing, I would blit from >> the real target texture into the temporary texture, and then when >> rendering is done, blit back from the temp texture back into the >> target. This deals with the target texture getting modified between >> draws with various blits/mapping/whatever. >> >&gt...

...t;>>>>> >>>>>> When rendering (i.e. draw_vbo & co) and the fbo has changed (and has >>>>>> one of the problems above), I would instead put in a temporary texture >>>>>> as the depth attachment. Before actually drawing, I would blit from >>>>>> the real target texture into the temporary texture, and then when >>>>>> rendering is done, blit back from the temp texture back into the >>>>>> target. This deals with the target texture getting modified between >>>>>...

.... Now that I kinda understand how things are structured, I was thinking of doing the following: When rendering (i.e. draw_vbo & co) and the fbo has changed (and has one of the problems above), I would instead put in a temporary texture as the depth attachment. Before actually drawing, I would blit from the real target texture into the temporary texture, and then when rendering is done, blit back from the temp texture back into the target. This deals with the target texture getting modified between draws with various blits/mapping/whatever. This means that you'll only get 16 bits of dept...

Hello, I''m coding a 2D map editor for a small game engine and I''m running into blitting problems. The bigger my map is, the longer it takes to blit a tile on it. sometimes, when I try to draw a tile to fast, it even fails completely at blitting and I have to close and reopen the program for it to work again. I have attached the main drawing methods to this post. How it works: 1...

1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128 was important as otherwise the GPU spams us with `CACHE_ERROR` messages. We use the blit subchannel inside our vblank handling, so we should keep at least this part. v2: Only do it for NV11+ GPUs Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/201 Fixes: 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") Signed-off-by: Karol Herbst <kherbst at redh...

1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128 was important as otherwise the GPU spams us with `CACHE_ERROR` messages. We use the blit subchannel inside our vblank handling, so we should keep at least this part. Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/201 Fixes: 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drivers/gpu/drm...

...he following: >>>>> >>>>> When rendering (i.e. draw_vbo & co) and the fbo has changed (and has >>>>> one of the problems above), I would instead put in a temporary texture >>>>> as the depth attachment. Before actually drawing, I would blit from >>>>> the real target texture into the temporary texture, and then when >>>>> rendering is done, blit back from the temp texture back into the >>>>> target. This deals with the target texture getting modified between >>>>> draws with...

This fixes a somewhat indeterministic corruption problem on nv17 when there is stuff going on the other fifos (e.g. gallium but I've also reproduced it with an app just SIFM-ing memory around): in some cases it made the blits the X server had scheduled use the wrong pitch. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- src/nv04_exa.c | 22 ++++++++++++---------- 1 files changed, 12 insertions(+), 10 deletions(-) diff --git a/src/nv04_exa.c b/src/nv04_exa.c index 132c9d5..7384cbc 100644 --- a/s...

...plemented yet. err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not registered err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441} could be created for context 0x1 fixme:d3d_surface:surface_cpu_blt Filter WINED3D_TEXF_LINEAR not supported in software blit. fixme:d3d_surface:surface_cpu_blt Filter WINED3D_TEXF_LINEAR not supported in software blit. fixme:d3d_surface:surface_cpu_blt Filter WINED3D_TEXF_LINEAR not supported in software blit. fixme:d3d_surface:surface_cpu_blt Filter WINED3D_TEXF_LINEAR not supported in software blit. fixme:d3d_surface:s...

On Fri, May 26, 2023 at 5:11?AM Karol Herbst <kherbst at redhat.com> wrote: > > 1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128 > was important as otherwise the GPU spams us with `CACHE_ERROR` messages. > > We use the blit subchannel inside our vblank handling, so we should keep > at least this part. > > v2: Only do it for NV11+ GPUs > > Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/201 > Fixes: 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") > Signed-off-by:...

...thinking >>> of doing the following: >>> >>> When rendering (i.e. draw_vbo & co) and the fbo has changed (and has >>> one of the problems above), I would instead put in a temporary texture >>> as the depth attachment. Before actually drawing, I would blit from >>> the real target texture into the temporary texture, and then when >>> rendering is done, blit back from the temp texture back into the >>> target. This deals with the target texture getting modified between >>> draws with various blits/mapping/whatever....

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedestkop.org> --- src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp index b8d0d3e..d566c99

fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in software blit. fixme:d3d_surface:surface_cpu_blt Stretched blit not implemented for bpp 64! I've tried different graphics settings without luck. Any ideas on the current *21 wine. Thanks

The 2D engine should be usable in more cases, but this fixes MS blits between textures with the same MS settings. Otherwise a single sample is selected to be the target texel value. This allows other tests to work that render to a RB and then blit that to a texture for input into a shader that uses sampler2DMS to verify it. Signed-off-by: Ilia Mirkin <imirkin a...

...rstand how things are structured, I was thinking > of doing the following: > > When rendering (i.e. draw_vbo & co) and the fbo has changed (and has > one of the problems above), I would instead put in a temporary texture > as the depth attachment. Before actually drawing, I would blit from > the real target texture into the temporary texture, and then when > rendering is done, blit back from the temp texture back into the > target. This deals with the target texture getting modified between > draws with various blits/mapping/whatever. > > This means that you...

Make sure to normalize the z coordinates as well as the x/y ones when there are mipmaps present. Fixes 3d mipmap generation, which now uses the blit path. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedesktop.org> --- Did a full piglit run on nva8 and nve7 without regressions. The cubemap array mipmap generation test still fails, but that will require more careful investigation...

...hanged, 6 insertions(+) diff --git a/src/gallium/drivers/nouveau/nv50/nv50_surface.c b/src/gallium/drivers/nouveau/nv50/nv50_surface.c index 8addefe..23613d8 100644 --- a/src/gallium/drivers/nouveau/nv50/nv50_surface.c +++ b/src/gallium/drivers/nouveau/nv50/nv50_surface.c @@ -698,6 +698,12 @@ nv50_blitter_make_fp(struct pipe_context *pipe, tc = ureg_DECL_fs_input( ureg, TGSI_SEMANTIC_GENERIC, 0, TGSI_INTERPOLATE_LINEAR); + if (ptarg == PIPE_TEXTURE_1D_ARRAY) { + /* Adjust coordinates. Depth is in z, but TEX expects it to be in y. */ + tc = ureg_swizzle(tc, TGSI_SWIZZLE_X,...