You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a game running in 1920x1080 and we are
using rendering to texture using fbo.
The render texture is 2048x2048,
so we set glViewport(0,0, 1920,1080).
and we expect that during rendering to 2048x2048 texture only
1920x1080 part will be used. And than we blit RT to main framebuffer.
This works as expected on desktop OpenGL and DX11/D3D11 version of libAngle.
However it seems that under D3d9 glViewport is not respected on FBO/RT
and rendering is being performed on the whole 2048x2048 texture.
As a result when we blit RT to main framebuffer we only get a (scaled up) part of the expected rendering.
glViewport should be respected during FBO/RT rendering under D3D9
as it is on OpenGL and D3D11.
I tried many versions of ANGLE from most recent to end of 2015
and the bug is there in all of them. Tested on Win10/GTX960m.
The text was updated successfully, but these errors were encountered:
Our team is primarily focused on maintaining the D3D11 version of ANGLE. For issues with the D3D9 renderer I recommend starting a discussion over on the master ANGLE project discussion pages.
We have a game running in 1920x1080 and we are
using rendering to texture using fbo.
The render texture is 2048x2048,
so we set glViewport(0,0, 1920,1080).
and we expect that during rendering to 2048x2048 texture only
1920x1080 part will be used. And than we blit RT to main framebuffer.
This works as expected on desktop OpenGL and DX11/D3D11 version of libAngle.
However it seems that under D3d9 glViewport is not respected on FBO/RT
and rendering is being performed on the whole 2048x2048 texture.
As a result when we blit RT to main framebuffer we only get a (scaled up) part of the expected rendering.
glViewport should be respected during FBO/RT rendering under D3D9
as it is on OpenGL and D3D11.
I tried many versions of ANGLE from most recent to end of 2015
and the bug is there in all of them. Tested on Win10/GTX960m.
The text was updated successfully, but these errors were encountered: