wined3d: Use wined3d_texture_bind_and_dirtify() in device_update_volume().

I missed this in 7c4d512f. Generally speaking, the only places where plain wined3d_texture_bind() calls are appropriate are places where you're binding the texture to a specific stage for a subsequent draw. I.e., places where context_active_texture() is called first.

wined3d: Use wined3d_texture_bind_and_dirtify() in device_update_volume().
5c9da580 · Henri Verbeet · Alexandre Julliard · 52478e38 · 5c9da580
Commit 5c9da580 authored Apr 16, 2015 by Henri Verbeet Committed by Alexandre Julliard Apr 16, 2015
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

device.c dlls/wined3d/device.c +1 -1

No files found.
--- a/dlls/wined3d/device.c
+++ b/dlls/wined3d/device.c
@@ -3511,7 +3511,7 @@ static HRESULT device_update_volume(struct wined3d_device *device,

    /* Only a prepare, since we're uploading the entire volume. */
    wined3d_texture_prepare_texture(dst_volume->container, context, FALSE);
-    wined3d_texture_bind(dst_volume->container, context, FALSE);
+    wined3d_texture_bind_and_dirtify(dst_volume->container, context, FALSE);

    data.buffer_object = 0;
    data.addr = src.data;