Glad to hear Dmitri solved your problem… and that it was not a bug after all of course ;D
Glad it helped.
One thing - you might want to start using BufferStrategy instead
of VolatileImage if possible.
In the future copying VIs to the screen may get problematic
(i.e, Direct3D9 doesn’t allow this kind of thing)…
Dmitri
This is strange, I don’t understand whats the magic to bind a renderable-buffer to a texture and use it … somehow strange. Why would a API designer would like to disallow it?
Will you have to do readbacks for allowing this?
Hmm, well for this thing I’ll leave it as-is, I simply have not enough knowledge about LwVCL to be sure that nothing is broken.
So I no longer want to consume your time, to be honest I feel really guilty for taking your time away for solving stupid implementation mistakes. Thanks a lot for analyzing the code … man you made me happy 
Thank you many times again, Clemens