|
|
Chromium Code Reviews|
Created:
3 years, 7 months ago by Geoff Lang Modified:
3 years, 6 months ago Reviewers:
Zhenyao Mo CC:
chromium-reviews, piman+watch_chromium.org Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionSet the texture base level before generating sRGB mipmaps.
GL ES 3.0 considers the framebuffer incomplete if the texture is not mip
complete and the bound mip level is not the base level. Set the base
level to the attached texture level before rendering each level to avoid
this validation.
BUG=722684
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Review-Url: https://codereview.chromium.org/2900403003
Cr-Commit-Position: refs/heads/master@{#475349}
Committed: https://chromium.googlesource.com/chromium/src/+/54841760a98142fac982f3ec12064093b8c3a7da
Patch Set 1 #Patch Set 2 : Make sure texture is mip complete first instead of setting base level #Patch Set 3 : Fix sizes for mips #Messages
Total messages: 33 (24 generated)
Description was changed from ========== Set the texture base level before generating sRGB mipmaps. GL ES 3.0 considers the framebuffer incomplete if the texture is not mip complete and the bound mip level is not the base level. Set the base level to the attached texture level before rendering each level to avoid this validation. BUG=722684 ========== to ========== Set the texture base level before generating sRGB mipmaps. GL ES 3.0 considers the framebuffer incomplete if the texture is not mip complete and the bound mip level is not the base level. Set the base level to the attached texture level before rendering each level to avoid this validation. BUG=722684 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel ==========
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Set the texture base level before generating sRGB mipmaps. GL ES 3.0 considers the framebuffer incomplete if the texture is not mip complete and the bound mip level is not the base level. Set the base level to the attached texture level before rendering each level to avoid this validation. BUG=722684 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel ========== to ========== Set the texture base level before generating sRGB mipmaps. GL ES 3.0 considers the framebuffer incomplete if the texture is not mip complete and the bound mip level is not the base level. Set the base level to the attached texture level before rendering each level to avoid this validation. BUG=722684 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel ==========
geofflang@chromium.org changed reviewers: + zmo@chromium.org
PTAL, noticed this issue when updating ANGLE's framebuffer validation in https://chromium-review.googlesource.com/c/506928/
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
nvm on the review, looks like some Mac drivers can't handle this.
geofflang@chromium.org changed reviewers: - zmo@chromium.org
On 2017/05/25 17:03:25, Geoff Lang wrote: > nvm on the review, looks like some Mac drivers can't handle this. lgtm thanks for catching this
On 2017/05/25 17:07:46, Zhenyao Mo wrote: > On 2017/05/25 17:03:25, Geoff Lang wrote: > > nvm on the review, looks like some Mac drivers can't handle this. > > lgtm > thanks for catching this What? Do you know what's the Mac driver issue? Is it a driver bug we aren't aware of?
On 2017/05/25 17:09:00, Zhenyao Mo wrote: > On 2017/05/25 17:07:46, Zhenyao Mo wrote: > > On 2017/05/25 17:03:25, Geoff Lang wrote: > > > nvm on the review, looks like some Mac drivers can't handle this. > > > > lgtm > > thanks for catching this > > What? Do you know what's the Mac driver issue? Is it a driver bug we aren't > aware of? I'll have to dig into it but the mac driver on AMD and Intel is saying the framebuffer isn't complete.
On 2017/05/25 17:10:25, Geoff Lang wrote: > On 2017/05/25 17:09:00, Zhenyao Mo wrote: > > On 2017/05/25 17:07:46, Zhenyao Mo wrote: > > > On 2017/05/25 17:03:25, Geoff Lang wrote: > > > > nvm on the review, looks like some Mac drivers can't handle this. > > > > > > lgtm > > > thanks for catching this > > > > What? Do you know what's the Mac driver issue? Is it a driver bug we aren't > > aware of? > > I'll have to dig into it but the mac driver on AMD and Intel is saying the > framebuffer isn't complete. Just confirmed that it is returning GL_FRAMEBUFFER_UNSUPPORTED in these cases. I'll try only setting the base level for ES drivers.
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_optional_gpu_tests_rel on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_optional_gpu_...)
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2017/05/25 17:32:47, Geoff Lang wrote: > On 2017/05/25 17:10:25, Geoff Lang wrote: > > On 2017/05/25 17:09:00, Zhenyao Mo wrote: > > > On 2017/05/25 17:07:46, Zhenyao Mo wrote: > > > > On 2017/05/25 17:03:25, Geoff Lang wrote: > > > > > nvm on the review, looks like some Mac drivers can't handle this. > > > > > > > > lgtm > > > > thanks for catching this > > > > > > What? Do you know what's the Mac driver issue? Is it a driver bug we aren't > > > aware of? > > > > I'll have to dig into it but the mac driver on AMD and Intel is saying the > > framebuffer isn't complete. > > Just confirmed that it is returning GL_FRAMEBUFFER_UNSUPPORTED in these cases. > I'll try only setting the base level for ES drivers. Ok, PTAL again Mo. I've re-written it in a way that doesn't require changing the base level by creating all the mip levels before rendering into any of them.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by geofflang@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from zmo@chromium.org Link to the patchset: https://codereview.chromium.org/2900403003/#ps40001 (title: "Fix sizes for mips")
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 40001, "attempt_start_ts": 1496065607713610,
"parent_rev": "fd7049c799296867fa282afcc266239e22ac2be1", "commit_rev":
"54841760a98142fac982f3ec12064093b8c3a7da"}
Message was sent while issue was closed.
Description was changed from ========== Set the texture base level before generating sRGB mipmaps. GL ES 3.0 considers the framebuffer incomplete if the texture is not mip complete and the bound mip level is not the base level. Set the base level to the attached texture level before rendering each level to avoid this validation. BUG=722684 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel ========== to ========== Set the texture base level before generating sRGB mipmaps. GL ES 3.0 considers the framebuffer incomplete if the texture is not mip complete and the bound mip level is not the base level. Set the base level to the attached texture level before rendering each level to avoid this validation. BUG=722684 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2900403003 Cr-Commit-Position: refs/heads/master@{#475349} Committed: https://chromium.googlesource.com/chromium/src/+/54841760a98142fac982f3ec1206... ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001) as https://chromium.googlesource.com/chromium/src/+/54841760a98142fac982f3ec1206... |
