Yes, completely sure, with the previous version (5.0-13905) this does not happen.
I forgot to mention that with OpenGL the error does not occur, only in software and with Direct3D 11.
I forgot to mention that with OpenGL the error does not occur, only in software and with Direct3D 11.
