Skip to content
This repository has been archived by the owner on Jul 19, 2018. It is now read-only.

No error reported for a buffer->image copy op which exceeds target mip's extents #2621

Open
DominikWitczakAMD opened this issue Apr 27, 2018 · 3 comments
Assignees
Milestone

Comments

@DominikWitczakAMD
Copy link
Contributor

Consider a copy op which:

  • targets a BC1-compressed image mip of size 5x3x1
  • uses start offset of 0x0x0
  • has extents of 8x4x1

No error is reported by the layers in this scenario, even though for this specific use case where start offset is located at zero and the app intends to fill the whole mip with data, it should specify a copy region of size 5x3x1.

Extents of 8x4x1, despite being aligned to the compressed block size, exceeds available mip space which is an error, as per language found in section 18.4 of the spec.

@tobine
Copy link
Contributor

tobine commented Apr 27, 2018

Seems like this is VALIDATION_ERROR_18e00158 which DB claims a check for but may be incomplete.

@mark-lunarg mark-lunarg added this to the P1 milestone Apr 27, 2018
@mark-lunarg
Copy link
Collaborator

@daveh-lunarg, Images! Extents! Offsets! MipLevels! Just sayin'.

@daveh-lunarg
Copy link
Contributor

@mark-lunarg, Ugh. I wish there was a more expressive emoticon available.

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

No branches or pull requests

4 participants