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

WorldEnvironment Auto Exposure only works if framebuffer allocation is set to 3D, not 3D Without Effects #55975

Closed
LoserFox opened this issue Dec 16, 2021 · 7 comments

Comments

@LoserFox
Copy link

Godot version

v3.4.stable.official.206ba70f4

System information

Android, huawei mate10 ,GLES3

Issue description

When I export a game that includes auto exposure post-processing to the android platform, the game screen will flicker. I think it is caused by auto exposure not supporting the android platform. I am using GLES3

Steps to reproduce

Use gles3 and auto exposure in any project to reproduce the problem

Minimal reproduction project

No response

@timothyqiu
Copy link
Member

I think you have to set rendering/quality/intended_usage/framebuffer_allocation.mobile to 3D in Project Settings first, it could resolve the flickering.

Although the flickering will possibly be gone, the auto exposure still won't work as expected I think. Could you try if #55983 works for you? You can try the export template in my own build in case it's not ready here: https://github.com/timothyqiu/godot/actions/runs/1586478548

@LoserFox
Copy link
Author

The problem was discussed in private with "timothyqiu". The problem is that the default value of "framebuffer_allocation.mobile" is 3D Without Effects. This option does not support auto exposure post-processing. Replace it with 3D to solve the problem.

@LoserFox
Copy link
Author

相关问题可查看#27439

@Calinou
Copy link
Member

Calinou commented Dec 16, 2021

Reopening, as we need to amend the documentation to mention this.

Does this mean the following line in the class reference is incorrect?

These effects will only apply when the [Viewport]'s intended usage is "3D" or "3D Without Effects". This can be configured for the root Viewport with [member ProjectSettings.rendering/quality/intended_usage/framebuffer_allocation], or for specific Viewports via the [member Viewport.usage] property.

Could someone test all 4 of those effects with the 3D Without Effects framebuffer allocation (preferably on mobile)?

@Calinou Calinou reopened this Dec 16, 2021
@Calinou Calinou changed the title auto exposure not working the Android WorldEnvironment Auto Exposure only works if framebuffer allocation is set to 3D, not 3D Without Effects Dec 16, 2021
@LoserFox
Copy link
Author

Reopening, as we need to amend the documentation to mention this.

Does this mean the following line in the class reference is incorrect?

These effects will only apply when the [Viewport]'s intended usage is "3D" or "3D Without Effects". This can be configured for the root Viewport with [member ProjectSettings.rendering/quality/intended_usage/framebuffer_allocation], or for specific Viewports via the [member Viewport.usage] property.

Could someone test all 4 of those effects with the 3D Without Effects framebuffer allocation (preferably on mobile)?

i will try it

@LoserFox
Copy link
Author

After my test, only ss_reflections and ssao are invalid under 3D Without Effects on PC. I guess it’s the same on Android

@LoserFox
Copy link
Author

LoserFox commented Dec 17, 2021

I tried to create a pull request to fix the errors on the document, you can take a look at it. (The first time I created a pull request, there may be some errors) #56034

@Calinou Calinou modified the milestones: 3.x, 3.5, 3.4 Aug 17, 2022
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