search for: wihl

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

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

.../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 whi...

Has anyone been able to make Photoshop CS2 work on wine? Mine works almost, wihle starting it just says that registration data incorrect, must shut down. I have working installation on windows though.

...hat 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 are no...

...ctly 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 &...

...5, 0.919057338245786, -0.085175885159938, 0.174891510504697, -0.639827759135, -1.80974578397221, 0.298106240033569, -0.410129481117372, 1.12489185606582, 0.527277375478827, -0.917240000748393, 0.464087477214494, 1.52046606812109, 0.60474736264106, -0.40! 8808568730677, -0.554248793092077, > Wihle, when I run the same program on the old Version 1.7.1, I've got different result as follows:R : Copyright 2003, The R Development Core TeamVersion 1.7.1 (2003-06-16)R is free software and comes with ABSOLUTELY NO WARRANTY.You are welcome to redistribute it under certain conditions.Type `lice...

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