-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Enable depth buffer copies on GLES3 devices without breaking any desktop
- Loading branch information
Showing
1 changed file
with
11 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43a93f0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tested on my Android 4.3 .It works beautifully and almost no performance penality (by company this build and the previous one)
Tested game :
43a93f0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But #5028 (and also #5032, but I didn't mean that one, oops) could've been caused by these copies. I'm sure there's no major performance penalty in Jeanne d'Arc.
-[Unknown]
43a93f0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least this should work the same as on PC.
Maybe we need to make it an option after all, sigh..
Or we should try to track depth buffers separately from color buffers after all. The drawback with that is that stencil will be attached to the depth buffer rather than the color buffer...
43a93f0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the problems associated with the color and stencil buffers not being tracked together will be worse than the depth ones...
Well, I'd prefer to get it right. I'm guessing framebuffer sizing is messing with it now.
-[Unknown]