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
As you can see from the attached 'SDL_RenderSetClipRect' does not work well
because the area of the clip does not coincide with the area set on 'SDL_RenderSetLogicalSize'.
On 2014-01-06 15:19:57 +0000, wrote:
*** Bug 2336 has been marked as a duplicate of this bug. ***
On 2014-06-07 20:15:50 +0000, Leonardo wrote:
Created attachment 1674
Uses viewport x and y to set cliprect x/y
Hello. This bug happens because the viewport x/y is not being taken in consideration when setting the clipping rectangle (and render logical size is implemented as a combination of viewport and scale)
With the proposed patch, I've fixed this problem for the OpenGL[ES[2]] renderers but I have no idea if such problems occur in the DirectX renderer (couldn't be sure after superficially analyzing its code). Also I havent tested it in more odd combinations of scaling, viewport, target textures, etc.
As a workaround until this is fixed, one can get the viewport and add its x/y coordinates to the clipping rectangle:
Created attachment 2010
Adds viewport x/y to cliprect in UpdateClipRect + D3D
Hello. I was affected by this bug and found Leonardo's patch to work better than raincomplex's. I guess it's better to add the viewport coordinates when the driver updates the scissor rect than to do it beforehand.
Attached patch is the same as Leonardo's but with fix for D3D added.
On 2015-02-18 21:44:21 +0000, Ryan C. Gordon wrote:
*** Bug 2336 has been marked as a duplicate of this bug. ***
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Uses viewport x and y to set cliprect x/y (consider-viewport-in-renderer-clip-rect.patch, text/plain, 2014-06-07 20:15:50 +0000, 1986 bytes)add viewport x/y to clipping rectangle (p, text/plain, 2014-09-26 02:21:40 +0000, 739 bytes)Reported in version: 2.0.1
Reported for operating system, platform: Windows 8, x86_64
Comments on the original bug report:
On 2013-11-24 16:35:06 +0000, neo wrote:
On 2014-01-06 15:19:57 +0000, wrote:
On 2014-06-07 20:15:50 +0000, Leonardo wrote:
On 2014-09-26 02:21:40 +0000, wrote:
On 2015-01-30 13:07:38 +0000, Vii wrote:
On 2015-02-18 21:44:21 +0000, Ryan C. Gordon wrote:
On 2015-05-29 02:01:54 +0000, Sam Lantinga wrote:
The text was updated successfully, but these errors were encountered: