search for: blitting

I want to put a bug in bugzilla but i prefer first asking here what is revelant in this console output concerning race driver GRID demo Code: fixme:mixer:ALSA_MixerInit No master control found on Brooktree Bt878, disabling mixer fixme:ntdll:NtQueryInformationProcess (0xffffffff,info_class=34,0x218a3b8,0x0000 0004,0x218a3b4) Unknown information class fixme:ntdll:NtQuerySystemInformation

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

...you mean >> exactly by bind/unbind? Do you mean the transfer_map/unmap stuff? So >> basically I would blit once on set_framebuffer_state, and then blit >> back and forth on resource map/unmap, and only ever render to the >> "temporary" buffer without worrying about blitting wihle rendering? > > "bind" is when a buffer is set, "unbind" is when the buffer is unset. > set_framebuffer_state unbinds the current framebuffer and binds a new > one. > > transfer_map/unmap must use the resource which contains the latest > data, there is...

...% on all the terminology -- what do you mean exactly by bind/unbind? Do you mean the transfer_map/unmap stuff? So basically I would blit once on set_framebuffer_state, and then blit back and forth on resource map/unmap, and only ever render to the "temporary" buffer without worrying about blitting wihle rendering? > > You can also drop support for 16-bit formats. I assumed that these were required by some GL version... I also presume that it's faster to use these. BTW, when I say 16-bit, I mean like B5G6R5 or B5G5R5X1, not R16*. > > What about rendering to R16F, RG16F, and...

...y by bind/unbind? Do you mean the transfer_map/unmap stuff? So >>>> basically I would blit once on set_framebuffer_state, and then blit >>>> back and forth on resource map/unmap, and only ever render to the >>>> "temporary" buffer without worrying about blitting wihle rendering? >>> >>> "bind" is when a buffer is set, "unbind" is when the buffer is unset. >>> set_framebuffer_state unbinds the current framebuffer and binds a new >>> one. >>> >>> transfer_map/unmap must use the resourc...

Hello, I attempted doing this a while back, before I really understood what was going on. I got some advice that went totally over my head, and I dropped the issue. I think I'm much better-prepared to tackle the issue this time around. To recap, nv30 (and nv40) hw can't handle certain color/depth format combinations. Specifically, a 16-bit color format must be paired with a 16-bit depth

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) I...

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

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:

...;> exactly by bind/unbind? Do you mean the transfer_map/unmap stuff? So >>> basically I would blit once on set_framebuffer_state, and then blit >>> back and forth on resource map/unmap, and only ever render to the >>> "temporary" buffer without worrying about blitting wihle rendering? >> >> "bind" is when a buffer is set, "unbind" is when the buffer is unset. >> set_framebuffer_state unbinds the current framebuffer and binds a new >> one. >> >> transfer_map/unmap must use the resource which contains the lat...

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

Hey all, I've downloaded and installed Wine v.1.3.13 and using that, installed Dungeon Keeper 2 from the iso (including patches and a crack) on my mac (OS X Lion). However, when I start the game, the graphics are, what I can only describe as, "screwy". The log for this exe is provided Code: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify

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 > >

...logy -- what do you mean > exactly by bind/unbind? Do you mean the transfer_map/unmap stuff? So > basically I would blit once on set_framebuffer_state, and then blit > back and forth on resource map/unmap, and only ever render to the > "temporary" buffer without worrying about blitting wihle rendering? "bind" is when a buffer is set, "unbind" is when the buffer is unset. set_framebuffer_state unbinds the current framebuffer and binds a new one. transfer_map/unmap must use the resource which contains the latest data, there is no doubt about that. If there ar...

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 at alum.mit.edu> ---

On Tue, May 20, 2014 at 9:58 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Hello, > > I attempted doing this a while back, before I really understood what > was going on. I got some advice that went totally over my head, and I > dropped the issue. I think I'm much better-prepared to tackle the > issue this time around. > > To recap, nv30 (and nv40) hw

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,

Need to adjust coordinates since the shader receives the array index as depth in z, but the TEX instruction expects it to be the second coordinate for a 1D array texture. This fixes fbo-generatemipmap-array. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedesktop.org> --- src/gallium/drivers/nouveau/nv50/nv50_surface.c | 6 ++++++ 1