src | Source texture. |
dst | Destination texture. |
srcElement | Source texture element (cubemap face, texture array layer or 3D texture depth slice). |
srcMip | Source texture mipmap level. |
dstElement | Destination texture element (cubemap face, texture array layer or 3D texture depth slice). |
dstMip | Destination texture mipmap level. |
srcX | X coordinate of source texture region to copy (left side is zero). |
srcY | Y coordinate of source texture region to copy (bottom is zero). |
srcWidth | Width of source texture region to copy. |
srcHeight | Height of source texture region to copy. |
dstX | X coordinate of where to copy region in destination texture (left side is zero). |
dstY | Y coordinate of where to copy region in destination texture (bottom is zero). |
Copy texture contents.
This function allows copying pixel data from one texture into another efficiently.
It also allows copying from an element (e.g. cubemap face) or a specific mip level, and from a subregion of a texture.
Copying does not do any scaling, i.e. source and destination sizes must be the same. Texture formats should be compatible
(for example, TextureFormat.ARGB32 and RenderTextureFormat.ARGB32 are compatible). Exact rules for which formats
are compatible vary a bit between graphics APIs; generally formats that are exactly the same can always be copied.
On some platforms (e.g. D3D11) you can also copy between formats that are of the same bit width.
Compressed texture formats add some restrictions to the CopyTexture with a region variant. For example, PVRTC formats
are not supported since they are not block-based (for these formats you can only copy whole texture or whole mip level).
For block-based formats (e.g. DXT, ETC), the region size and coordinates must be a multiple of compression block size
(4 pixels for DXT).
If both source and destination textures are marked as "readable" (i.e. copy of data exists
in system memory for reading/writing on the CPU), these functions copy it as well.
Some platforms might not have functionality of all sorts of texture copying (e.g. copy from a
render texture into a regular texture). See CopyTextureSupport, and use
SystemInfo.copyTextureSupport to check.
Calling Texture2D.Apply, Texture2DArray.Apply or Texture3D.Apply after CopyTexture
yields undefined results as CopyTexture
operates on GPU-side data exclusively, whereas Apply
transfers data from CPU to GPU-side.
See Also: CopyTextureSupport.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.