Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opengles 2.0 BUG BackBufferCopy child node, change the ZIndex buffer to screen cache. BackBuffer Copy cannot be sampled correctly #27586

Open
cjmxp opened this issue Apr 2, 2019 · 8 comments

Comments

@cjmxp
Copy link

cjmxp commented Apr 2, 2019

Godot version:
3.2 dev

OS/device including version:
windows N 1080ti opengles 2.0

Issue description:

BackBufferCopy child node, change the ZIndex buffer to screen cache. BackBuffer Copy cannot be sampled correctly

@Calinou
Copy link
Member

Calinou commented Apr 3, 2019

Can you upload an example project so we can try reproducing the issue?

@cjmxp
Copy link
Author

cjmxp commented Apr 3, 2019

@Calinou Tomorrow I'll write a demo.

@cjmxp
Copy link
Author

cjmxp commented Apr 3, 2019

Opengles 2.0 Reproducible Opengles 3.0 No problem

@cjmxp
Copy link
Author

cjmxp commented Apr 3, 2019

demo backbuffercopy-bug.zip

@cjmxp
Copy link
Author

cjmxp commented Apr 4, 2019

@reduz 3.1 This problem also exists.

@cjmxp cjmxp changed the title BackBufferCopy child node, change the ZIndex buffer to screen cache. BackBuffer Copy cannot be sampled correctly Opengles 2.0 BUG BackBufferCopy child node, change the ZIndex buffer to screen cache. BackBuffer Copy cannot be sampled correctly Apr 10, 2019
@cjmxp cjmxp closed this as completed May 20, 2019
@Calinou
Copy link
Member

Calinou commented May 20, 2019

@cjmxp According to your last comment, this issue still appears to be present, so I'll reopen it.

@Calinou Calinou reopened this May 20, 2019
@groud
Copy link
Member

groud commented May 20, 2019

I encountered several such issues, which were ignored and solved without marking the version.

There are almost 2000 other bugs opened (and almost 5000 issues), please stop thinking that contributors do not care about your issue because it does not have label/milestone or takes a long time to get fixed. That's normal.

Let's make things simple:

  • You raise the issue and let it open => the issues has a chance to get fixed someday,
  • You don't raise the issue or close it => it will never be fixed.

@KoBeWi
Copy link
Member

KoBeWi commented Sep 26, 2020

Still valid in 3.2.3
Works fine on master with Vulkan renderer (although might be again a problem if GLES2 is reintroduced for 2D).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants